Operator policy
Weights, budgets, source catalogue, and curiosity shape the routing field.
JobCache operatorBlueprint · careervector.blueprint-graph/v5
Twenty composable top-level diagrams plus recursively nested 21×21 semantic layers. Nodes descend; boundary arrows cross to neighbours.
Cell 3.1 · runtime · data · control · evidence
Resilient pull-based work distribution over unreliable actors, with raw evidence preserved before canonical publication.
Weights, budgets, source catalogue, and curiosity shape the routing field.
JobCache operatorRanks due work and actor class; mints lease and causal receipt.
Open layer ↘Priority lanes carry work, never participant credentials.
JobCache orchestratorPortals, feeds, APIs, discovery, and refresh signals.
Public webBrowser, Tauri, and container actors parse locally and return feedback.
JobCache participantsScoped transient deposits, immutable raw archive, and B2 overflow.
JobCache ingestionFingerprint, extract, embed, validate, and reconcile once per input and recipe.
JobCache pipelineReceipt validation and idempotent batch publication into Core.
JobCache CoreWeights, budgets, source catalogue, and curiosity shape the routing field.
JobCache operatorRanks due work and actor class; mints lease and causal receipt.
Open deeper layer ↘Priority lanes carry work, never participant credentials.
JobCache orchestratorPortals, feeds, APIs, discovery, and refresh signals.
Public webBrowser, Tauri, and container actors parse locally and return feedback.
JobCache participantsScoped transient deposits, immutable raw archive, and B2 overflow.
JobCache ingestionFingerprint, extract, embed, validate, and reconcile once per input and recipe.
JobCache pipelineReceipt validation and idempotent batch publication into Core.
JobCache CoreCanonical architecture note
Open note ↗Continuously acquire public job observations, preserve what was seen, extract and enrich it once per stable input, and publish a coherent result into JobCache Core without overwhelming the production database.
discover → lease → fetch → preserve raw → fingerprint → extract → enrich → validate
→ reconcile ad/role → publish batch → verify → age and refresh
| Concern | Authority |
|---|---|
| Raw observations | Corbet S3 with declared overflow/fallback storage |
| Unfinished work | Small rebuildable pipeline state, not CrateDB truth |
| Routing and feedback | JobCache's Sporewright application |
| Embeddings and selected analysis | Cloudflare AI behind content-addressed caches |
| Published public facts | CrateDB in JobCache Core |
The adaptive extraction orchestrator, browser/Tauri/container participants, routing receipts, S3 preservation, CrateDB deposit path, evidence aging, and source adapters exist in varying degrees of maturity. The complete cold processing ledger and atomic publish pipeline remain target evolution.
Load, drift, poison, retry, duplicate, outage, and heterogeneous-actor simulations plus a production trace from source discovery to a published role revision.