Skip to content

Separate local, PR and release completion criteria #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jh1nresh wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Separate local, PR and release completion criteria #5

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 12 additions & 4 deletions AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,10 +30,18 @@ or on-chain authority change.
production health.
- Feedback: deterministic failure, security finding, contract invariant, or
production revision mismatch.
- Artifact: one atomic PR, one `maiat-release-readiness.json`, and one
`maiat-delivery-receipt.json`.
- Convergence: all app and contract checks pass and production reports the
exact merged commit under the approved release policy.
- Artifact and convergence follow the requested stage:
- Local-only: scoped patch plus applicable verification; no PR or production
state is required to report local implementation verified.
- PR: one atomic PR with applicable checks and review evidence. Report merge
and deployment as not requested unless separately authorized.
- Merge: verify the authorized merge and its readiness checks.
- Deployment: only for an authorized release, require
`maiat-release-readiness.json`, `maiat-delivery-receipt.json`, and production
readback of the expected commit and approved chain.
- Do not wait for an unrequested release or broaden authority just to satisfy a
delivery receipt. Full app/contract/release checks apply when their affected
scope or requested stage requires them.
- Human approval: merge, database migration, production secret, Vercel/Railway
setting, cron activation, chain switch, contract broadcast/verification,
signer/role change, transaction, settlement, refund, and fund movement.
Expand Down
Loading