Mechanize the critical release-lane proofs currently held only in prose #135

Open
opened 2026-07-29 01:47:32 +00:00 by perishadmin · 0 comments
Contributor

Context

The release-lane anatomy is incident-derived but remains prose-only: fresh guard, manifest stamping, publish dry-run assertion, idempotent publish, registry readback, and seal. These are closer to the irreversible accident surface than another repository layout check.

Acceptance

  • Define the smallest checkable release-lane evidence model without parsing arbitrary product behavior.
  • Mechanize fresh guard, pre-publish dry-run assertion, registry readback, and final seal ordering where repository evidence can prove them.
  • Refuse ambiguous or unprovable lanes instead of guessing.
  • Move only genuinely enforced clauses from prose-only Standing into checked Standing.
  • Add living specimens for each supported release topology.
Context The release-lane anatomy is incident-derived but remains prose-only: fresh guard, manifest stamping, publish dry-run assertion, idempotent publish, registry readback, and seal. These are closer to the irreversible accident surface than another repository layout check. Acceptance - Define the smallest checkable release-lane evidence model without parsing arbitrary product behavior. - Mechanize fresh guard, pre-publish dry-run assertion, registry readback, and final seal ordering where repository evidence can prove them. - Refuse ambiguous or unprovable lanes instead of guessing. - Move only genuinely enforced clauses from prose-only Standing into checked Standing. - Add living specimens for each supported release topology.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
PerishLab/plumb#135
No description provided.