CI / release workflows
PUBLIC REPOSITORY
Evidence ceiling E3Proof boundary
RELEASE GOVERNANCE
Published proof records remain separately identifiable.
The public protocol repository has an active default-branch ruleset and a published pub.2 release. Public Site 80 reports the ruleset exactly: pull-request workflow, review-thread resolution, deletion protection and non-fast-forward protection. The current ruleset does not contain a required-status-check rule, so Finality does not claim that it does.
Repository control
Current GitHub ruleset facts.
The active Protect main ruleset applies to the default branch. These are governance controls, not independent protocol assurance.
- Pull request rule
- ACTIVE
- Review-thread resolution
- REQUIRED
- Non-fast-forward
- BLOCKED
- Deletion
- BLOCKED
- Current-user bypass
- NEVER
- Required status-check rule
- NOT PRESENT
Workflow evidence
Workflows exist; ruleset enforcement is reported separately.
CI, CodeQL, Scorecard, fuzzing and release-provenance workflows may produce integrity evidence. Their existence or historical success does not make them required by the current branch ruleset and never creates E4/E5 independence.
CodeQL workflow
PRESENT
Scorecard workflow
PRESENT
ClusterFuzzLite workflows
PRESENT
Branch required-check rule
NOT PRESENT
Publication rule
Frozen protocol-publication identity is separate from Public Site 80.
The public repository exposes external-proof-v2.0.0-draft.1-pub.2 and release assets including a Sigstore bundle. Public Site 80 preserves rather than rewrites that frozen protocol-publication identity.
Current semantic release
FRP-2.0.0-draft.1
Current kernel
FSK-1.0.0
Frozen publication
external-proof-v2.0.0-draft.1-pub.2
Sigstore bundle
PUBLIC RELEASE ASSET
External evidence
ZERO