generated from coulomb/repo-seed
Reorganize documentation into canonical repository layout
Adopt CoulombSocial/HelixForge/MarkiTect documentation structure: - research/260608-yawex-prior-art/ — yawex exploration and sources - demand/ — inbound NetKingdom integration requirements - spec/ — PRD, TSD, UseCaseCatalog, ArchitectureBlueprint scaffolds - docs/ — stakeholder documentation and repository-layout guide - wiki/, issues/, history/ — scaffolded directories Add SCOPE.md and AGENTS.md. Update workplan paths and README.
This commit is contained in:
15
spec/README.md
Normal file
15
spec/README.md
Normal file
@@ -0,0 +1,15 @@
|
||||
# spec/
|
||||
|
||||
Specification files that guide and guardrail implementation.
|
||||
|
||||
Background on document types: InfoTechPrimers on coulomb.social.
|
||||
|
||||
| File | Status | Role |
|
||||
|------|--------|------|
|
||||
| `ProductRequirementsDocument.md` | draft scaffold | What the product must deliver |
|
||||
| `TechnicalSpecificationDocument.md` | draft scaffold | How the system is built |
|
||||
| `UseCaseCatalog.md` | draft scaffold | Observable usage scenarios |
|
||||
| `ArchitectureBlueprint.md` | draft | Access, history, and identity architecture |
|
||||
|
||||
Promote material from `research/` and reviewed items from `demand/` into spec
|
||||
before treating it as implementation authority.
|
||||
Reference in New Issue
Block a user