Repository navigation
Prism ID: an app's workspace key, sealed to the ID and carried when it joins (FR-04) - #95
Merged
Merged
Conversation
…t joins (FR-04) The frame hands an app 32 bytes only a device of the visitor's Prism ID opens, sealed under the ID's private boundary key. Joining or recovering the ID reseals it for that ID in the same write that keeps the device; a removed device keeps its work locked. The ID card says when an app holds one. The popovers in panels.css share one surface and title rule and relay messages parse in one place, so the counted lines shrink. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… bundle its locked copy Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 16, 2026
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.
Why
A Prism app that keeps a visitor's work in the browser had no way to keep it private to that visitor. The frame holds the visitor's Prism ID, but it gave an app nothing to seal with. Foundry is the first app that needs this: its apps, chats and files sit in IndexedDB in the clear.
What changes
frame.workspaceKey()(FR-04). The frame hands an app 32 bytes that only a device of the visitor's Prism ID opens. The frame makes them once, seals them under the ID's private boundary key (sealPrivate), and keeps only the sealed copy in this origin'sprism-idstore. The app never stores the key.removed.{ replace: true }starts a new one.An unpublished frame imports its panels from beside it, as
panels.mjsalready imports Prism ID. An app can then bundle its locked copy of the frame (Foundry will), with no fetch to this site at run time.The ratchet shrinks. The three popovers in
panels.cssshare one surface and title rule, and the panel's relay messages parse in one place. Net change: −6 counted lines.Evidence
frame_fr_04runsopenWorkspaceandcarryWorkspacein Node: make, reopen, refuse another ID, carry, refuse a carry from the wrong ID, and reseal after a rotation that the removed device cannot open.npm run test:identitycarries the key across two apps in Chromium: stable across calls, carried through the link and six-digit code,removedafter the device is removed, and replaced on request. 16 of 16 pass.TEMPLATE-VERIFICATION.md, "An app's workspace key (FR-04)". Both were rejected and both restored green.Not in this PR
Foundry's use of the key (sealing its store) lands in UOR-Foundation/foundry after this merges and its frame is re-pinned.
🤖 Generated with Claude Code