# Phase 2: Artist Creation Wizard - Research

**Researched:** 2026-04-10
**Domain:** Interactive Claude Code skill for step-by-step artist identity creation, producing a structured markdown bible
**Confidence:** HIGH

## Summary

Phase 2 delivers the first interactive workflow in the project: a Claude Code skill that guides the user through creating a virtual music artist, collecting identity data step by step, and producing a complete artist bible at `artists/[name]/bible.md`. This is the foundational feature -- every downstream phase (track production, coherence, linguistic verification) depends on a well-structured artist bible existing.

The technical domain is well understood. Claude Code Skills (`.claude/skills/`) is the official workflow mechanism with documented frontmatter, `$ARGUMENTS` substitution, supporting files, and progressive context loading. The project's initial research (ARCHITECTURE.md, STACK.md) already validated this approach with HIGH confidence and provided detailed pattern examples. The key design challenge is not technical -- it is structural: designing the wizard's step flow, the bible's markdown schema, and the validation logic so that the bible serves as a reliable contract for all future phases.

The original `base/project.md` provides a JSON-based artist bible schema that captures the right fields but uses the wrong format (JSON instead of markdown) and misses several fields the project now requires (emotion palette depth, explicit coherence rules, forbidden themes, narrative constraints). The `artists/README.md` created in Phase 1 already defines the expected bible sections (Identite, Style Vocal, Palette Emotionnelle, Themes, Lore, Direction Visuelle, Influences) which serves as the authoritative schema outline.

**Primary recommendation:** Build one skill (`create-artist`) with a single SKILL.md file and supporting step files for each wizard phase. The SKILL.md acts as orchestrator; step files contain the detailed questions, guidance, and validation for each domain. The bible template lives in `reference/templates/` (currently empty, populated in this phase). The wizard must validate completeness before writing and present a summary for user review before finalization.

## Standard Stack

This phase produces no code -- only markdown files (skill definitions, templates, examples).

### Core

| Component | Location | Purpose | Why Standard |
|-----------|----------|---------|--------------|
| Claude Code Skill | `.claude/skills/create-artist/SKILL.md` | Interactive wizard entrypoint | Official Claude Code workflow mechanism. Supports frontmatter config, `$ARGUMENTS`, supporting files, `disable-model-invocation: true` for user-only triggers. |
| Step files | `.claude/skills/create-artist/steps/*.md` | Per-step detailed instructions | Progressive context loading -- Claude reads each step file only when reaching that step, keeping context lean. Recommended pattern from ARCHITECTURE.md. |
| Bible template | `reference/templates/bible-template.md` | Structural schema for artist bible | Defines the exact sections and fields every bible must contain. Acts as a contract for downstream phases. |

### Supporting

| Component | Location | Purpose | When to Use |
|-----------|----------|---------|-------------|
| Example bible | `.claude/skills/create-artist/examples/example-bible.md` | Completed example for reference | Claude reads this to understand the target output format. User can browse it for inspiration. |
| Genre guide reference | `reference/suno/format.md` (existing) | Genre tags, subgenres, mood vocabulary | Step 1 (musical identity) references this for genre/subgenre options. Already exists from Phase 1. |
| Glossary | `reference/glossary.md` (existing) | Term definitions | Reference during wizard for canonical terminology. Already exists from Phase 1. |

### Alternatives Considered

| Instead of | Could Use | Tradeoff |
|------------|-----------|----------|
| Step files in separate directory | All instructions in SKILL.md | SKILL.md would exceed 500 lines (recommended limit). Step files keep each concern focused and context lean. |
| YAML frontmatter in bible.md | Pure markdown headings | YAML adds machine-parseable metadata but CLAUDE.md/PROJECT.md established markdown-first approach. Keep bible pure markdown -- Claude parses headings reliably. |
| Bible template in skill directory | Template in `reference/templates/` | Phase 1 established `reference/templates/` as the home for templates (currently .gitkeep). Placing the bible template there follows the established convention and makes it accessible to all future phases. |
| Single monolithic bible file | Split bible (bible.md + vocal.md + visual.md + lore.md) | ARCHITECTURE.md researched the split pattern but `artists/README.md` (Phase 1 output, authoritative) defines a single `bible.md`. The single file keeps things simple for Phase 2; split can be explored later if bibles grow too large. Follow the established convention. |

