Solution Strategy
| Driver | Strategy | Detailed view or ADR |
|---|---|---|
| Product knowledge must remain reviewable | Markdown and YAML are canonical; generated graphs and snapshots are disposable | ADR 0001, ADR 0002 |
| Artifacts must remain linkable as files move | Stable identifiers own identity; paths are repository-relative locations | ADR 0003 |
| Proposed product evolution must be inspectable before acceptance | Current model and Product Changes are separate; apply materializes a reviewed proposal on a branch | ADR 0004 |
| Product Definition must work across delivery methods | SDD integrations consume a common product-definition interface rather than defining product semantics | ADR 0005, ADR 0006 |
| Structural verdicts must be reproducible | Deterministic code validates structure; AI supports semantic reasoning; people approve meaning | ADR 0007 |
| Provider files must not become competing sources | Canonical skills and commands render provider-specific managed assets | ADR 0008 |
| Reference docs must track validation schemas | Generate reference material from the same schemas the CLI enforces | ADR 0009 |
The public site follows the same derived-output approach: its model explorer is generated from the accepted model, while informational pages and architecture views are authored in the repository and published as static files.