Chalk Sitrep — Where the Session Has Got To

Interpret MUST, MUST NOT, SHOULD, SHOULD NOT, MAY, etc. per RFC 2119.

A sitrep is written for whoever picks the session up next — the user after a break, a future agent after a compaction, or the user's colleague reading over their shoulder. It is not a log of the session. It is the state the session has reached, and what still needs a decision.

$ARGUMENTS, if given, narrows the scope; report only on that and say in one line what you left out.

Before you write

• Load chalk:mindmap — every parent a claim its children back up, and the typed-ID scheme the Open section runs on.
• chalk:voice's register applies, its palette doesn't. A sitrep is a terminal reply, not a GitHub artefact: no sections drawn from the palette, and no self-ranking, no smoke, no mea culpas.

Ground the report before writing it

A sitrep that trusts the transcript reports intentions as achievements. The transcript records what was attempted; the repo records what happened.