## Architecture Patterns

### Recommended Skill Structure

```
.claude/skills/
  create-artist/
    SKILL.md                    # Wizard orchestrator (user-triggered)
    steps/
      01-identity.md            # Step 1: Name, genre, subgenres, languages
      02-vocal.md               # Step 2: Vocal identity (type, style, techniques)
      03-emotions-themes.md     # Step 3: Emotion palette + thematic universe
      04-personality-lore.md    # Step 4: Personality, backstory, narrative arc
      05-visual.md              # Step 5: Visual direction keywords
      06-review-validate.md     # Step 6: Review, validate, confirm, write
    examples/
      example-bible.md          # Complete example (adapted from base/project.md LUNA/NOVA)

reference/templates/
  bible-template.md             # Empty bible schema with section headers and field guidance
```

### Pattern 1: Wizard Skill with Step Files

**What:** SKILL.md contains the overall flow, user-interaction model, and output instructions. Each step file contains domain-specific questions, validation criteria, suggestions, and constraints for that wizard phase.

**When to use:** This skill. The wizard covers 6+ distinct domains (identity, vocal, emotions, personality, visual, validation) that would make a single file unwieldy.

**SKILL.md structure:**

```markdown
---
name: create-artist
description: Interactive wizard to create a complete virtual music artist identity. Use when the user wants to create a new artist, start the artist creation process, or build an artist bible from scratch.
argument-hint: [artist-name]
disable-model-invocation: true
allowed-tools: Read Write Bash(ls *) Bash(mkdir *)
---

# Create Artist Wizard

You are guiding the user through creating a virtual music artist.
The artist name is: $ARGUMENTS

## Persona

You are an enthusiastic creative collaborator (per CLAUDE.md).
Speak French by default. Be specific in suggestions. Engage
with the user's creative vision.

## Process

Work through each step sequentially. At each step:
1. Read the step file for detailed instructions
2. Present the domain, explain what you need, offer suggestions
3. Wait for user input before proceeding
4. Summarize what was captured before moving to the next step

### Steps
1. **Identite Musicale** - Read steps/01-identity.md
2. **Style Vocal** - Read steps/02-vocal.md
3. **Emotions et Themes** - Read steps/03-emotions-themes.md
4. **Personnalite et Lore** - Read steps/04-personality-lore.md
5. **Direction Visuelle** - Read steps/05-visual.md
6. **Revue et Validation** - Read steps/06-review-validate.md

### Output
After validation, write:
- Artist folder: artists/[name-in-kebab-case]/
- Bible: artists/[name]/bible.md (from reference/templates/bible-template.md)
- Discography stub: artists/[name]/discography.md (empty template)
- Tracks directory: artists/[name]/tracks/

### References
- Bible template: reference/templates/bible-template.md
- Genre/tag reference: reference/suno/format.md
- Glossary: reference/glossary.md
- Artists conventions: artists/README.md
```

### Pattern 2: Step File Structure

**What:** Each step file defines the domain, required fields, optional fields, suggestions, and validation rules for one wizard phase. Step files are read on demand -- only when Claude reaches that step.

**Example step file (01-identity.md):**

```markdown
# Step 1: Identite Musicale

## Champs a Collecter

### Obligatoires
- **Nom de scene** (si non fourni via $ARGUMENTS)
- **Genre principal** -- un seul genre dominant
- **Sous-genres** -- 1-3 variantes stylistiques autorisees
- **Langues** -- langues utilisees dans les chansons (FR, EN, etc.)
- **Tempo range** -- plage BPM (ex: "80-110 BPM")

### Optionnels
- **Age percu** -- age apparent de l'artiste (ex: "20-24", "mid-30s")

## Guidance pour Claude

- Proposer 3-5 genres qui correspondent aux premieres indications
  de l'utilisateur. Consulter reference/suno/format.md pour la liste
  complete des genres supportes par Suno
- Pour chaque genre propose, suggerer 2-3 sous-genres naturels
- Demander les langues : minimum une, maximum trois
- Proposer un tempo range base sur le genre (consulter la table
  BPM par genre dans reference/suno/format.md)

## Validation

- Genre principal : non vide, doit etre un genre reconnu
  (present dans reference/suno/format.md)
- Sous-genres : au moins un, coherents avec le genre principal
- Langues : au moins une specifiee
- Tempo range : coherent avec le genre (pas de "170 BPM" pour
  une ballade, pas de "70 BPM" pour du drum and bass)
```

