|
| 1 | +# Codex autonomous task convergence protocol |
| 2 | + |
| 3 | +## Purpose |
| 4 | + |
| 5 | +Long-running operator tasks must reduce a fixed set of acceptance criteria. They may not multiply tasks, review loops, agents, or verification gates without tying each addition to a newly failed criterion in the authorized manifest. |
| 6 | + |
| 7 | +## Required controls |
| 8 | + |
| 9 | +Each authoritative task records: |
| 10 | + |
| 11 | +- immutable completion-criteria SHA-256; |
| 12 | +- task and operation identifiers; |
| 13 | +- maximum elapsed time; |
| 14 | +- maximum correction cycles; |
| 15 | +- maximum consecutive cycles that do not reduce remaining work; |
| 16 | +- remaining and completed criterion identifiers; |
| 17 | +- whether any external write outcome is uncertain; |
| 18 | +- terminal snapshot evidence. |
| 19 | + |
| 20 | +Subagents remain disabled on the authoritative guarded route. Parallel local analysis requires separately authorized provider-neutral manifests. |
| 21 | + |
| 22 | +Run: |
| 23 | + |
| 24 | +```bash |
| 25 | +node scripts/operator/codex-task-convergence-guard.mjs \ |
| 26 | + --input /approved/task/convergence-evidence.json \ |
| 27 | + --json |
| 28 | +``` |
| 29 | + |
| 30 | +Exit codes: |
| 31 | + |
| 32 | +```text |
| 33 | +0 task is inside its convergence envelope, or a terminal snapshot is verified |
| 34 | +75 convergence limit reached and a terminal snapshot is required |
| 35 | +64 policy, routing, state, provenance or write-reconciliation failure |
| 36 | +2 malformed invocation or evidence |
| 37 | +``` |
| 38 | + |
| 39 | +## Terminal behavior |
| 40 | + |
| 41 | +When time, cycle, non-reduction, work-expansion, or operator-stop limits are reached: |
| 42 | + |
| 43 | +1. Stop creating tasks, agents, reviews, and verification gates. |
| 44 | +2. Preserve the exact task-owned diff and a SHA-256 manifest of affected paths. |
| 45 | +3. Reconcile every uncertain external write before replay or publication. |
| 46 | +4. When repository writes are authorized, commit and push the current work to the existing branch or a safe snapshot branch. |
| 47 | +5. Open or update a draft pull request and record its immutable commit SHA. |
| 48 | +6. Persist objective, criteria, current state, changed files, unresolved blockers, operation IDs, and continuation instructions outside model memory. |
| 49 | +7. End the current task without another correction cycle. |
| 50 | + |
| 51 | +If repository writes are not authorized, create a provider-neutral diff manifest and continuation package instead of silently discarding local work. |
| 52 | + |
| 53 | +## Restoration condition |
| 54 | + |
| 55 | +A new correction cycle requires a new human-authorized task manifest that names the exact failed criterion and resets a bounded cycle budget. Rewording the same goal or adding review steps does not reset the budget. |
0 commit comments