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.
A confirmed model is the authorized set of purposes, behaviors, and choices. Its authoritative
specifications are the single persisted home: CONCEPT for concepts, SYNCS for coordination, and the
overall PRD for global relations. Preserve both design arguments—contract → OP → concept purpose,
and selection/sync → application scenario → application purpose—and their assumptions. Acceptance
scenarios derive from OPs or behavioral contracts and never invent requirements.
Transcribe
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.
Choose locations — Use the following layout. Stage centrally only until modules exist.
docs/prd/README.md
<module>/CONCEPT.md or docs/prd/concepts/<name>.md
<syncs>/SYNCS.md or docs/prd/SYNCS.md
Write the overall PRD — Preserve application purpose, end-to-end scenarios and their
concept/sync basis, misfits, concept index with purpose and links, synchronization graph, product
dependencies and subsets, exclusions, and open decisions. Put cross-concept assumptions and
arguments here.
Write specifications and acceptance — Read references/spec-format.md and
references/templates.md. Preserve the four CONCEPT sections, concept-local assumptions, and
purpose argument; put application context in notes. Transcribe app/include/sync into one SYNCS
file grouped by entry point or rule responsibility with // flow:. Derive acceptance separately
from concept OPs, application scenarios, and behavioral contracts, each with provenance. Mark
missing application goals as open rather than constructing them from concept purposes.
Update consistently — Make minimal edits to existing documents, refresh indexes and derived
diagrams, and preserve human-maintained content. Leave implementation-time migration and sync
package splitting to concept-implementation.
Completion requires one authoritative location per model element; no lost definitions, relations,
assumptions, exclusions, or open decisions; independent CONCEPT sections; application instantiation
in SYNCS rather than legacy interactions/dependencies sections; acceptance linked to OP, application
scenario, or contract evidence; real sync declarations for every parameter, binding, and output;
preserved reachable failure behavior and empty-query semantics; and valid global links.
For the first transcription read references/example-reserving.md; for specification sources read
references/sources.md.
1---2name: concept-prd-23description: Transcribes a confirmed concept model into traceable PRD and colocated specification files only when the user explicitly invokes $concept-prd. Use to preserve purposes, behavior, synchronizations, assumptions, exclusions, open decisions, and acceptance provenance without redesigning the model.4---56# Concept PRD78Focus: how can a confirmed model be persisted without losing purpose, behavior, or acceptance9traceability? Run only on explicit `$concept-prd` invocation. Input includes concepts,10synchronizations, dependencies, exclusions, and open decisions. Route model gaps to `concept-design`11and code realization to `concept-implementation`.1213A confirmed model is the authorized set of purposes, behaviors, and choices. Its authoritative14specifications are the single persisted home: CONCEPT for concepts, SYNCS for coordination, and the15overall PRD for global relations. Preserve both design arguments—contract → OP → concept purpose,16and selection/sync → application scenario → application purpose—and their assumptions. Acceptance17scenarios derive from OPs or behavioral contracts and never invent requirements.1819## Transcribe20211. **Verify input** — Read the confirmed model, requirement sources, and existing documents. Inspect22 code only for module locations and indexing facts. Never let implementation differences silently23 rewrite the model.242. **Choose locations** — Use the following layout. Stage centrally only until modules exist.2526 ```text27 docs/prd/README.md28 <module>/CONCEPT.md or docs/prd/concepts/<name>.md29 <syncs>/SYNCS.md or docs/prd/SYNCS.md30 ```31323. **Write the overall PRD** — Preserve application purpose, end-to-end scenarios and their33 concept/sync basis, misfits, concept index with purpose and links, synchronization graph, product34 dependencies and subsets, exclusions, and open decisions. Put cross-concept assumptions and35 arguments here.364. **Write specifications and acceptance** — Read `references/spec-format.md` and37 `references/templates.md`. Preserve the four CONCEPT sections, concept-local assumptions, and38 purpose argument; put application context in notes. Transcribe app/include/sync into one SYNCS39 file grouped by entry point or rule responsibility with `// flow:`. Derive acceptance separately40 from concept OPs, application scenarios, and behavioral contracts, each with provenance. Mark41 missing application goals as open rather than constructing them from concept purposes.425. **Update consistently** — Make minimal edits to existing documents, refresh indexes and derived43 diagrams, and preserve human-maintained content. Leave implementation-time migration and sync44 package splitting to `concept-implementation`.4546Completion requires one authoritative location per model element; no lost definitions, relations,47assumptions, exclusions, or open decisions; independent CONCEPT sections; application instantiation48in SYNCS rather than legacy interactions/dependencies sections; acceptance linked to OP, application49scenario, or contract evidence; real sync declarations for every parameter, binding, and output;50preserved reachable failure behavior and empty-query semantics; and valid global links.5152For the first transcription read `references/example-reserving.md`; for specification sources read53`references/sources.md`.
ontology-of-everything