Challenge system assumptions against accumulated evidence. Triages observations and tensions, detects patterns, generates proposals. The scientific method applied to this vault. Triggers on "/review", "review observations", "challenge assumptions", "what have I learned".
Read ops/derivation-manifest.md, ops/config.yaml, and all files in ops/methodology/.
Target: $ARGUMENTS
START NOW.
The system is not sacred. Evidence beats intuition. Observations in ops/observations/ and tensions in ops/tensions/ are evidence from actual use. This command triages them and proposes system changes when patterns emerge.
Rule Zero: ops/methodology/ is the canonical spec. Before triaging observations, check whether the system has drifted from what the methodology says.
Read all files in ops/methodology/. Compare against:
Flag any drift. Drift that isn't caught becomes technical debt.
Read all pending observations in ops/observations/ (status: pending).
For each observation, triage:
Read all pending tensions in ops/tensions/ (status: pending).
For each tension, triage:
After triage, look at what was promoted and implemented. Are there patterns?
For each pattern detected, generate a concrete proposal:
NEVER auto-implement. Always propose for approval.
## Review Complete
### Drift Check
[No drift detected | Drift found: description]
### Observations Triaged: N
| Observation | Action | Notes |
|-------------|--------|-------|
| [title] | PROMOTE / IMPLEMENT / ARCHIVE | [details] |
### Tensions Triaged: M
| Tension | Action | Notes |
|---------|--------|-------|
| [title] | RESOLVED / DISSOLVED / KEEP | [details] |
### Patterns Detected
[Pattern description → proposed change]
### Proposals (requiring approval)
**Proposal 1: [title]**
Evidence: [observations/tensions supporting this]
Proposed change: [what specifically would change]
Approve? (yes/no/modify)