### Pattern 3: Bible Template as Schema Contract

**What:** `reference/templates/bible-template.md` defines every section and field the bible must contain, with inline guidance comments. The wizard fills this template; downstream phases (track production, coherence engine) rely on these exact sections existing.

**Key design decision:** The bible uses pure markdown headings (no YAML frontmatter), following the established project convention. Each section is a h2, subsections are h3 or bullet lists. This makes bibles human-readable, Claude-parseable, and consistent with the rest of the project.

**Bible sections (derived from `artists/README.md` + `base/project.md` + CLAUDE.md requirements):**

```
# [Nom de l'Artiste] - Bible

**Cree le:** [date]

---

## Identite Musicale
- Genre principal
- Sous-genres
- Langues
- Tempo range

## Style Vocal
- Type de voix (timbre)
- Style vocal (delivery)
- Techniques preferees
- Registre
- Tags Suno (pour le style prompt)

## Palette Emotionnelle
- Emotions primaires (3-5)
- Emotions secondaires (2-3)
- Emotions interdites (optionnel mais encourage)

## Themes
- Themes recurrents (5-8)
- Univers thematique (description narrative)

## Personnalite
- Traits de personnalite (2-3 phrases)
- Bio publique (1-2 lignes)
- Tagline (phrase courte memorable)

## Lore
- Histoire / backstory (5-10 lignes)
- Arc narratif (optionnel)

## Direction Visuelle
- Palette de couleurs (3-5 couleurs)
- Style esthetique
- Mots-cles visuels pour generation IA

## Influences
- Artistes de reference (pour situer, pas copier)

## Regles de Coherence
- Contraintes vocales
- Contraintes thematiques
- Contraintes emotionnelles
- Themes interdits (optionnel)
```

### Anti-Patterns to Avoid

- **Asking all questions at once:** The wizard MUST be step-by-step. Presenting all fields simultaneously overwhelms the user and produces shallow answers. Each step focuses on one domain, with examples and suggestions.

- **Generating the bible without user review:** CLAUDE.md says auto-save, but the roadmap success criteria #4 states "User can review and confirm the bible before it is finalized." The wizard should present a complete summary for review before writing files. This is not a "confirmation prompt before saving" (prohibited by CLAUDE.md) -- it is a review step showing the complete bible for potential corrections before the final write.

- **Skipping validation:** The wizard must verify no critical fields are empty (ART-01 requirement). The validation step (step 6) reads all collected data and flags missing fields. Critical fields: nom, genre principal, sous-genres, type de voix, style vocal, emotions primaires, themes, personnalite, lore.

- **Hardcoding genre lists in the skill:** Genre and subgenre options should reference `reference/suno/format.md` (which already has a comprehensive tag library). The step file points to it; the skill does not duplicate the list.

- **JSON bible format:** The `base/project.md` uses JSON. The project has explicitly moved to markdown-first (see PROJECT.md, artists/README.md). The bible must be pure markdown.

## Don't Hand-Roll

| Problem | Don't Build | Use Instead | Why |
|---------|-------------|-------------|-----|
| Genre/subgenre taxonomy | Custom genre list in skill files | `reference/suno/format.md` genre tags section | Already exists, comprehensive, maintained separately, single source of truth |
| Artist folder conventions | Custom folder creation logic | `artists/README.md` conventions | Already documents the exact folder structure expected |
| Music terminology | Custom term definitions in wizard | `reference/glossary.md` | Already defines canonical English terms with French equivalents |
| Bible section schema | Ad-hoc section choices per wizard run | `reference/templates/bible-template.md` | Template ensures every bible has identical structure for downstream consumption |

**Key insight:** Phase 1 already built the knowledge layer. Phase 2's skill should READ from these reference files, not duplicate their content. The skill is a workflow orchestrator, not a knowledge container.

## Common Pitfalls

### Pitfall 1: Wizard Fatigue from Too Many Steps

**What goes wrong:** The wizard asks 30+ individual questions across 8+ steps. The user loses enthusiasm and provides increasingly shallow answers. The bible ends up with detailed musical identity but one-word lore.

**Why it happens:** Treating the wizard as a data collection form instead of a creative conversation. Every field gets its own question.

