feat: add secure PoCI external submission admission - #205
Conversation
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Validation completeFinal head: Passed:
Readiness result: Evidence artifact:
Bootstrap boundary: the |
What changed
Adds the twelfth PoCI slice: a secure admission path for an independently owned external witness submission.
The implementation adds:
pull_request_targetintake workflow that checks out only trusted base code;response.json,submission.json,provenance.json);gh attestation verifyinvocation;ACCEPTafter admission;HOLDuntil a real external submission exists;provenance.json.Security boundary
The trusted intake workflow:
Permissions are limited to:
The write permission is used only to comment the verified result on the pull request.
Honest live result
No repository owned by another GitHub account is connected to the current session. Therefore the conformance workflow must emit:
It does not generate a synthetic external acceptance.
Bootstrap limitation
pull_request_targetworkflows are loaded from the target branch. This PR validates the verifier and security contract; the live external intake endpoint becomes active after the trusted workflow reaches the branch targeted by an external submission.Stacked PR
Base:
agent/poci-external-witness-sdk-v0.1/ #204No merge is performed by this PR.