docs: define continuity dispatch receipt core fields
This commit is contained in:
19
docs/runbooks/approved-plan-continuity.md
Normal file
19
docs/runbooks/approved-plan-continuity.md
Normal file
@@ -0,0 +1,19 @@
|
|||||||
|
# Approved Plan Continuity
|
||||||
|
|
||||||
|
## Continuity receipt core fields
|
||||||
|
|
||||||
|
### `planId`
|
||||||
|
- The identifier of the approved plan that the continuity receipt belongs to.
|
||||||
|
- Use this field to associate the receipt with one specific approved plan.
|
||||||
|
|
||||||
|
### `currentTask`
|
||||||
|
- The task from the approved plan that is currently being executed or has just completed.
|
||||||
|
- Use this field to record which plan task the receipt is about.
|
||||||
|
|
||||||
|
### `nextDerivedAction`
|
||||||
|
- The next concrete action derived from the current task that should be dispatched to continue the workflow.
|
||||||
|
- Use this field to record the intended follow-up action for continuity.
|
||||||
|
|
||||||
|
### `dispatchedAt`
|
||||||
|
- The timestamp indicating when the next derived action was actually dispatched.
|
||||||
|
- Use this field to record when the continuity handoff occurred.
|
||||||
Reference in New Issue
Block a user