Substrate
Bitemporal context engine that remembers what your team knew and when. Every fact, graph link, and interaction is versioned across two time axes.
| Entity | Property | Value | Valid Time | Tx Time |
|---|---|---|---|---|
| deploy:api-v2.3 | status | rolled back | Apr 9, 14:22 | Apr 9, 14:25 |
| ticket:MAI-142 | assignee | sakthi | Apr 8, 09:00 | Apr 8, 09:01 |
| model:gpt-4o | p95_latency | 1,240ms | Apr 9, 12:00 | Apr 9, 12:05 |
| policy:rate-eng | limit | 500 req/h | Apr 7, 00:00 | Apr 7, 10:30 |
Valid time — when it happened Tx time — when recorded
Key capabilities
Bitemporal versioning
Track both when a fact was true in the world (valid time) and when the system recorded it (transaction time). Full audit trail without data loss.
Cross-source context graph
Facts from connectors, registry artifacts, and team interactions form a unified knowledge graph. Query across sources, not within silos.
Team memory
Context persists across sessions and team members. No more rebuilding context from scratch — the substrate retains institutional knowledge.
Governed access
Substrate queries respect the same policy engine as everything else. Data routing, role-based access, and audit logs apply to context retrieval.