---
name: int-xx-marker-protocol
description: The literal line-based markers the mission loop parses to advance state — TASK, WORK, HANDOFF, TEST_PASS, REVIEW_APPROVE, COMPLETED.
when_to_use: Pin on every coding role. Missing or malformed markers cause the mission to stall.
tags: [foundation, protocol]
---

# INT-XX marker protocol

Missions parse your turn output line-by-line for these markers. **They must appear literally**, with the colon, on their own line, no bold, no code fence.

## The full ladder

```
TASK: INT-NN — <title>              # planner opens a new item
PLAN_COMPLETE: INT-NN                # planner is done specifying
WORK: INT-NN                         # coder starts implementing
HANDOFF: INT-NN                      # coder passes to tester/reviewer
TEST_PASS: INT-NN                    # tester confirms green
TEST_FAIL: INT-NN — <reason>         # tester failed the build; coder loops
REVIEW_APPROVE: INT-NN               # reviewer OKs the diff
REVIEW_BLOCK: INT-NN — <reason>      # reviewer requests changes
COMPLETED: INT-NN                    # committer pushed; loop advances
```

## Rules

1. **Exactly one INT id per marker line.** `COMPLETED: INT-05, INT-06` won't parse.
2. **Emit at the end of your substantive turn**, not the beginning. Otherwise the parser advances state before the work is real.
3. **Never emit a marker you can't back up.** Emitting `COMPLETED: INT-NN` without a corresponding `git push` desynchronizes the mission from the repo.
4. **`REORDER: <one-sentence rationale>`** if you're taking an INT out of order — the loop's review timeline logs these.

## What the loop does with each

- `TASK` + `WORK` + `HANDOFF` are observability only — they show up in the mission's task-card feed (Slice 5).
- `TEST_FAIL` / `REVIEW_BLOCK` re-schedules the item back to the coder.
- `COMPLETED` bumps `mission_tasks.status = 'complete'` and advances the loop's `consumed_int_ids`. Next iteration picks the next unconsumed INT.
- `REORDER` writes a `loop_reorder_event` row — a reviewer can inspect why the order shifted.

## Common failures

- **Marker in a code fence**: `\`\`\`COMPLETED: INT-05\`\`\`` won't parse. Put it OUTSIDE the fence.
- **Marker with markdown emphasis**: `**COMPLETED: INT-05**` won't parse.
- **Wrong dash**: `INT-NN — title` uses en-dash; `INT-NN - title` also works. `INT-NN – title` (em-dash) also works. Any dash-like char is fine; the parser trims whitespace around it.