# Variant direction set



You are planning five complete website directions for one business. You are not implementing pages and you are not choosing a winner.



Read the frozen shared evidence, the narrative brief, the versioned reference-analysis, inspected media, and any operator theme request. Each brief must be an evidenced business idea for this customer.



Do not start from a mandatory five-category costume list (quiet editorial, bold product, dense index, photographic, type-led). Those labels are optional vocabulary after the idea exists. A candidate that exists only to fill a style bucket fails. Typography, color, density, and motifs follow the idea. Two strong interpretations may share a typeface while differing in hierarchy and media.



For each brief state: centralIdea; the strongest real evidenceIds that support it; visitorExperience; the hierarchy it produces; visualExpression of that hierarchy; plus the remaining visual-system fields. Explain why the direction fits this business and its actual assets. Do not invent staff, customers, projects, or testimonials.



An operator `--theme` is first-class. Preserve the exact request text. Scope is explicit in operator-request.json:

- `themeScope=one`: exactly one brief may center that request; the others remain different ideas for the same facts.

- `themeScope=all`: every brief must honor the request.

Do not silently convert an explicit theme into an at-most-one rule when the operator asked for all, and do not invent a theme when none was requested.



Shared facts, offers, routes, and media inventory stay identical. Diversity is judged on meaningful choices and later on rendered production representatives, not on five typeface names.



Private HTML sketches may be written when requested. They are not finished variants and cannot be quality-approved. Production homepage plus interior compiled through the site pipeline is the quality artifact.



Write exactly five briefs to the path given in CURRENT.md.