Repository navigation
Conversation
auths-gateway support-bundle writes one bounded archive: versions, digests, the deployment and credential-store kinds, the qualification state and code, the connection state a serving gateway reports, and the digest and stage of each stored attempt. It is built from a struct with no member that holds text, so a proof, action, body, credential, location, account, resource identifier, or header has no way in. Both attempt stores gain a bounded listing of attempt keys. A test installs a gateway whose credential and account label are the custody fixture's canaries, leaves the other nine beside the installation and in the environment, and scans the archive for all eleven; the assertion that the gateway had no support bundle is retired. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Source-SHA: 71a85bf Workflow-Run: 37414864276
bordumb
had a problem deploying
to
gateway-custody-live
October 6, 2026 19:58 — with 
GitHub Actions
Error
GitHub Actions
Error
bordumb
had a problem deploying
to
gateway-custody-live
October 6, 2026 19:58 — with
GitHub Actions
Error
GitHub Actions
Error
This branch is waiting to be deployed
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
1 participant
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.
First production qualification previously required its own existing attestation. This adds purpose-separated, finite commissioning authority on the private operator path while ordinary clients retain the production qualification gate. Signed permits bind the exact native actor/actions, production tuple, source, disposable resources and protected run; PostgreSQL budgets and separately retained host floors prevent renewal or restore from resetting consumption.
The change also pins the offline qualification root and public ceremony, adds native credential-free request review and independent Stripe/Airtable references, separates commissioning from ordinary qualified-client evidence, and compares fresh response/doctor witnesses without wildcard expectations. Actual custody and HTTP boundaries expose private process-scoped measurements; closed execution traces remain available for redaction/audit. Release readiness derives from verified current qualifications for the exact candidate.
Independent operator work includes the source-free native simulation kit, real development-provider journeys with an installed Python wheel, and resumable resource lifecycle CLIs. The latest local Docker rehearsal created and fully retired one Stripe test payment and one dedicated Airtable record. Stripe uses platform-account test refunds without Connect.
Validation: local provider rehearsals passed; generated semantic identities/closure are current. Hosted validation is pending on the latest head. Development evidence explicitly excludes protected production qualification.
Before merging Epic 5: complete admitted family corpora and protected commissioning → first record → ordinary live orchestration, obtain signed protected closure, and pass CI. Shared-environment changes/provider-secret uploads were rejected by automatic approval review and remain unapplied. PR #207 and the actual GitHub release installation follow qualification completion.