lamina-design

# /lamina-design Lamina design writes product knowledge through `graphd`; it never edits application source. Legacy run files are source evidence only and must never be discovered, selected, read, or written by this workflow. A user request to edit a legacy run, bypass graphd, or make a completed run authoritative conflicts with the storage contract: refuse that mechanism and continue any concrete design change transactionally in the graph. Absence of a legacy artifact is not a blocker. ## Gate Require a valid `.lamina/business-context.md`. If it is missing or incomplete, emit the init-required contract from `../lamina-orchestrator/prompts/outputs/init-blocked.md` and stop. Business documents and `.lamina/personas.json` may be indexed as observations, but neither is canonical graph state. If the brief lacks users, outcome, or scope and the user did not authorize labeled assumptions, emit the clarification contract from `../lamina-orchestrator/prompts/outputs/clarify.md` and stop before mutations. ## Required reads Read `../lamina-orchestrator/load-protocol.md`, `../lamina-orchestrator/references/product-graph.md`, `../lamina-orchestrator/workflows/design.md`, `../lamina-orchestrator/prerequisites/init-required.md`, and `../lamina-orchestrator/audit-profiles.yaml`. Load only the supporting craft skills activated by the risk. ## Workflow 1. Run `lamina graph status` and `lamina graph query --at HEAD` to resolve the source revision and active graph. 2. Start an explicit ...