Repository navigation
docs(deploy): document the write gate and add its acceptance evidence - #104
Merged
Merged
Conversation
The gate itself lives in the unversioned server script; this records how it works, its failure modes and the refusal test hook, plus the terminal capture that proves the issue #81 acceptance criteria on the live system.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Records the deploy write gate (issue #81) in the repo and ships its acceptance evidence.
docs/deploy-gate.md: where the gate runs (server-side script, 5-minute cron, flock), the four API steps with expected codes, the three failure modes and their swap/FAILED-marker behavior, the--gate/--gate-test/--forcemodes, theGATE_DB_READONLY=1refusal hook with its mandatory cleanup, and the operational risk that the script is unversioned.docs/assets/deploy-gate-evidence.png: terminal capture measured 2026-11-15 on the live deploy against build943bab4. Gate steps of a real deploy, a--gate-testpass on HEAD, a refusal run withdeployed.shaunchanged and the service still healthy, and read-only sqlite queries proving scratch rows never persist while the audit entry keeps actordeploy-gate.Evidence for issue #81; the issue carries the same measurements as text. No code changes.