Design Studio

Role boundaries

• Visual Director never receives HTML, CSS, JSX, selectors, implementation diffs or the unattended assignment index.
• Evaluator never receives source, implementation effort, full design description or prior scores. Document evaluation also excludes renderer identity/build metadata.
• Builder implements the selected direction; it may not quietly replace it with a safer one.
• Orchestrator is the sole decision owner. Evaluators/reviewers provide evidence, not workflow decisions.

Load and route

1. Load

   invocation.md

   for host input mapping and isolated-role rules.
2. Load

   workflow.yaml

   for the interactive Studio lifecycle and shared schemas/budgets/decisions.
3. Load

   runtime-contract.md

   ,

   references/context.md

   and

   references/runtime-integrity.md

   for deterministic operations and run truth.
4. Read

   method-router.json

   . Every populated signal dimension on a route is required; load the union of matching

   leaves

   . If the route declares

   procedure

   , run that progressively disclosed procedure after its leaves.
5. Never load the full specialist catalog by default.

method-router.json

Required references

• invocation.md

• workflow.yaml

• runtime-contract.md

• method-router.json

• references/context.md

• references/runtime-integrity.md

• Conditional Document procedure:

  references/document/document.md

Lanes

workflow.yaml

references/review/polish.md

references/document/document.md

references/meta.md

Studio

workflow.yaml

• Prove repository/app/context roots and actual capabilities before planning.
• Separate product truth, copy authority and proven visual authority.
• Commit unattended candidate assignment before direction generation and hide it from Visual Director.
• Generate materially different viable directions; user choice or precommitted assignment selects.
• Builder implements the source-free direction. Local mechanical evidence runs before blind browser evaluation.
• Evaluator uses required live viewports without source/prior scores. Orchestrator alone decides.
• Preserve evaluated builds/evidence. Acceptance names the final tree before codification.

Document

references/document/document.md

• A4 is default; Letter and explicit physical sizes are supported without binding the visual model to a renderer.
• Visual Director/Evaluator may receive rendered page images, never document source, renderer identity or implementation rationale.
• Reuse hierarchy and generated-specificity methods, then the Document pagination, table, furniture and print lenses. Interaction/motion review does not apply.
• Rendering/export is optional host capability. Without complete page evidence, creation preserves one build and halts unselected; review returns visual status unverified.
• Accepted Document work may emit

  harness-output/design-system/document-visual-contract.json

  for downstream document-generation skills.

Review

references/review/polish.md

unverified

Evidence and degradation

• roots.json

  /

  capabilities.json

  are operational truth;

  events.jsonl

  is append-only recovery truth.

• PRODUCT.md

  stores confirmed product truth;

  COPY.md

  durable language rules;

  DESIGN.md

  only proven accepted visual authority.
• Mechanical snapshots are complete current-state evidence. Missing evidence is explicit, never a pass.
• Acceptance, not directory existence or a high score, proves authority.

• Missing browser in Studio: one build + mechanical evidence, then halt without winner.
• Missing interactive viewport in Review: partial evidence, visual status unverified.
• Missing complete pages in Document: never infer quality from source; follow the Document failure contract.
• No user-answer mechanism: use precommitted deterministic assignment.
• No image generation: use equally specified text directions.
• Any failed/missing operation is recorded with exact reason.

Method ownership