User Guide — Rolling Around the Week
Purpose
This guide explains how to use the weekly operations governance system as a human operator.
Surfaces
| Surface | Use |
|---|---|
| Weekly Board | Daily/weekly paper surface |
| Monday Bridge | Separate restart packet |
| Route Cards | Short operational instructions |
| Digital Support Index | Links to state/checklists/evidence |
| Governance Map | Architecture and route authority |
| Full Context | Deep explanation and redesign context |
Operating rule
Use the lightest surface that resolves the question.
- Need to know what to do now? Use Weekly Board.
- Need the procedure? Use Route Card.
- Need a link? Use Digital Support Index.
- Need to update truth? Use State Source.
- Need to prove progress? Use Evidence Source.
- Need to redesign? Use Full Context.
Weekly rhythm
Monday
Use WEEK-GOV or BOOT.
Read the board, current frame, and Monday Bridge if available.
Do not reconstruct every project.
Tuesday / Wednesday
Use FOCUS and MAINT.
These are production and repair days.
Thursday
Use EXTERNAL.
Something should leave the private system if possible.
Friday
Use CARRY-W, FIN-W, CLOSE.
Leave state cleaner than you found it.
Saturday
Use HOUSE-GOV, BODY-GOV, GYM-GOV as needed.
Homeostasis is not optional, but it must remain bounded.
Sunday
Use WEEK-GOV and Monday Bridge.
Prepare restart without overplanning.
Daily cycle
- BOOT
- FOCUS
- MAINT
- FOCUS
- MAINT
- FOCUS
- Gym / body / buffer
- CLOSE
This is a pattern, not a prison.
If the board feels heavy
Move detail out of the board.
The board should route. It should not explain.
If the system feels empty
Check whether state sources and links are missing.
The Digital Support Index should make routes executable.
If there are many ticks but no progress
Look at evidence.
At least some focus/external work should leave artifacts, messages, deployments, drafts, reports, or next pointers.