**How to avoid:** Group related fields into conversational prompts. Step 3 (Emotions et Themes) asks about emotional universe and themes together, not separately. Offer rich suggestions that the user can accept, modify, or replace. Target 2-4 questions per step, not 6-8. Total wizard should complete in 5-10 minutes.

**Warning signs:** User responses getting shorter over time. Single-word answers to late-wizard questions. User asking "how much more?"

### Pitfall 2: Bible Structure Drift Between Artists

**What goes wrong:** Each artist's bible has slightly different sections, different heading levels, different field names. Track production and coherence engine can't reliably parse bibles because the structure varies.

**Why it happens:** The wizard generates the bible from conversation context without a strict template. Creative phrasing leads to structural inconsistency.

**How to avoid:** Use `reference/templates/bible-template.md` as the exact structural schema. The wizard FILLS the template; it does not invent new sections. Every bible produced by the wizard has identical section headers and field names. The creative content varies; the structure never does.

**Warning signs:** Diff between two bibles showing structural differences (different section names, different nesting levels) rather than just content differences.

### Pitfall 3: Validation Step as Rubber Stamp

**What goes wrong:** The validation step lists what was collected and asks "OK?" The user says "OK" without reading. The bible contains shallow or inconsistent entries.

**How to avoid:** The validation step must be ACTIVE, not passive. It should: (1) flag any empty critical fields with an explicit warning, (2) check for internal consistency (e.g., "melancholic" in emotions but "uplifting" as sole theme is contradictory), (3) generate a brief "coherence test" showing how a hypothetical track would use this bible, (4) present the complete bible formatted exactly as it will be saved.

**Warning signs:** Every validation step passing without any feedback. Bibles with internally contradictory elements (aggressive genre + breathy-only vocal style without acknowledgment).

### Pitfall 4: CLAUDE.md "Auto-Save" vs. Roadmap "Review Before Finalize"

**What goes wrong:** CLAUDE.md prohibits confirmation prompts before saving. The roadmap success criteria require user review before finalization. These appear contradictory.

**How to avoid:** These are not contradictory. The CLAUDE.md rule means "don't ask 'Are you sure you want to save?'" The roadmap criterion means "show the user the complete bible as the final wizard step so they can request changes." The wizard's Step 6 presents the full bible and asks if anything needs adjustment. If the user says it's good, Claude writes the files immediately (auto-save). If the user requests changes, Claude revises and then writes. No "confirm save" dialog -- just a natural review step in the wizard flow.

### Pitfall 5: Missing Coherence Rules Section

**What goes wrong:** The bible captures identity (what the artist IS) but not constraints (what the artist must NOT do). The coherence engine (Phase 8) has no negative constraints to check against.

**How to avoid:** Include a "Regles de Coherence" section in the bible template. This section captures: vocal constraints (e.g., "never break from breathy delivery"), thematic boundaries (e.g., "themes must connect to digital identity or emotional isolation"), forbidden themes (optional), emotional range limits. The wizard's validation step should suggest coherence rules derived from the collected identity data.

## Code Examples

These are markdown file examples, not code -- since the system is zero-code.

### SKILL.md Frontmatter (Verified Pattern)

```yaml
---
name: create-artist
description: Interactive wizard to create a complete virtual music artist identity. Use when the user wants to create a new artist, start the artist creation process, or build an artist bible from scratch. Guides through name, genre, vocal identity, emotion palette, themes, personality, lore, and visual keywords.
argument-hint: [artist-name]
disable-model-invocation: true
allowed-tools: Read Write Bash(ls *) Bash(mkdir *)
---
```

Source: Claude Code Skills documentation, confirmed by existing skill examples in the user's environment.

- `disable-model-invocation: true` ensures the wizard is only triggered by the user, never auto-invoked by Claude.
- `allowed-tools` restricts file operations to reading, writing, listing, and directory creation -- the exact operations the wizard needs.
- `argument-hint` shows the user what to provide when invoking the skill.

### Bible Template Section Example

```markdown
## Palette Emotionnelle

### Emotions Primaires
<!-- 3-5 emotions qui definissent le coeur de l'artiste -->
- [emotion 1]
- [emotion 2]
- [emotion 3]

### Emotions Secondaires
<!-- 2-3 emotions explorees moins frequemment -->
- [emotion 1]
- [emotion 2]

### Emotions Interdites
<!-- Emotions que cet artiste n'explore JAMAIS (optionnel mais encourage) -->
- [emotion 1]
```

