A read-only route registry that defines how Discovery Engine readiness, provider registry, source scoring, deduplication, conflict detection, Vault ingestion, claim cards, visual observations, and capsule candidates will eventually route into the Universal Intelligence Hub.
Every TheoB pathway can move through Past, Present, and Future without losing context.
Read current signals, conditions, and live context.
Voice ready
Discovery-To-Hub Route Registry prepares TheoB to route source-linked discovery intelligence into the Universal Hub without activating live search, provider retrieval, Vault writes, Hub node writes, or agent handoff. Routes are maps, not pipes. Big difference. One keeps order. The other turns the basement into a swimming pool.
Discovery-To-Hub Route Registry is active as a non-destructive route registry. TheoB can define route maps, route signals, safety rules, future route shape, and route receipt shape, but it cannot activate live Discovery-to-Hub routing, store routes, write Hub nodes, write Vault records, run live search, retrieve provider data, issue truth verdicts, hand routes to agents, or mutate production yet.
Route Discovery Engine foundation state, positioning, safety posture, and live-disabled search readiness into Universal Hub visibility.
theob-discovery-engine-foundation → universal-intelligence-hub-foundationDiscovery route visibility cannot activate live search.Route provider readiness, provider classes, retrieval boundaries, and disabled credential state into hub domain visibility.
discovery-provider-registry → universal-intelligence-hub-foundationProvider visibility cannot attach credentials or retrieve live data.Route source authority, citation trail, freshness, conflict context, and scoring readiness into hub evidence navigation.
discovery-source-scoring-readiness → universal-intelligence-hub-foundationSource scores cannot become automatic truth.Route duplicate cluster readiness, duplicate types, and no-deletion boundaries into hub evidence compression visibility.
discovery-deduplication-readiness → universal-intelligence-hub-foundationDeduplication routes must not delete sources.Route conflict types, conflict severity, unresolved disagreement, and automatic-verdict-disabled state into hub review visibility.
discovery-conflict-detection-readiness → universal-intelligence-hub-foundationConflict routing cannot issue verdicts.Route future Vault record shapes, ingestion readiness, database-write-disabled state, and capsule candidate boundaries into hub evidence structure.
discovery-vault-ingestion-readiness → universal-intelligence-hub-foundationVault route visibility cannot write to storage.Prepare future routing of discovery receipts, scoring receipts, dedupe receipts, conflict receipts, and Vault ingestion receipts into the hub receipt ledger.
discovery-readiness-chain → hub-receipt-ledgerReceipt routing waits until ledger storage rules exist.Prepare future claim-card routing into hub nodes with source trail, confidence, conflict, dedupe, and rights context.
claim-card-records → universal-hub-nodeClaims must not enter the hub without source trail and conflict state.Prepare future routing of visual observations from Discovery into hub visual domains without flattening modality boundaries.
multimodal-observation-records → visual-and-schematic-domainVisual observations are not automatically verified claims.Prepare future routing of capsule candidates into hub capsule memory visibility before compression or reactivation.
capsule-candidate-records → capsule-memory-domainCapsule candidates are not stored capsules.Show Discovery Engine Foundation readiness before Hub routing.
Route use: hub domain readinessShow that live search remains disabled.
Route use: safety boundaryShow that live provider retrieval remains disabled.
Route use: provider safetyShow that source scoring readiness exists but live scoring remains disabled.
Route use: evidence qualityShow that deduplication readiness exists but live dedupe and deletion remain disabled.
Route use: duplicate cluster contextShow that conflict detection readiness exists but automatic truth verdicts remain disabled.
Route use: conflict contextShow that Vault ingestion readiness exists but database writes remain disabled.
Route use: hub evidence structureShow that Universal Hub Foundation is ready to display routes without activation.
Route use: hub destinationShow that Hub Cockpit Binding Readiness can display route state.
Route use: cockpit visibilityShow that Discovery-To-Hub Route Registry cannot mutate production.
Route use: global safetyDiscovery-To-Hub routes define future routing visibility, not live data transfer.
Do not confuse route registry with live routing.Every future Discovery-to-Hub route must preserve source trail, provider context, score context, dedupe context, conflict context, and rights state.
No naked claims in the Hub.This layer cannot activate live search, provider retrieval, scraping, API retrieval, or universal search.
Discovery readiness is not discovery execution.Discovery-to-Hub routing cannot write Vault records, hub nodes, receipt ledgers, capsules, or database records.
No writes through a route map.Discovery routes can expose conflict context but cannot decide truth.
Routing evidence is not judging evidence.Claim cards, receipts, visual observations, and capsule candidates require review before future hub routing.
The Hub should receive governed evidence, not raw noise.Discovery-to-Hub routes cannot hand context to agents or trigger actions.
Routes do not become agents.This registry does not mutate routes, registries, hub nodes, Vault records, capsules, agents, or production.
No writes. No sync. No surprise.