Add specs/ProductRequirementsDocument.md: hybrid product PRD (sister-repo
skeleton plus the template's Formal Standards / Related Concepts /
Appendix sections), heavy FR/NFR with Requirement/Details/Acceptance
triplets, Canon Alignment, 12 functional + 8 non-functional requirements,
conceptual model, MVP, roadmap, risks, and orientation-map appendix.
Substance traces to INTENT, ArchitectureBlueprint, ecosystem-boundaries,
and the research digest; no scope invented beyond repo-boundary.
Fix relative links broken by the ArchitectureBlueprint.md move into
specs/ (its own INTENT/SCOPE/research links and the ecosystem-boundaries
back-reference).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add docs/ecosystem-boundaries.md: per-repo boundary table, overlap
hotspots and resolutions (control-plane/scope/resolver vs
feature-control, vocabulary vs info-tech-canon, connectors vs
repo-scoping, ownership vs domain-tree, schema/federation vs
reuse-surface), and concrete reuse actions mapped to the blueprint
roadmap.
Tighten .claude/rules/repo-boundary.md to name all five sister repos
with their consume/reuse/reference/link relationships and scope
config-atlas to its novel core.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
