Part 3 · Operate
Approvals
Keyboard-first review. Four keys and a queue that should be short.
01What it is
The review queue. Everything that cleared the gates and needs a human, worked with the keyboard.
02Why it exists
Review is the one task you will do every day, so it is built for speed rather than for browsing. The queue should be short, because the gates and the revision loop already removed everything that would waste your time.
A long queue means something upstream is wrong. Usually a thin context or a missing voice profile.
03How to use it
- 01Use j and k to move, a to approve, e to edit, x to reject, and ? for the list.
- 02Reject with a reason. The loop reads it.
- 03Edit when the substance is right. Your edit is signal too.
- 04If the queue is long, fix the context rather than working faster.
04What good looks like
- You give it
- Six drafts a day, four approved without editing.
- You get
- Ten minutes of review, and the edit rate tells you when to raise your autonomy stage.
- Why
- The gates removed the rest before you saw them.
Derived from the rules in the code
05What weak looks like, and what it costs
- You give it
- Forty drafts a day, most of them edited heavily.
- You get
- An hour of review and no improvement, because heavy edits without a reason teach the loop nothing.
- Why
- The revision loop reads rejections with reasons. A silent rewrite is invisible to it.
Derived from the rules in the code