status

Report on programme $1 (resolve as /programme:resume does). Pass --gates to also run the slow gates.

This command writes nothing. Not the ledger, not NEXT-SESSION.md, not INDEX.md — even when you find something wrong. That is the whole point: a status that quietly corrects the record cannot be used to find out whether the record is honest, because running it makes the answer yes. Report the drift and name the file to fix; /programme:handoff is what writes.

Use this when you want to know where things stand without starting work. /programme:resume reads the same files and then begins.

1. Where the programme is

From <docsRoot>/programmes/<SLUG>/ledger.md and its NEXT-SESSION.md:

• ## The arc first — the goal, and the programme's terminal condition quoted verbatim. Say plainly that it is the programme's and that the one below is the phase's; a met phase condition read as a met programme condition is how a programme gets called finished with phases still planned.
• what is done and what is left, from the arc's status column: the done rows, the current one, and every row still planned. Do not invent a progress metric, and never read what has closed by counting Archive index rows — that table's own note says why.
• the phase's terminal condition, quoting its Command: and Expected output: verbatim
• the mode — INDEX.md's mode cell, read as INDEX.md's header comment states; if the raw cell is not exactly one of the three, quote it and say how it reads. For supervised or autonomous, run the herdr dependency check /programme:mode states and report each of its three results — a failure here is reported, not refused.

If the arc, the Current position and the Archive index disagree about what has closed, say so — that is a real finding, not a formatting problem. An arc whose current row is not the phase NEXT-SESSION.md describes is the same finding, and it is the one that means the programme has drifted off its own map.