Repository navigation
Human action 49
Decision completed on 2026-09-09. The maintainer explicitly accepted ADR-0025 and authorized implementation. The recorded acceptance cleared the contract gate. The implementation is merged in PR #75, and #49 is closed. See Causal object retention for historical backfill and transfer instructions. No further human decision is required for this item. The decision procedure below is retained as the historical execution record.
Canonical work item: #49. Owner role: repository maintainer.
When required: before changing live object-retention persistence. This prerequisite is now satisfied by the accepted retention/lifecycle ADR. Implementation and qualification are complete; the decision procedure remains available as the historical record.
Read ADR-0025 and the reproduction evidence on #49. GitHub access to comment on the issue or PR is sufficient. No live repository cleanup or destructive experiment is needed to make this decision.
- Review the proposed dependency set: the note attachment and every typed commit, tree, and blob required by its accepted schema. Confirm that the scope includes applications, rebase, provenance, and resolution stage blobs, as well as hard-squash receipts.
- Review the publication boundary: update the shared retention root with notes and any new resolution ref in one checked transaction. Retaining an object must never make a target-unreachable receipt prove coverage.
- Choose the lifetime policy. The recommendation is no automatic expiration: branch deletion, note deletion, and abort do not reclaim previously retained objects. This preserves evidence at the cost of keeping orphaned source history. If that cost is unacceptable, specify the desired reclamation trigger and what evidence may become invalid before accepting an alternative.
- Record either “Accept ADR-0025 as proposed” or the requested changes on #49 or PR #75. If accepting, explicitly include the conservative lifetime policy so implementation does not infer approval for pruning or erasure semantics.
- After acceptance is recorded, update ADR-0025 to Accepted, remove the
human-action-requiredlabel from #49, and move its existing card on the private board to In Progress with its contract gate cleared. The implementation agent can perform these updates from the recorded decision. Keep #49 open through implementation.
A completed decision has a linked acceptance or revision request, a matching ADR status, and matching issue/board state. Accepting the ADR does not establish that publication, migration, or transport has been fixed: those require the regressions and qualification listed in the ADR and issue.
If the proposal is revised, leave the ADR Proposed and the existing contract gate in place while the revision is reviewed. Do not delete retention refs, expire reflogs, or run pruning commands in a valuable repository as a shortcut to evaluating storage cost. The bounded probes already supplied the initial reachability evidence in disposable repositories.
Completion evidence belongs on #49. Update this procedure to link the accepted decision when available; do not close the defect just because the design is accepted.