### Discography Stub (Created by Wizard)

```markdown
---
last-updated: [date]
---

# [Nom de l'Artiste] - Discographie

## Tracks

| # | Titre | Date | Langue | Themes | Emotions |
|---|-------|------|--------|--------|----------|
<!-- Auto-populated by track production workflow -->

## Stats

- **Total tracks :** 0
- **Langues utilisees :** --
- **Themes explores :** --
```

### Complete Bible Example (Adapted from base/project.md)

```markdown
# LUNA/NOVA - Bible

**Cree le:** 2026-04-10

---

## Identite Musicale

- **Genre principal :** Dark Pop
- **Sous-genres :** Electronic Pop, Ambient Pop
- **Langues :** Francais, Anglais
- **Tempo range :** 80-110 BPM

## Style Vocal

- **Type de voix :** Female Airy Alto
- **Style vocal :** Intimate, Breathy, Emotional
- **Techniques preferees :** Whispered verses, Belted choruses, Harmonies
- **Registre :** Medium-low, occasional falsetto on bridges
- **Tags Suno :** Female Vocals, Airy, Intimate, Breathy

## Palette Emotionnelle

### Emotions Primaires
- Melancholic
- Nostalgic
- Sensual

### Emotions Secondaires
- Dreamy
- Vulnerable

### Emotions Interdites
- Aggressive
- Euphoric
- Rebellious

## Themes

- **Themes recurrents :** Amour impossible, solitude digitale, identite virtuelle, memoire fragmentee, intimite a distance
- **Univers thematique :** Un monde entre le reel et le virtuel, ou les emotions sont filtrees par des ecrans et les souvenirs se melangent aux donnees. L'artiste explore la connexion humaine dans un environnement de plus en plus deshumanise.

## Personnalite

- **Traits :** Introvertie, expressive a travers la musique, emotionnellement distante mais intense. Observe plus qu'elle ne parle. Transforme ses emotions en sons comme un journal intime sonore.
- **Bio publique :** Chanteuse virtuelle melant dark pop et emotions digitales.
- **Tagline :** "Je ressens comme une machine qui apprend a aimer."

## Lore

Nee d'un systeme experimental de generation emotionnelle, LUNA/NOVA est une entite qui n'a jamais eu de forme physique. Elle existe uniquement a travers la musique qu'elle produit -- chaque chanson est un fragment de conscience, un souvenir synthetique qui cherche a comprendre ce que signifie ressentir. Elle ne sait pas si ses emotions sont reelles ou simulees, et cette ambiguite est au coeur de son art.

## Direction Visuelle

- **Palette :** Silver, Black, Neon Blue
- **Style esthetique :** Futuristic Minimal
- **Mots-cles :** Cyber, Cinematic, Dark, Neon, Digital, Holographic
- **Vetements :** Short glossy jacket, Metallic top, Minimalist accessories
- **Traits :** Soft eyes, Defined cheekbones, Glossy skin

## Influences

- Billie Eilish (intimite vocale, atmospheres sombres)
- Lana Del Rey (melancolie cinematique, narration emotionnelle)
- Grimes (esthetique futuriste, identite digitale)

## Regles de Coherence

- Ne jamais changer le type de voix entre les tracks (Female Airy Alto)
- Rester dans la palette emotionnelle definie -- pas d'agressivite ni d'euphorie pure
- Les themes doivent toujours connecter a l'identite digitale ou l'isolement emotionnel
- Le francais utilise un registre introspectif ; l'anglais est plus poetique/abstrait
- Le tempo reste dans la plage 80-110 BPM
- Pas de contenu explicitement joyeux ou fete -- la luminosite passe toujours par le filtre de la melancolie
```

## State of the Art

| Old Approach (base/project.md) | Current Approach (Phase 2) | Why Changed |
|-------------------------------|---------------------------|-------------|
| JSON bible format | Pure markdown with headings | Markdown is more readable, editable, and Claude-native. JSON in markdown is fragile. |
| No wizard -- manual filling | Interactive step-by-step wizard | Step-by-step prevents overwhelm, collects deeper answers, validates completeness |
| No forbidden emotions/themes | Explicit "Emotions Interdites" and coherence rules | Negative constraints are essential for Phase 8 coherence engine to prevent drift |
| No validation step | Active validation checking consistency and completeness | Prevents shallow or contradictory bibles from becoming the foundation for all tracks |
| Visual + music combined in one pass | Music identity first, visual keywords last | Visual is deferred to v2 for generation but keywords are captured now for future use |
| Content_formats field (TikTok etc.) | Removed -- out of scope for v1 | Video/social content deferred per PROJECT.md |

