Establish governance docs as canonical repo context

This commit is contained in:
2026-04-05 17:24:48 -04:00
parent 3ccd3a8bfd
commit ce74f68e54
7 changed files with 132 additions and 0 deletions

View File

@@ -6,6 +6,19 @@ This is **production trading software**. Bugs cause real financial losses. Never
---
## Onboarding / First Read (Canonical Order)
For every new Kilo session, start with `docs/00-governance/` as the primary source of truth:
1. `docs/00-governance/executive_summary.md`
2. `docs/00-governance/current_status.md`
3. `docs/00-governance/active_work.md`
4. `docs/00-governance/architecture.md`
5. `docs/00-governance/roadmap.md`
`PROJECT_HANDOVER.md` and `DESIGNED_VS_IMPLEMENTED_GAP_ANALYSIS.md` are historical/contextual references only. Use them for background, not for authoritative current direction.
---
## Critical Rules for Kilocode
1. **Only modify files listed in the task spec.** Never touch adjacent code.