I2003 — A handover pins the binding it was written under, and resolving it reports drift
Write issue, intent and binding_revision into a handover's front matter when the task is bound, and have handover --resolve ask intents.binding again and say whether the plan revision or the evidence standing changed since.
BLOCKED wave 2 · p1 · implementation profile · runs alone
Part of intent-bound-work — A task is bound to the intent it serves.
Blocked. This issue cannot start until I2001, milestone:intent-bound-work are done. The status is derived from that, not declared.
Objective
Write issue, intent and binding_revision into a handover's front matter when the task is bound, and have handover --resolve ask intents.binding again and say whether the plan revision or the evidence standing changed since.
Why
A resumed worker is told how far the commit moved and nothing about whether the criteria it was working to were rewritten, or the critique reopened, in between.
Current state
A handover's front matter carries the task, the branch and the head. --resolve prints Match, Git state, Freshness and Divergence.
Desired state
--resolve prints an Intent line: unchanged, or which of the two revisions moved, or unknown when the binding cannot be read.
Scope
- lib/handover.sh
- lib/common.sh
- lib/intent_binding.sh
- test/cases/961_a_resumed_task_is_told_its_intent_moved.sh
Dependencies
What waits on this
Acceptance criteria
- A handover of a bound task carries the binding revision
- After a criterion of the intent is edited, --resolve reports the plan revision changed
- A handover of an unbound task carries no pin and --resolve prints no Intent line
- The front matter carries plan_revision and evidence_standing as two keys, a body that forges either is refused like every other computed key, and a checkpoint carries neither
- An ordinary commit that changes no intent, link or critique leaves plan_revision unchanged
Validation
- bash test/run.sh 961_a_resumed_task_is_told_its_intent_moved
- bash test/run.sh 05_handover
Evidence required
- resolve_reports_intent_drift
Evidence
None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.
Timeline
- started
- —
- verified
- —
- completed
- —
Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.
Canonical record: .ai/repo/project/issues/I2003.yaml. Read it back with majordomus plan show I2003.