PATCHDAY
CA5NAuQt8HLcAeghBeYTa3o2PMiG1p3o1HqAEeb7Fvpump
PATCHDAY mark: a pixel-art circuit chip with an orange bandage patched across it

Release discipline, onchain.

PATCHDAY

Every update gets witnesses before production gets surprises.

House Rule

Software behaves better when every patch arrives with a public paper trail.

Release Cycle

A maintainer submits one bounded change for one named application. Reviewers inspect the diff and dependencies, approval is recorded onchain, and deployment waits for its declared window. After release, independent verification closes the trail. The shared release record is identified by $PATCH; the application still owns the shipping decision.

  1. Draft

    A maintainer describes one bounded change and the application it touches.

  2. Review

    Independent eyes inspect the diff, dependencies, and declared effect.

  3. Approval

    Authorized signers record consent before any production handoff begins.

  4. Queue

    The accepted patch waits for its published deployment window.

  5. Deploy

    The application applies exactly the version reviewers approved.

  6. Verify

    Observers compare the live result with the recorded release.

Patch first. Surprise nobody.