A snapshot: read at commit 707a04c7ce8 on 2026-10-18T00:06:01Z by majordomus 0.29.0. Nothing on this page is read again. See it live
I2003
A handover pins the binding it was written under, and resolving it reports drift
Where it stands
devtask.issue- Readiness
- blocked 1 of its dependencies is not DONE
- Status
- BLOCKED
- Can start
- not now
- Milestone
- Milestone status
- BLOCKED
- Wave
2- Waiting on
- Holds back
- none
- Behind it in all
0- Evidence
0of1
| In the way | Subject | Detail |
|---|---|---|
| issue | I2001 | I2001 is not DONE |
| milestone | intent-bound-work | the milestone intent-bound-work waits on an outcome of its own |
Moves
plan.transitionWhat it is
- 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.
- Now
- A handover's front matter carries the task, the branch and the head. --resolve prints Match, Git state, Freshness and Divergence.
- Wanted
- --resolve prints an Intent line: unchanged, or which of the two revisions moved, or unknown when the binding cannot be read.
- Done when
- unknown: the record declares no `completion`
- Risk
- unknown: the record declares no `risk`
Acceptance
- 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_movedbash test/run.sh 05_handover- Evidence required
resolve_reports_intent_drift- Evidence present
- unknown: the record carries no `evidence` entries
Scope
- Touches
lib/handover.shlib/common.shlib/intent_binding.shtest/cases/961_a_resumed_task_is_told_its_intent_moved.sh- Not
- unknown: the record declares no `non_scope`
- Depends on
- Priority
- p1
- Profile
- implementation
- Parallel safe
- false
- Owner
- unknown: the record declares no `owner`
The work so far
- Branches
- none
- Merged
- none
- Commits
0- Trunk
- master
- Sessions
- none
- Created
- 2026-10-07
- Updated
- 2026-10-07
- Started
- unknown: the record declares no `started_at`
- Verified
- unknown: the record declares no `verified_at`
- Completed
- unknown: the record declares no `completed_at`
Synchronisation
- Adapter
scripts/github-sync- Repository
- unknown: the derived plan's header carries no repository
- External issue
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
- State there
- unknown: a live GitHub state; this executable makes no network call, so only `scripts/github-sync --check` can answer it
Findings
Nothing is wrong with these records.