I3150 — A handover carries the governance digest it was written under, and resolving it says when governance moved

✕BLOCKED wave 3 · p2 · implementation profile · parallel safe

Part of entry-proves-what-it-handed — An episode records the governance and briefing it was handed, and a change is told.

Objective

Write the governance digest and manifest into a handover's front matter and have handover --resolve name the inputs that moved, beside the plan_revision drift I2003 reports.

Why

The fingerprint was proposed for handovers on 2026-09-10; I2003 pins the intent binding only. Proposed in ADR 0181 (An episode records the governance and the briefing it was handed, each by one digest) (proposed; it carries no authority until the owner accepts it). Sources: chatgpt-majordomus:c103#2.

Current state

lib/handover.sh prints plan_revision drift (line 129); no governance pin.

Desired state

Resume names governance drift with the rules that moved.

Scope

• lib/handover.sh
• apps/majordomus-cli/src/continuity

Dependencies

• I3147✕BLOCKED The effective governance has one digest, computed by one function and shown by the preflight
• I2003✕BLOCKED A handover pins the binding it was written under, and resolving it reports drift

Acceptance criteria

• A handover written before a rule edit reports governance moved on resolve

Validation

• bash test/run.sh 05_handover

Evidence required

• case_handover_reports_governance_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/I3150.yaml. Read it back with majordomus plan show I3150.