Skip to main content

Module dispatch_record

Module dispatch_record 

Source
Expand description

Per-task dispatch record JSON.

Defined in plan-issue-contract-v2.md “Canonical Runtime Artifacts (v2)”.

The binary writes the nine required keys at sprint start. Optional adapter fields (runtime_name, runtime_role, runtime_role_fallback_reason) are intentionally absent — they belong to the active runtime adapter and are added post-emission by the wrapper / main-agent.

Structs§

DispatchRecord
Stable, sorted JSON object written to dispatch-<TASK_ID>.json.

Constants§

WORKFLOW_ROLE_IMPLEMENTATION
workflow_role value emitted by start-sprint for every implementation task.

Functions§

write_dispatch_record
Pretty-print + write a dispatch record to disk (creating parent dirs).