Skip to content

docs: move certificate revocation (3.5h) to Phase 8 - #108

Open
atiernan wants to merge 5 commits into
mainfrom
docs/revocation-to-phase-8
Open

atiernan wants to merge 5 commits into
mainfrom
docs/revocation-to-phase-8

Conversation

@atiernan

@atiernan atiernan commented Nov 5, 2026 •

Copy link
Copy Markdown
Member

The maintainer moved certificate revocation (3.5h) from Phase 3 to Phase 8. Docs only.

What changed

  • docs/phases/phase-3.md: exit criterion 6 now covers the cookie jar, localStorage and the history surviving a restart. 3.5h opens with the move, and its status row, crate row and the order of work follow.
  • docs/ROADMAP.md: revocation leaves Phase 3 and joins Phase 8.
  • The 3.5h and 3.5h.0 decisions stay as the record for when this is picked up.

The known gap

Production still passes NothingRevoked, so a revoked certificate that has not expired is accepted. Both documents now say so.

New fact recorded

Mozilla's Remote Settings client specification strongly discourages new ad-hoc clients and says the team must validate any new implementation, so asking Mozilla comes first when this resumes. No agent contacts Mozilla.

Left alone

The 3.10 section and its status row still name the revocation set. 3.5h's note says that part goes with it.

Verification

cargo xtask check passes locally (static checks; no build, tests or proofs). cargo xtask verify --changed was not run, because nothing but docs changed. CI's full verification has not run on this PR yet, and its proof jobs need a full-verification reviewer's approval.

🤖 Generated with Claude Code

…ase-8

# Conflicts:
#	docs/ROADMAP.md
#	docs/phases/phase-3.md
Keep main's Windows wording for Phase 8 and the revocation sentence.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Takes #115's fix for the status test that failed this branch's CI.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Keep main's 3.5g row and this branch's 3.5h row.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

This branch is waiting to be deployed

1 waiting deployment
full-verification — 78897de7 Waiting Nov 5, 2026 by atiernan via Approve the proofs #327
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