todo2code

Ticket 007: Explicit unresolved response routing

Goal and scope

Ensure every communication divergence names a concrete respondent or an explicit unresolved-role sentinel. The measured regression case is ticket-006: an agent-only ticket correctly requires a human response but currently emits an empty responseRequiredFrom array.

Executable implementation belongs in src/, regression coverage in test/ and public behavior documentation in docs/. This directory contains only governance, decisions, logs and captured evidence.

Acceptance criteria

Non-goals

Participants

Approval

The agent records the existence of the instruction but does not materialize it as human-authored participant content.

Evidence

Conclusion

Issue construction now fills an otherwise empty route with a role-specific sentinel. The real ticket-006 audit changed three human-required issues from an empty list to unresolved:human; no participant was inferred. Offline tests, both gold versions and all five SDK examples pass.