Scraping participation
Explicit consent and truthful foreground/background capability.
CareerVector participantBlueprint · careervector.blueprint-graph/v5
Twenty composable top-level diagrams plus recursively nested 21×21 semantic layers. Nodes descend; boundary arrows cross to neighbours.
Cell 4.1 · runtime · privacy · data · feedback
A CareerVector device may perform public acquisition work without exporting workspace identity or private career data.
Explicit consent and truthful foreground/background capability.
CareerVector participantNegotiates native or browser execution without exposing workspace state.
CareerVector deviceAdapter task plus causal routing receipt; no workspace identifier.
JobCache orchestratorPublic observation and execution outcome follow the receipt path.
JobCache ingestionExplicit consent and truthful foreground/background capability.
CareerVector participantNegotiates native or browser execution without exposing workspace state.
CareerVector deviceAdapter task plus causal routing receipt; no workspace identifier.
JobCache orchestratorPublic observation and execution outcome follow the receipt path.
JobCache ingestionCanonical architecture note
Open note ↗Let CareerVector's browser and desktop surfaces contribute public acquisition work and request public job knowledge without turning a private workspace into ingestion metadata.
| Path | Boundary behavior |
|---|---|
| Scraping contribution | Explicit participation; participant capability and execution feedback, no workspace state |
| Add job by URL | Fast public lookup/extraction plus a private workspace-job projection |
| Corpus lookup | Resolve public role/ad facts, then attach them locally without exposing shared IDs |
| Workspace reduction | Only named, consented pseudonymous facts or thresholded aggregates may cross |
| Public result delivery | Return a privacy-safe projection to the exact requesting workspace |
Browser/Tauri/container execution can share lease, receipt, failure, routing, and adapter contracts. CareerVector consent, workspace operations, local AI, and user-facing language remain product-owned.
workspace_id, CV/CL content, notes, preferences, and application history do not enter
extraction routing or JobCache Core.Two-way privacy tests, a browser and desktop contribution trace, fast-path outage behavior, consent withdrawal, participant erasure, and proof that no workspace identifiers reach Core.