Governance Map — Printable Reference
Use this as a light architecture reference. It is not the weekly board.
Routing Architecture
Weekly Board
-> route ID / checkbox / annotation
-> governance contract
-> route card
-> digital support index
-> state source
-> evidence / next pointer
Core Routes
| ID | Domain | Use |
|---|---|---|
| WEEK-GOV | Weekly governance | Frame the week and active routes |
| BOOT | Daily execution | Start the day without reconstructing context |
| MAINT | Maintenance | Reduce friction and prepare execution |
| FOCUS | Deep work | Produce evidence |
| CLOSE | Daily close | Prevent context loss |
| NEXT | Continuity | Make restart cheap |
Weekly / State Routes
| ID | Domain | Use |
|---|---|---|
| CARRY-M | Project state | Micro project update |
| CARRY-W | Project state | Weekly project reconciliation |
| FIN-W | Finance | Weekly finance review |
| FIN-U | Finance | Urgent finance item |
| EXTERNAL | Externalization | Send, publish, contact, request feedback |
Homeostasis Routes
| ID | Domain | Use |
|---|---|---|
| BODY-GOV | Body / health | Log useful body signals |
| GYM-GOV | Gym / movement | Keep training governed |
| HOUSE-GOV | House ops | Keep environment from drifting |
| CLN-30 | Cleaning | 20-30 minute bounded reset |
Capture
| ID | Domain | Use |
|---|---|---|
| CAPTURE-GOV | Capture | Route free notes inside review/capture |
| CAPTURE-ROUTER | Capture | Action / state / archive / waiting / discard |
Rule
The weekly board shows IDs. The route cards define action. The support index gives links. State sources hold truth. Evidence proves movement.