L04-07 — Converge provenance and sign-off #39

Outcome

Append one authoritative chain for plan, approval, execution, artifacts, validation, and sign-off.

Parent and boundary

Parent: #5. Owner: LoopLibCore correction subsystem. This issue owns one bounded slice of Governed Operation Engine; consume accepted upstream contracts and keep PDF/verdict/publication authority with Core.

Acceptance

• Every event binds exact identities and a reader can reconstruct who approved what output.
• Failure case: A second history store or stale sign-off after output changes is rejected.

Required proof

Close/reopen/tamper tests and audit reconstruction. Record the exact source SHA, test command or hosted run, fixture/artifact identity, and any skipped or unavailable lane. Run the repository's mapped proof and check-change gate for a PR.

Handoff

Record changed files, observed result, remaining risk, and a 1–3 sentence anti-slop review. Completion means acceptance evidence, not merely a merged implementation.

Sources

Approved master roadmap.