Approvals and evidence#
Syndicate records provider output, state transitions, approvals and technical evidence. Approval capability differs by adapter; unsupported interactive approval must fail closed rather than silently continue.
Before you start#
- The session uses a provider and mode that supports the intended action.
- The approval request names an exact operation and expiry.
- You can inspect the repository diff independently.
Review the complete command, target and requested authority. Approve only the specific action needed. After completion, inspect events, output and Git diff. Provider output can contain sensitive prompt or repository content, so protect the event database as project data.
Verify#
Confirm an approval cannot be reused, expired approvals fail, and denied work does not change the worktree. Run the project's tests and compare recorded evidence with the actual commits before integration.
If it does not work#
| Symptom | Check | Recovery |
|---|---|---|
| An approval never appears | Whether the session is actually waiting on one | See A session is stuck |
| An approved action does not resume the run | Whether approval ends the current run | Start a follow-up run to interpret the result |
| Evidence is missing for a completed action | What was preserved at the time | Preserve evidence before retrying — a retry can overwrite what explains the first attempt |
| You cannot tell what an action would do | — | Decline it. An approval you cannot evaluate is not an approval |