Repository navigation
docs: preflight readiness record, SPEC-018 stays blocked - #186
Merged
Merged
Conversation
The matrix states observed controls. It does not flip a readiness gate, choose a queue vendor, or claim production authority.
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: af1382a9a0
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
The suas-specs protection row was one column short. The missing blocker cell is restored, and Prettier can check the file.
The D-022 packet and factory already select the Postgres outbox. The readiness row records that choice as partial. The 2026-09-25 operator call still forbids a PRODUCTION_DURABLE_QUEUE READY claim. worker-deploy.yml is labeled a synthetic-staging deployment, and production deployment stays prohibited.
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.
Problem
mainhad no branch protection, and the remaining production-readiness gaps were not written down as observed facts. That made it easy to treat a green check as launch authority.Released authority
0.6.0,RELEASE_MANIFEST-0.6.0.mdSPEC018_OWNER_LAUNCH_PACKET.mdsettlementKEEP_BLOCKED(2026-09-26)OPERATOR_CALLS_2026-09-25.mdfor D-001, D-002, D-006, D-008, D-010, D-013, D-021/D-023/D-024, D-022, D-034, D-036Files changed
docs/hardening/BRANCH_PROTECTION.mddocs/hardening/READINESS_MATRIX.mdTests
No product code changed. No test run.
Security / privacy effect
None in the application. The matrix restates that native session storage stays memory-only and that HIPAA classification is counsel-owned.
Migration effect
None.
Rollback / forward-fix
Revert the documentation commit. The GitHub branch-protection change is separate and is recorded in
BRANCH_PROTECTION.md. Reverting the commit does not remove that GitHub setting.Remaining unavailable surfaces
SPEC-018 stays
KEEP_BLOCKED. No readiness gate moves to READY. D-001, D-002, D-006, D-008, D-010, and D-013 stay pending. SLO, RTO, and RPO stayNOT_COMPUTABLE.Evidence
On 2026-09-30 the branch-protection API applied, for
suasmain: pull request required, required checkverify(strict), conversation resolution required, force-push blocked, deletion blocked.enforce_adminsis false.required_approving_review_countis 0.suas-specsandsuas-androidreceived pull-request protection without a required status check.suas-iosreturned HTTP 403 (private repository, GitHub Pro or public required). That protection was not applied.