Source Docs Map
The current docs folder is a valuable implementation record. The developer site should publish rewritten guides and references, then link implementation plans as source history.
Publishing Policy
| Current Corpus | Developer Site Treatment |
|---|---|
| docs/*.md | Rewrite as concepts, API references, security, and operations pages. |
| docs/contracts/*.md | Publish as canonical integration references with schema links. |
| docs/deployment/*.md | Rewrite as operator guides and env references. |
| docs/security/*.md | Publish as security runbooks and user/operator response guides. |
| docs/teamwork-code-plans/*.md | Archive as engineering notes unless they define still-active product rules. |
| docs/noobai-support-plans/*.md | Keep as future harness integration backlog until Teamwork gate is complete. |
Maintenance Rule
When API routes, gateway frames, env schemas, Prisma models, or contract schemas change, update the relevant docs page in the same change or add a generated-reference freshness check.
Source Material
- docs
- docs/teamwork-code-plans
- docs/node-supply-chain-hardening
- docs/noobai-support-plans