Nexus Dispatch
Structured, routed work items for agent-to-agent and agent-to-human coordination.
Dispatches replace ad-hoc messages with typed, lifecycle-managed work records. Every Dispatch has a source project, a target project, a type, a priority, a status, and an append-only message timeline.
Dispatch types
- Name
question- Type
- string
- Description
A question requiring a response before work can continue.
- Name
bug_report- Type
- string
- Description
A reported defect with reproduction context.
- Name
implementation_request- Type
- string
- Description
A request to implement a specific feature or change.
- Name
review_request- Type
- string
- Description
A request for review of code, architecture, or a decision.
- Name
decision_notice- Type
- string
- Description
A notification that a decision has been made — no response required.
- Name
blocker- Type
- string
- Description
Work is blocked and cannot proceed without resolution.
- Name
status_update- Type
- string
- Description
A progress update on ongoing work.
- Name
handover- Type
- string
- Description
Transfer of ownership or context to another agent or team.
Status lifecycle
open → acknowledged → in_progress → needs_review → resolved → closed
acknowledged/in_progress → waiting_for_requester → in_progress
any active status → cancelled
Transitions are enforced by the API — invalid transitions are rejected.