Repository navigation
Prism ID: an app's pages on every device of the ID meet on a sealed channel (FR-05) - #97
Merged
Merged
Conversation
…hannel (FR-05) frame.appChannel(listen) gives an app send(value) and listen(value) across the visitor's devices: a relay topic only the ID's devices derive, per app, from the current private boundary key, every message sealed with sealPrivate. A removed device is left on a topic the others have moved from. The bar's panels share one placement and elements are made with Object.assign, so the counted lines shrink; frame.lock is rewritten in the same change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.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.
Why
Foundry keeps a visitor's work sealed to their Prism ID, but only on the device that made it. To bring two of the visitor's devices together, an app's pages need a way to find each other that only the ID's devices share. Only the frame holds the ID's key.
What changes
frame.appChannel(listen). It resolves to{ send(value), stop() }. The pages of one app on every device of the visitor's Prism ID meet on a relay topic,prism-app:plus an HMAC of the app's origin under the ID's current private boundary key (appTopic). Only the ID's devices derive it, and each app gets its own.sealPrivate, and one that doesn't open is dropped.placeUnder), and elements made with several properties useObject.assign.frame.lockis rewritten in the same change. FR-04's PR missed that, which frame.lock: the frame FR-04 changed, so every app can pin it #96 fixed.Evidence
frame_fr_05derives the topic for two linked devices, another app and another ID. It checks that a sealed message opens on the other device, and that after a removal the remaining device's topic is one the removed device can't derive.npm run test:identityhas two pages of one app hear each other: 17 of 17 pass.not ok 4) and restored. It is recorded inTEMPLATE-VERIFICATION.md.🤖 Generated with Claude Code