concept-prd

# Concept PRD Focus: how can a confirmed model be persisted without losing purpose, behavior, or acceptance traceability? Run only on explicit `$concept-prd` invocation. Input includes concepts, synchronizations, dependencies, exclusions, and open decisions. Route model gaps to `concept-design` and code realization to `concept-implementation`. ## Transcription Principles CONCEPT owns the confirmed concept contract, SYNCS the coordination, and the overall PRD global relations. Keep one authoritative location per element. Preserve both arguments and assumptions: contract → OP → concept purpose; selection/sync → application scenario → application purpose. Derive acceptance with provenance; complete files cannot repair model gaps. **Synchronization may restrict behavior, never extend the contract**: record application restrictions in SYNCS/the overall PRD while preserving the concept's allowed behavior. Flag contract-violating coordination as a model gap for design revision. ## Transcribe 1. **Verify input** — Read the confirmed model, requirement sources, and existing documents. Inspect code only for module locations and indexing facts. Never let implementation differences silently rewrite the model. 2. **Choose locations** — Use the following layout. Stage centrally only until modules exist. ```text docs/prd/README.md <module>/CONCEPT.md or docs/prd/concepts/<name>.md <syncs>/SYNCS.md or docs/prd/SYNCS.md ``` 3. **Write the overall PRD** — Preserve ...