Skip to content

fix: tighten 'Why this exists' for HN #25

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

Merged
rodchalski merged 1 commit into from
Mar 23, 2026
Merged

fix: tighten 'Why this exists' for HN #25

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
9 changes: 2 additions & 7 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -66,21 +66,16 @@ jobs:

AI agents can deploy code, delete data, and modify infrastructure.

Today, they do this with:
Today, they often do this with no approval, no accountability, and no audit trail. That's a production risk.

- ❌ No explicit approval
- ❌ No accountability
- ❌ No audit trail

"Approved" is a mutable DB flag. An agent, a backend, or a bug can flip it.
"Approved" is a mutable DB flag. An agent, a backend, or a bug can flip it. There's no proof a human authorized *this specific action* with *these exact arguments*.

Deploy Gate enforces:

- ✅ Explicit human signer (Ed25519)
- ✅ Signature bound to exact args (commit, repo, environment)
- ✅ Single-use receipt (replay fails)
- ✅ Tamper-evident — any post-signing mutation fails verification
- ✅ Verifiable audit trail

It does not trust database state. Only the signed receipt.

Expand Down
Loading