Repository navigation
Studio keeps a visitor's work sealed to their Prism ID (FA-93) - #238
Merged
Merged
Conversation
Built and proved by the locked SDK in the kernel pin workflow, from 3144154.
Every record of the visitor's work is sealed with Hologram's seal_bytes as it is stored and opened as it is read, under the workspace key the Prism frame keeps for this origin (UOR-Foundation/template FR-04), which only a device of their Prism ID opens. The cipher is synchronous, so the one database handle the host hands its writers seals inside their own transactions and no writer changed. Foundry's Prism kernel decides every step: open, the one move of the work kept before, and each read and store. A removed device's work, previews and covers are cleared. The visitor hears one sentence when something changed, each a statement of the experience module. Studio bundles the frame frame.lock pins (now UOR-Foundation/template@975f95c), so it opens offline and asks no network, and runs the kernel guest built from this model (the pin of #233, merged here so its commit stays reachable). Upstream Dyad's own tests, which Foundry never ran or typechecked, are removed. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…e workspace protocol
… visit opens fast The Performance gate refused a first visit's mobile LCP of 31 s: opening the workspace waited for the holospaces wasm. The core, loaded at start already, now provides hologram-space's PayloadCipher seam with ChaCha20-Poly1305 (13 KB), and a published .holo is recognised by its ref instead of by hashing it. Also: the perf gate measures the entry the page loads, not the Prism frame's; the experience module's lost brace after the Theater merge; rustfmt. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… the settings gate now names Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ich the workspace now asks on load On each load after the first the frame asks stitch's relay whether this device was removed, since the workspace opens only for a device still the ID's. The relay topics are hashes of secrets only the ID's devices hold; isPrismIdRelay admits exactly those. 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
A visitor's apps, chats, files, versions, prompts and settings sat in this browser's IndexedDB in the clear. Anything with access to the browser profile could read them, and they stayed on a device the visitor had removed from their Prism ID. FA-91 proved the kernel's decisions for a private workspace, but nothing asked them yet.
What the visitor experiences
Nothing, until something changes. Each record is sealed as it is saved and opened as it is read, with no step on the visitor's part. Then they get one sentence, each a statement of
FoundryExperience.lex.tex(workspaceWords):How (FA-93)
studio/shell/inference.js(workspace) wraps the one database handle the host gives every writer. Each value is sealed with Hologram'sseal_bytes(ChaCha20-Poly1305) on put and opened withopen_byteson read, inside the writer's own transaction, because the cipher is synchronous. No writer changed. The sealed bytes record the record's place, so a copied record doesn't open elsewhere..holobytes (checked by their address) and the audit.frame.lockpins (re-pinned to UOR-Foundation/template@975f95c; UOR-Foundation/template#96 fixed the template's own lock). It works offline and asks no network. The live frame loader in the sidebar is gone, and the shell keeps one frame for the page.blake3:f1c50fb2) with a merge commit, soKERNEL_REV's commit stays reachable. The guest Studio shipped before answeredinvalidto everyworkspacerequest.Evidence
private_workspace_fa_93runsin_tab_kernel_verdict.test.mjs, which builds every request with Studio's ownworkspaceRequestandopenFactsand asks the pinned guest.storage_request_browser.mjs(Studio CI, Chromium) runs the built shell's owninference.jsover the real guest, cipher and frame. It checks:shell_ui.test.mjsholds the six sentences to the spec.verification/private-workspace.md.workspace(), the handle Studio uses, instead of the plaindb(). These run only in Studio CI, not locally (they need the full lane).Ratchet
Upstream Dyad's own tests (
src/__tests__/and one test that read its fixtures) are removed. Foundry never ran or typechecked them, andVENDORED.mdrecords the removal. Net: −14,701 counted lines.Not covered
🤖 Generated with Claude Code