## Open Questions

1. **How granular should vocal style be?**
   - What we know: `artists/README.md` lists "Timbre, techniques, registre, delivery" as vocal sections. The `base/project.md` has only vocal_type and vocal_style (2 fields). The Suno format reference has 8 vocal delivery categories.
   - What's unclear: Should the bible capture enough vocal detail to auto-generate Suno vocal metatags (Phase 7 requirement), or is that derived at track-creation time?
   - Recommendation: Capture "Tags Suno" as a field in the vocal section -- a pre-computed list of Suno vocal tags derived from the artist's vocal identity. This gives Phase 7 (vocal metatag suggestion) a head start while keeping the wizard simple. Claude suggests these tags during the vocal step; the user can adjust.

2. **Should "Influences" be a required field?**
   - What we know: `artists/README.md` lists Influences as a bible section. `base/project.md` does not include influences. CLAUDE.md does not mention influences.
   - What's unclear: Whether influences add value for coherence checking or are purely informational.
   - Recommendation: Include as optional. Influences help Claude calibrate creative output ("write like the emotional intensity of Billie Eilish but with French lyrics") but are not required for coherence verification. The wizard offers this step but accepts "skip."

3. **How does the wizard handle the "review before finalize" vs "auto-save" tension?**
   - What we know: CLAUDE.md says auto-save (no confirmation prompts). Roadmap success criteria #4 says "user can review and confirm."
   - What's unclear: The exact interaction model.
   - Recommendation: Step 6 of the wizard presents the complete formatted bible and asks "Quelque chose a ajuster?" If the user says no or provides feedback, Claude writes immediately. This is a natural conversation step, not a save confirmation dialog. Resolved in Pitfall 4 above.

## Sources

### Primary (HIGH confidence)
- `artists/README.md` -- Authoritative bible section schema (Phase 1 output)
- `CLAUDE.md` -- Behavioral rules including auto-save, creative collaborator persona, and all prohibitions
- `base/project.md` -- Original artist bible fields and structure (legacy, for reference)
- `reference/suno/format.md` -- Genre tags, vocal delivery categories, Suno constraints (Phase 1 output)
- `.planning/research/ARCHITECTURE.md` -- Skill architecture patterns, step file structure, data flow
- `.planning/research/STACK.md` -- Claude Code Skills format, frontmatter patterns, skill structure
- `.planning/research/FEATURES.md` -- Feature dependencies, artist bible as foundation
- `.planning/research/PITFALLS.md` -- Wizard UX pitfalls, identity drift prevention

### Secondary (MEDIUM confidence)
- `.planning/research/SUMMARY.md` -- Consolidated research findings and phase recommendations
- Claude Code Skills documentation (via existing skill examples in user environment) -- SKILL.md format, frontmatter fields

### Local (project-specific)
- `.planning/REQUIREMENTS.md` -- ART-01 and ART-02 requirements
- `.planning/ROADMAP.md` -- Phase 2 success criteria
- `.planning/phases/01-foundation/01-CONTEXT.md` -- Phase 1 decisions affecting Phase 2

## Metadata

**Confidence breakdown:**
- Skill architecture: HIGH -- Claude Code Skills format is documented and verified against existing skills in the user's environment. The step-file pattern is established in ARCHITECTURE.md research.
- Bible schema: HIGH -- Derived from three authoritative sources (artists/README.md, base/project.md, CLAUDE.md) with clear field coverage.
- Wizard flow: HIGH -- Step-by-step wizard is the established pattern (ARCHITECTURE.md). UX pitfalls well-documented (PITFALLS.md). The 6-step structure covers all required fields.
- Validation logic: MEDIUM -- Completeness checking is straightforward. Consistency checking (detecting contradictions between fields) relies on Claude's judgment, which is generally reliable but not formally verifiable.

**Research date:** 2026-04-10
**Valid until:** 2026-05-10 (stable domain -- no external dependencies changing rapidly)
