Skip to content

Prism ID: an app's pages on every device of the ID meet on a sealed channel (FR-05) - #97

Merged
humuhumu33 merged 2 commits into
mainfrom
app-channel
Nov 16, 2026
Merged

humuhumu33 merged 2 commits into
mainfrom
app-channel

Conversation

@humuhumu33

Copy link
Copy Markdown
Contributor

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.
  • Sealing. Every message is sealed with sealPrivate, and one that doesn't open is dropped.
  • Removal. A removal rotates the key, so the remaining devices move to a topic the removed device can't derive.
  • The ratchet shrinks (−3). The bar's three panels share one placement helper (placeUnder), and elements made with several properties use Object.assign.
  • frame.lock is 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_05 derives 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:identity has two pages of one app hear each other: 17 of 17 pass.
  • Planted defect: sending unsealed was rejected (not ok 4) and restored. It is recorded in TEMPLATE-VERIFICATION.md.
  • Regression gates: the FR-01 to FR-03 gates pass on the changed frame.

🤖 Generated with Claude Code

…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>
@humuhumu33
humuhumu33 requested a review from afflom as a code owner November 16, 2026 21:10
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@humuhumu33
humuhumu33 merged commit b64cc73 into main Nov 16, 2026
4 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.

1 participant