Repository navigation
scoreboard: r3–r6 Seals under the founder's run authorization, anchored in Rekor, with Sigstore TSA tokens - #1438
Merged
Merged
Conversation
…ed in Rekor, with Sigstore TSA tokens The founder signed run-authorization.json (github:abrichr, SSH key SHA256:x+1M…eO9A, items r3–r6, standard profile, one run per item) after the runs. The four redacted reports are re-sealed under it with the demo Seal key. Each Seal and the authorization is anchored in Sigstore Rekor (log indexes 3339630782, 3339635766, 3339636256, 3339636914, 3339637492) and carries an RFC 3161 token from the Sigstore TSA. All four verify with --strict --require-anchor --require-timestamp --live; timing after_run. operator-profile.json counts them (3 verified, 1 stopped before effect) with the identity checked live against GitHub. RFC 3161 tokens are stored in their standard binary form, <name>.tsr (DER), next to <name>.tsa.json, which names the file (tsr_file) and its SHA-256 (tsr_sha256) instead of embedding base64. The verifier reads the .tsr, checks its SHA-256, then the token; a path in tsr_file is refused. tests/test_rekor_real_fixture.py verifies r3's real Rekor entry, the authorization's, and both TSA tokens offline against the shipped roots. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
abrichr
enabled auto-merge
October 20, 2026 16:45
…ic artifacts Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
These are the landing demo's referral receipts. Four Seals were re-signed under the founder's signed run authorization. Each Seal, and the authorization itself, is anchored in the public Sigstore Rekor log and timestamped by the Sigstore TSA. The receipts sit next to #1409's redacted evidence in
packages/flow/benchmark/scoreboard/raw/openemr_referral/certified/2026-10-20/.What's in it
run-authorization/holdsrun-authorization.json,.sig,.allowed_signers,.anchor.json,.tsrand.tsa.json. The statement isopenadapt.run-authorization/v1, sha256bdfda160…04d3. It names bundleec096afa…60b6, items r3–r6 with one run each, the standard profile, Seal keyseal-ed25519-ca08dd7f42a4be01, and signer keySHA256:x+1MwCSAsNNHpc+UcIdbktY/Z+/FByyqfhuwiRzeO9A. The founder signed it withssh-keygen -Y signand the key published at github.com/abrichr.keys.N-rX-…/engine/gets a newseal.jsonover the same redactedreport.jsonbytes from scoreboard: OpenEMR referrals r3–r6 on the certified bundle, reports redacted and under an offline Seal #1409, plusseal.anchor.json,seal.tsrandseal.tsa.json.operator-profile.jsoncovers the Seal key: 4 anchored runs, 3 verified and 1 stopped before effect, with the identitygithub:abrichrchecked live against GitHub.These are the first live submissions with the #1394 anchoring code. Public Rekor accepted the Ed25519ph
hashedrekordentries.Verification
Run on main's code, after the #1421 batch:
All four pass. For each run, the output says the Seal is valid over
report.json, and that its anchor checks out live and offline. It also prints this line: "authorized by github:abrichr (… identity checked against https://github.com/abrichr.keys now)". The timing isafter_run: the runs ran at about 03:03 UTC and the authorization was logged at 15:53 UTC. So the card reads "Authorization signed by @abrichr on 2026-10-20, after this run". The re-seal doesn't change that.Fixture test
tests/test_rekor_real_fixture.pyadds 7 tests; offline, they verify:The fixtures (32 KB of public records) are in
tests/fixtures/rekor_real/.Timestamp token files
Each RFC 3161 token is stored in its standard binary form,
<name>.tsr(DER, as returned by the TSA).openssl ts -reply -in seal.tsr -token_in -textreads it.<name>.tsa.jsonnames the file intsr_fileand its SHA-256 intsr_sha256instead of embedding base64. The verifier reads the.tsrand checks its SHA-256, then the token. Atsr_filethat is anything but a bare.tsrname beside the JSON is refused, as are a missing or changed.tsr, each with a test. The real tokens were converted to this layout as-is, with no new TSA requests.Hygiene
private/files are committed..gitleaks.tomlis unchanged. With the stock config,gitleaks git --log-opts=origin/main..HEAD(this PR's commits) and the staged scan are clean. The JSON field names avoid the word "token", which is what trippedgeneric-api-key. The prospect-name check is clean.🤖 Generated with Claude Code