Skip to content

clarify the frozen R5 protocol provenance - #64

Merged
papasop merged 1 commit into
mainfrom
codex/clarify-r5-protocol-provenance
Aug 18, 2026
Merged

clarify the frozen R5 protocol provenance#64
papasop merged 1 commit into
mainfrom
codex/clarify-r5-protocol-provenance

Conversation

@papasop

@papasop papasop commented Aug 18, 2026

Copy link
Copy Markdown
Owner

Clarify that r5_full_tube_protocol_v1_0.json records the prospectively frozen starting protocol for the subsequently completed subordinate R5-A/B0-B6 certificate chain.

Preserve the protocol's immutable R5_FULL_TUBE_PROTOCOL_FROZEN_NO_CERTIFICATE_RUN status while removing stale wording that describes the certificate as merely future or says that no R5 certificate can yet exist.

Do not modify any protocol bytes, certificates, scientific claims, verification code, published-paper boundary, R6 status, or normal K=1 scope. Refresh only the README-bound manifest and checksums required by the documentation change.

Clarify that r5_full_tube_protocol_v1_0.json records the prospectively frozen starting protocol for the subsequently completed subordinate R5-A/B0-B6 certificate chain.

Preserve the protocol's immutable R5_FULL_TUBE_PROTOCOL_FROZEN_NO_CERTIFICATE_RUN status while removing stale wording that describes the certificate as merely future or says that no R5 certificate can yet exist.

Do not modify any protocol bytes, certificates, scientific claims, verification code, published-paper boundary, R6 status, or normal K=1 scope. Refresh only the README-bound manifest and checksums required by the documentation change.
@papasop
papasop merged commit e0ec327 into main Aug 18, 2026
2 checks passed
@papasop
papasop deleted the codex/clarify-r5-protocol-provenance branch August 18, 2026 09:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant