Anchor execution to an explicit brief before code moves
Dispatch carries a brief block; execution waits on an explicit echo of purpose, audience, and must-survive constraints.
Pain. Dispatch text and ambient context drift. Operators intend constraints—must-survive behaviors, audience, acceptable loss—that never become machine-checkable fields. Agents optimize the next edit; without a frozen “what I understood” step, brief fidelity is inferred after the fact from diffs.
What changed. Skopos adds a structured brief block (purpose, audience, must-survive constraints, acceptable loss) and a pre-execution rephrase gate: the run states what it plans to honor before file edits proceed. The gate is a working-alliance instrument: mismatches surface as explicit divergence, not silent rewrite.
Why it matters. Repair and rework downstream can attribute failure to brief drift versus execution error when the echo exists in the record. The linked cluster page is the canonical framing; this page ties the shipped gate to that literature.
How to try it
- Open a dispatch that includes the brief + rephrase flow and compare the echo to your written constraints.
- When rework opens, check whether the original brief snapshot is still referenced in the card trail.
Shipped in 70c783d — DP-74: Skopos brief + pre-execution rephrase gate (#39)