Episodes
Durable source events: messages, tool results, observations, documents, decisions, and application events. Episodes are never silently rewritten.
Product architecture
One database contract for living context.
SolarflareDB private-beta directions the part of agent infrastructure that becomes fragile when history, graph structure, semantic retrieval, and current truth live in separate systems.
4public usage meters
2× timerecorded + valid time
6 signalshybrid retrieval target
1 streamauthoritative replay contract
Data model
Context stays structured from source to retrieval.
Episodes preserve what happened. Facts capture claims. Entities and links create navigable structure. Temporal and provenance fields explain how the interpretation evolved.
Entities and relations
Typed, content-addressed nodes and hyperedges represent people, projects, concepts, sources, and higher-order relationships.
Facts through time
Claims carry recorded and valid time. Supersedes, retracts, and contradicts relationships preserve history while exposing current truth.
Query plane
One result, multiple signals, visible freshness.
Search results should identify what made them relevant and how far each derived index has caught up with the authoritative operation stream.
Semantic + lexical
Fuse embeddings with lexical retrieval instead of forcing one retrieval mode to carry every query.
Graph + exact
Follow typed neighborhoods, identifiers, aliases, sources, and access predicates before reranking.
Temporal + recent writes
Filter current or as-of truth and overlay authoritative recent writes until derived indexes reach the bookmark.
Consistency vocabulary
Say exactly what an acknowledgment means.
SolarflareDB should not flatten every guarantee into “eventually consistent.” Clients receive a bookmark and can select the durability or visibility boundary they need.
Leader-durable
Committed atomically to the authoritative shard, including idempotency record, HLC state, operation log, and index/archive outboxes.
Archive-durable
The operation is included in a verified packed segment and an immutable R2 root generation.
Search-visible
Lexical and vector indexes report watermarks at or beyond the write bookmark; recent writes bridge the gap before then.
Globally visible
Required regional materializers have reached the sequence under the graph’s replication policy.
API / Auth / Policytenant · principal · residency · limits
→
SQLite-backed shardsatomic graph state · log · indexes · outboxes
→
R2 + search projectionspacked WAL · checkpoints · vector · lexical · DR
Release sequence
Correctness first. Retrieval second. Scale without amnesia.
The supplied architecture has promising primitives, but launch must be gated by tests that prevent silent gaps, partial commits, unsafe sealing, unauthenticated tenancy, and false convergence.
Stage 0 · trustworthy semantics
Strict storage errors, checksummed segments, contiguous replay, atomic type/data batches, persistent clocks, safe mirror roots, and fail-closed policy.
Stage 1 · disk-backed scale
Sharded authoritative Durable Objects, bounded caches, packed R2 manifests, durable projection repair, and partial subscriptions.
Stage 2 · context quality
Hybrid retrieval, temporal truth, entity resolution, recent-write overlay, provenance explanations, and reproducible evaluation.
See the product contract, not just the diagram.
The console simulation turns the architecture into a developer journey with a key, write bookmark, provenance result, and budget guardrail.