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:
2026-06-08 13:55:27 +02:00
parent 4acf23f4f4
commit 1c0c0efc56
53 changed files with 483 additions and 12 deletions

13
demand/README.md Normal file
View File

@@ -0,0 +1,13 @@
# demand/
Inbound feature requests, requirements, suggestions, and improvement
opportunities that have **not** been systematically reviewed and captured in
`spec/` or `workplans/`.
Material here may be raw and needs scrutiny before implementation picks it up.
## Current Items
| Date | File | Summary |
|------|------|---------|
| 2026-06-08 | `260608-netkingdom-integration-requirements.md` | Integration contracts needed from user-engine and net-kingdom for L2L4 access modes |