ci: add keyless multi-runner PoCI witness network - #200
Draft
safal207 wants to merge 2 commits into
Draft
Conversation
Owner
Author
|
Validation complete on Passed:
The signed-witness workflow completed all three witness jobs, coordinator verification, exact-root quorum, final report attestation, and evidence upload. Final artifact: |
This was referenced Jul 31, 2026
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.
What changed
Adds the eighth PoCI slice as a deliberately small trust-layer PR:
witness-alpha,witness-beta, andwitness-gammaas three separate GitHub-hosted matrix jobs;actions/attest@v4;gh attestation verifyto validate the exact repository, signer workflow, source digest, signer workflow digest, GitHub OIDC issuer, and hosted-runner boundary;2-of-3policy;attested-quorum-report.json;Why keyless Sigstore instead of committed test keys
No long-lived signing key is stored in the repository. GitHub OIDC mints the short-lived signing identity, Sigstore signs the artifact provenance, and the coordinator pins the signer workflow and source commits during verification.
Trust boundary
This demonstrates separate runners and cryptographically verified workflow provenance. It does not claim that the three jobs are operated by independent organizations: the same repository still controls all three jobs. A real network boundary requires at least one externally governed signer workflow or consumer.
Stacked PR
Base:
agent/poci-multigraph-witness-quorum-v0.1/ #199Review and merge after #199, then retarget to
mainif GitHub does not do so automatically.Reviewer evidence
Expected final artifact layout: