coulomb/config-atlas
2
0
Fork 0
generated from coulomb/repo-seed
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: add config-atlas Product Requirements Document

Browse Source 
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>
This commit is contained in:
Bernd Worsch
2026-06-26 22:37:06 +02:00
parent dd5b405300
commit 05fa73e20f
3 changed files with 558 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/ecosystem-boundaries.md
View File

@@ -3,7 +3,7 @@
> How config-atlas should tighten its responsibility boundaries and reuse existing
> concepts/functionality from five sister repos rather than reinventing them.
> Drafted 2026-06-26. Companion to [`INTENT.md`](../INTENT.md),
> [`SCOPE.md`](../SCOPE.md), [`ArchitectureBlueprint.md`](../ArchitectureBlueprint.md),
> [`SCOPE.md`](../SCOPE.md), [`ArchitectureBlueprint.md`](../specs/ArchitectureBlueprint.md),
> and [`.claude/rules/repo-boundary.md`](../.claude/rules/repo-boundary.md).
---