Tauri v2 shell
Remote-loads the production Svelte workspace from allowlisted origins.
CareerVector desktopBlueprint · careervector.blueprint-graph/v7
Graph explorer
Twenty composable top-level diagrams plus recursively nested 21×21 semantic layers. Nodes descend; boundary arrows cross to neighbours.
Nested layer 1 · product · runtime · privacy · evidence
CareerVector Tauri desktop client
The Tauri v2 app loads the production browser UI inside a controlled native shell and adds adapter execution, native fetch/render, signed updates, and OS integration without creating an offline workspace truth.
- Tauri v2 shell to Allowlisted IPC bridge: invoke allowlisted command
- Allowlisted IPC bridge to Native adapter runtime: execute adapter
- Tauri v2 shell to Network workspace: load canonical UI
- Native adapter runtime to Native fetch + render: fetch public source
- Vendor AI host seam to Network workspace: typed tools only
- Tauri v2 shell to Signed updater + bundles: verify + install
- Signed updater + bundles to OS integration: package capability
Allowlisted IPC bridge
Only approved production origins may invoke explicit native commands.
CareerVector desktopNative adapter runtime
Rust router exposes the linked JobCache adapter families and capability report.
CareerVector desktopNetwork workspace
The same D1/Yjs state remains canonical; the shell is not an offline editor or local database.
CareerVector D1/YjsNative fetch + render
Native HTTP and hidden WebKit rendering extend public acquisition beyond browser CORS.
CareerVector desktopVendor AI host seam
Desktop may host the same bounded connector and tool contract as the other clients.
CareerVector desktopSigned updater + bundles
Linux AppImage, deb, and rpm artifacts update the shell independently from the network UI.
CareerVector releaseOS integration
Single instance and filesystem/OS capabilities are explicit; tray, notifications, and deep links remain phased.
CareerVector desktop01 · perspective · as-built Tauri v2 shell Remote-loads the production Svelte workspace from allowlisted origins.
CareerVector desktop02 · boundary · as-built Allowlisted IPC bridge Only approved production origins may invoke explicit native commands.
CareerVector desktop03 · service · as-built Native adapter runtime Rust router exposes the linked JobCache adapter families and capability report.
CareerVector desktop04 · store · as-built Network workspace The same D1/Yjs state remains canonical; the shell is not an offline editor or local database.
CareerVector D1/Yjs05 · service · as-built Native fetch + render Native HTTP and hidden WebKit rendering extend public acquisition beyond browser CORS.
CareerVector desktop06 · boundary · target Vendor AI host seam Desktop may host the same bounded connector and tool contract as the other clients.
CareerVector desktop07 · boundary · as-built Signed updater + bundles Linux AppImage, deb, and rpm artifacts update the shell independently from the network UI.
CareerVector release08 · service · target OS integration Single instance and filesystem/OS capabilities are explicit; tray, notifications, and deep links remain phased.
CareerVector desktop
Flows
- Tauri v2 shell → Allowlisted IPC bridge invoke allowlisted command
- Allowlisted IPC bridge → Native adapter runtime execute adapter
- Tauri v2 shell → Network workspace load canonical UI
- Native adapter runtime → Native fetch + render fetch public source
- Vendor AI host seam → Network workspace typed tools only
- Tauri v2 shell → Signed updater + bundles verify + install
- Signed updater + bundles → OS integration package capability
Canonical architecture note
Open note ↗CareerVector Tauri Desktop Client
The desktop app is a thin native shell around the production Svelte workspace. The UI remains network-loaded and canonical state remains in D1/Yjs; the desktop is not an offline-first editor or a fork of CareerVector.
The native boundary adds allowlisted IPC commands, the Rust JobCache adapter router, native HTTP, hidden-WebKit rendered fetch, participant capability reporting, single-instance behavior, signed updates, Linux bundles, and later OS integrations. Remote UI origins and native commands are explicitly allowlisted because network-loaded code must not receive ambient device authority.
The Linux MVP and native adapter/fetch-render paths are as built. Multi-OS release coverage, broker lease/deposit completion, tray, notifications, deep links, and the exact vendor-AI host placement remain phased or target work.
Completion evidence covers production-origin denial, IPC capability boundaries, adapter and render behavior, canonical workspace convergence, bundle installation/launch, signature/update and rollback, participant privacy, and parity with browser-visible workspace results.