48 lines
1.1 KiB
Markdown
48 lines
1.1 KiB
Markdown
# Review Rhythm
|
|
|
|
## Purpose
|
|
|
|
The review rhythm keeps the system useful without turning it into bureaucracy.
|
|
|
|
## Daily Capture
|
|
|
|
Goal: remove pressure from memory.
|
|
|
|
Suggested practice:
|
|
|
|
- Capture loose items in `inbox/`.
|
|
- Do not classify everything immediately.
|
|
- Do not convert ideas into commitments during capture.
|
|
|
|
## Weekly Review
|
|
|
|
Goal: restore orientation.
|
|
|
|
Suggested checks:
|
|
|
|
- What is active?
|
|
- What is critical?
|
|
- What is waiting?
|
|
- What became noisy but not important?
|
|
- What should be moved from inbox into an area card?
|
|
- What should be explicitly parked as incubating?
|
|
|
|
Use `templates/weekly-review.md`.
|
|
|
|
## Monthly Landscape Review
|
|
|
|
Goal: prevent drift.
|
|
|
|
Suggested checks:
|
|
|
|
- Are activation levels still correct?
|
|
- Is Binky still A3, or has it stabilized?
|
|
- Is Helix moving the production capability forward?
|
|
- Is Coulomb migration clearer?
|
|
- Are Sloppers, WhyWhyNot, and Plenitude still safely incubating?
|
|
- Are any repos/projects creating stress without clear value?
|
|
|
|
## Burnout Guardrail
|
|
|
|
If the system feels heavy, reduce the number of active commitments before adding structure.
|