Review & approve

Approvals are the only moment Lumen interrupts you. Everything risky waits for your OK; everything else just happens.

What needs approval

By default, a crew asks before it:

• deploys anything, anywhere,
• runs a command that isn't on the allowed list,
• deletes files or branches,
• sends anything outside your machine except calls to model providers.

Change the list in Settings & permissions.

What you see

An approval request always comes from the manager and always has the same parts:

1. SummaryOne or two sentences on what will happen.
2. TrailThe handoffs that led here, as a short sequence: who found, who built, who tested.
3. EvidenceDiff, test results and any risk the crew noticed.
4. ActionsApprove, Reject with a note, or Ask a question.

Where approvals appear

In the app's Waiting for you list, as a macOS notification, and in the manager's direct message. Approving from the notification works even when Lumen is in the background.

Rejecting well

A rejection goes back to the manager with your note. Be specific; the note becomes part of the next handoff and often of a lesson in memory.

Not yet: the migration locks the users table.
Make it run in batches of 1,000.