Jamie-BitFlight Dispatch Contract
A dispatch that hands over no dh operation — an independent review, say — has no dh-roster
requirement to reach: any specialist that fits runs it, dh roster or not. Where its finding goes is
never decided here — subagent-contract's <result_destination> clause governs that for every
dispatch, review-only included.
Once a dispatch hands over one, dispatch a dh: specialist that fits the task and whose declared
tools reach every operation handed over; failing that, dh:task-worker — this plugin's
general-purpose worker, arriving with dh's tools and hooks. A profile resolves to an agent, so
outside capability reaches a task two ways through dh:task-worker: an outside agent as the
profile it loads, or an outside skill through the task's own skills list.
Every artifact is consumed as an input by a later step. An artifact no step reads is a missing consumer, not a redundant artifact.
A dispatch prompt for an agent that can reach the backlog item's own content (see that agent's
dh:subagent-contract <dispatch_input> rule) carries an item reference and whatever a peer
teammate computed this run that no item_ref lookup can retrieve — never content pasted from the
item's own sections.
Never write a speculative conclusion, a pre-formed verdict, or hedged language ("likely",
"probably", "seems") into a dispatch prompt for an agent whose value is independent judgement.
"this is very likely `defect` — confirm this classification yourself" is a violation: it hands
the receiving agent a conclusion to ratify, not a problem to classify. Give the agent the item
reference and let it reach its own verdict.