Skip to content

feat(prism-id): guardians witness a paper kit's use (replaceRecovery), residual stated exactly - #4

Merged
afflom merged 2 commits into
mainfrom
claude/project-thread-i4vn2z
Nov 14, 2026
Merged

afflom merged 2 commits into
mainfrom
claude/project-thread-i4vn2z

Conversation

@afflom

@afflom afflom commented Nov 14, 2026 •

Copy link
Copy Markdown
Owner

What

  • replaceRecovery(session, shares, { threshold, guardians }): a member uses the current recovery device's shares to move the prism to a new recovery device with fresh shares.
    • The old recovery device is combined from its shares and is never kept by the member.
    • It binds the new recovery device through createRecovery, then retires itself through revokeDevice, keeping what it signed.
    • Nothing else in the log changes.
    • Using it with threshold: 2 over a paper share and a guardian's share means the paper alone no longer recovers.
  • recoverySecret: the share combination that recoverPrism did inline now lives here, and both functions use it. recoverPrism's behaviour is unchanged.
  • No new model predicates.
  • tests/prism-guardian.test.js (new file, so the retained proof evidence stays valid) checks that:
    • a guardian joins a paper kit, and the old recovery device is retired;
    • the paper share alone is refused below the threshold;
    • the guardian's released share recovers, and it opens only on the device it was released to;
    • a share is refused to a guardian it was not made for.
  • docs/prism-id.md:
    • The replayed-kit residual is stated exactly. Where the recovery is not heard, a replay passes as a recovery.
    • The doc explains why no stitch element can close it for a paper-only kit.
    • It names guardians as the witness that closes it, added through replaceRecovery.

Why

After losing every device, nothing besides the kit knows that a recovery happened. A guardian is a witness that outlasts the person's devices: it confirms the person out of band and releases its share only once. The template frame will offer this quietly, next to the paper kit.

🤖 Generated with Claude Code

https://claude.ai/code/session_013Asa3NdLCxdzL1iQw9rg5T

The Open item said a replayed old recovery kit could only deny the id at
hosts. That holds only where the recovery that used the kit is heard: a
verifier that hears only the replay, because nothing retains the recovery
any more, takes it for a recovery. The item now says so, and gives why no
stitch element closes it for a kit of paper shares alone: a recovery after
losing every device leaves nothing but the kit that knows it happened, so a
later holder of a copy holds everything the person held and only the order
of the two uses differs. Guardians are that witness already (they confirm
the person out of band before releaseShare); a paper-only kit has none.
The Recovery paragraph's "the replay never acts as the person" is scoped to
where the recovery is heard. product/contracts.json regenerated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3NdLCxdzL1iQw9rg5T
A kit of one paper share has no witness of its use, so a copy of it
replays. Guardians are that witness: each confirms the person out of band
before releaseShare, and one that released its share has none left to give
a replay. replaceRecovery(session, shares, { threshold, guardians }) lets a
member, holding the current recovery device's shares, move the prism to a
new recovery device with fresh shares: the old recovery device (combined
from the shares, never kept by the member) binds the new one through
createRecovery and retires itself through revokeDevice, keeping what it
signed. Nothing else in the log changes; the member's keyring takes up the
rotation. With threshold 2 over a paper share and a guardian, the paper
alone no longer recovers.

The share combination recoverPrism did inline moves to recoverySecret,
which both use; recoverPrism's behaviour is unchanged. No model predicate
is added: thresholdMet, mayAdminister, bindAllowed, recoveryBindAllowed and
revocationCounts decide every step as before.

tests/prism-guardian.test.js: a guardian joins a paper kit and the old
recovery device is retired; the paper share alone is refused below the
threshold; with the guardian's released share recovery succeeds, and the
released share opens only on the device it was released to; a share is
refused to a guardian it was not made for. docs/prism-id.md describes
replaceRecovery and the residual it closes. product/contracts.json
regenerated.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3NdLCxdzL1iQw9rg5T
@afflom afflom changed the title docs(prism-id): state the replayed paper kit residual exactly feat(prism-id): guardians witness a paper kit's use (replaceRecovery), residual stated exactly Nov 14, 2026
@afflom
afflom merged commit 68a9222 into main Nov 14, 2026
2 of 3 checks passed
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.

2 participants