Repository navigation
docs(roadmap): #294's entry names the proof visit it is actually gated on - #609
Merged
Merged
Conversation
…d on The entry landed hours ago in 3b691fe, written from the issue's original body rather than its state, and it described the lab as it was before 2026-09-09. Three of its claims were false when it was written: - "what it needs is somewhere to put the second key" — the home was decided 2026-09-08 (#397): the technical second named on the break-glass card. - "Decryption depends on one key held by one person until it lands" — it does not. #412 re-keyed on 2026-09-09 and either recipient opens the secrets. - "ADR-0048 already assumes that medium exists" — ADR-0048 does not assume it, it reports it: "the medium exists, is off-estate by construction, and has not yet made its first visit." It also never said what gates the issue, which is the one thing roadmap.md says an entry is for — "a link, the gate, its place in the order, and why". The gate is the first proof of the new copy: verify-key-backup.sh refuses the live key by device and inode, so no timer can clear it and the medium has to be carried here. That is the same visit #573 rides on, which is the ordering fact this section exists to carry, and the entry now points at the runbook for it as #531, #573 and #574 already do. Measured before writing, rather than read off the issue: ./scripts/key-recipients.sh --list two recipients, matching .sops.yaml's catch-all rule — no drift key-recipients.prom age1cutv5... = 0, never proved SecretsKeyBackupUnproven firing, naming that recipient homelab-recipient-state.timer active, last run 09:20 today "Honest reading" is attributed to back-up-the-age-key.md and not to ADR-0024 on purpose: the ADR's "honest state" is about the period before a second key existed, which ended on 2026-09-09, and reusing it here would have been a second false claim in a commit fixing three. No changelog entry. roadmap.md sends history to changelog.md on the day an issue is done, and #294 is not: the remaining box is the visit, not this merge. The trailer below is deliberately Refs and not a close keyword. Refs #294, #573. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Gerrrt
added a commit
that referenced
this pull request
Sep 22, 2026
… its text Both branches corrected the same false clause — "decryption depends on one key held by one person until it lands" — after the re-key had landed. #609 came from the session that owns #294 and says more: ADR-0024, the holder, the device-and-inode refusal that means no timer can clear the proof, and the runbook pointer. It already carries this branch's correction, so the resolution is its text unchanged and this branch stops touching roadmap.md. The other three corrections here are untouched by the merge. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
docs/roadmap.md's entry for #294now states the gate the issue is actually waiting on — the first proof of the
second recipient's copy — instead of describing the lab as it was before
2026-09-09. Docs only; one bullet.
Why
The entry landed a few hours ago in
3b691fe, written from the issue'soriginal body rather than its state, so three of its claims were false when
they were written:
It also never named the gate, which is the one thing
roadmap.mdsays anentry is for: "A link, the gate, its place in the order, and why. Nothing
else." The gate is the proof visit —
verify-key-backup.shrefuses the livekey by device and inode, so no timer can clear it and the medium has to be
carried here. That is the same visit #573 rides on, and the entry now carries
a
→ [runbook]pointer as #531, #573 and #574 already do.#294 is not closed by this. Its remaining box is the visit, so the trailer
is
Refsrather than a close keyword.Blast radius
secrets/*.sops.yamlNothing outside
docs/roadmap.mdis touched..sops.yaml,secrets/,back-up-the-age-key.md,successor-handover.mdandsecrets/README.mdwereall read and are correct as they stand.
Verification
Measured on the host before writing, so the entry's claims are read off the
lab rather than off the issue:
Two recipients, matching
.sops.yaml's catch-all rule — no drift, which iswhat makes "carry two, and either opens the secrets" true. Also read:
key-recipients.promhasage1cutv5…at0(never proved),SecretsKeyBackupUnprovenis firing and naming it, andhomelab-recipient-state.timeris active and last ran 09:20 today — so thegate really is the visit and nothing has drifted since the 2026-09-20 reading
on the issue.
make validatepasses —all checks passed (3 skipped — NOT run, not verified); the skipped three need a docker daemon and CI runs the fullset.
check_docs.pytreatsroadmap.mdas a record rather than prose,so only its buy-table count is checked, and this change does not touch
that table.
docs/roadmap.md)No changelog entry:
roadmap.mdsends history tochangelog.mdon the day anissue is done, and this one is not.
Refs #294, #573.
🤖 Generated with Claude Code