Stop the lane when ambiguity requires an operator
A typed halt stops the lane and raises operator-visible signal when automation alone cannot resolve a condition.
Pain. Agent runs that hit file conflicts, missing invariants, or unsafe inference sometimes plow forward with best-effort text. The trace alone does not tell the board that a human decision is mandatory.
What changed. A typed halt-and-surface path raises a visible halt for the operator—e.g., HALT_AND_SURFACE with a one-line reason—instead of silently choosing. Halts integrate with the escalation hooks so attention is routed, not buried in logs.
Why it matters. Coordination research here separates automation gain from vigilance loss. Surfacing halts as first-class events supports C1-style analysis of who caught what class of failure after tooling improved.
How to try it
- Trigger a workflow branch that emits a halt (conflict or ambiguous instruction) in a controlled scenario.
- Confirm the board or inbox path lists the halt until resolved.
Shipped in 612fbd1 — feat(DP-84): halt-and-surface lane for operator attention (#42)