Repository navigation
Conversation
Adds a second active key, uk-gate-team-2026 (dd31e325...), held in the shared agent store, beside the key that signed every cut on record, which stays active. One key per builder: nobody shares a secret, and a cut is signed, certified and published by one key holder. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been 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
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.
Hold: do not merge until María Juaristi agrees. This is stacked on #1348; retarget it to
mainonce #1348 merges.Registers a second active UK gate signing key in
microcosm.data.gate_signing_keys:uk-gate-team-2026dd31e32563854596d983a71a6519c6b7860a7c1f63ffb80dbe679d5d34c4de8cmicrocosm/uk-gate-signing-key-team(accountmaxghenis) on Max's build Mac. The key was generated on 2026-10-22, stored without being printed, and verified by reading it back and comparing fingerprints.Why a second key, rather than sharing the existing one: HMAC verification needs the secret that signed. A cut is signed, certified and published end to end by one key holder, so each builder can hold their own registered key. María's key,
66bf0e29…, stays active, and every cut it signed still verifies.To build with it:
Rotation and revocation are covered in
docs/uk-cut-anyone.md(#1348).axiom: n/a: build infrastructure
🤖 Generated with Claude Code