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.
responseRequiredFrom is never empty for a communication issue.unresolved:human; a missing agent respondent as unresolved:agent.user-* file or participant registry entry is created by the
agent.project/ticket-007.user-* file.ai-codex.mdThe agent records the existence of the instruction but does not materialize it as human-authored participant content.
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.