Advanced Concepts
Temporal Context and the Event Clock
Most systems can tell you what's true now. Almost none can tell you what was true at a specific point in the past, or how truth evolved over time. This temporal dimension is critical for AI agent reasoning.
Why Time Matters
Consider a simple fact: “Paula works at Microsoft.” This seems straightforward, but it's incomplete. When did she start? Does she still work there? What was true in 2022?
Existing knowledge graphs and databases generally don't solve this. They define entities like Person and Organization, but they don't have native primitives for “this relationship was true from date X to date Y.”
“We've built trillion-dollar infrastructure for what's true now. Almost nothing for why it became true.”
For AI agents making decisions, this temporal blindness is a critical limitation. Agents need to understand not just current state, but historical patterns and precedent.
The Two Clocks Problem
Every system has two fundamentally different types of time tracking:
State Clock
What's true right now. This is what traditional databases excel at.
- • Current account balance
- • Latest configuration value
- • Current employee roster
- • Present deal status
Event Clock
What happened, in what order, with what reasoning. This barely exists in most systems.
- • Why the balance changed
- • Who changed the config and why
- • History of role changes
- • Evolution of deal terms
The event clock tells you how the system behaves—and behavior is what you need to simulate and predict. This is what experienced employees have that new hires don't: a better mental model of how things have changed over time.
Example: Configuration Change
The config file says timeout=30s. It used to say timeout=5s. Someone tripled it.
- State clock knows: Current value is 30s
- Git blame knows: Who changed it
- What's missing: The reasoning is gone
Temporal Validity
Temporal validity is the practice of tracking when facts are true, not just what facts are true. It requires adding time boundaries to every piece of information:
{
"fact": "Paula works at Microsoft",
"validFrom": "2020-03-15",
"validUntil": "2024-08-30",
"source": "hr_system_record_#12345",
"confidence": 0.99
}
{
"fact": "Paula works at Google",
"validFrom": "2024-09-01",
"validUntil": null, // Still current
"source": "linkedin_profile",
"confidence": 0.85
}Key Capabilities of Temporal Validity
- ✓Point-in-time queries: “What did we believe about this account when we made that decision?”
- ✓Change tracking: “How has this customer's tier changed over time?”
- ✓Precedent search: “Find similar decisions from the same time period.”
- ✓Decision replay: “Recreate the context that existed when this was decided.”
Fact Resolution
When you extract facts from content, you get assertions—not necessarily truth. Content can be wrong, outdated, or contradictory.
The Challenge
“The customer is renewing” might appear in a March email. “The customer churned” might appear in a September Slack thread. Both are facts extracted from content. But they can't both be currently true.
Fact resolution is the process of determining what's canonical, what's superseded, and what's corroborated. It requires judgment about:
- ●Temporal ordering: Which information is more recent?
- ●Source authority: Which source is more authoritative?
- ●Corroboration: Do multiple sources agree?
- ●Update semantics: How does later information update earlier assertions?
“Freshness and recency are not the same as accuracy and precision. Just because data is old and obscure doesn't mean it's not still valid.”
Implementation Approaches
Building temporal context into your systems requires specific infrastructure choices:
1. Bitemporal Modeling
Track both “valid time” (when the fact was true in the real world) and “transaction time” (when we learned about it). This enables both historical queries and audit capabilities.
2. Append-Only Event Stores
Never delete or update events. Always append new events that reference previous ones. This preserves the complete history for replay and analysis.
3. Temporal Indexes
Build indexes that support efficient queries across time dimensions: “What was true at time T?” “When did X become true?” “What changed between T1 and T2?”
4. Versioned Facts
Maintain versions of facts as they evolve. Each version includes the validity period, source, and confidence level. Superseded versions remain queryable.
Impact on AI Reasoning
Temporal context fundamentally changes what AI agents can accomplish:
Without Temporal Context
- • Can only see current state
- • No understanding of trends
- • Can't find historical precedent
- • No context for why things are as they are
With Temporal Context
- • Understands evolution over time
- • Can identify patterns and trends
- • Finds relevant historical decisions
- • Reasons about cause and effect
The path to economically transformative AI might not require solving continual learning. It might require building world models that let static models behave as if they're learning—through expanding evidence bases and inference-time compute to reason over them.
Build Time-Aware AI Systems
Join the Context Graph Marketplace to explore temporal context infrastructure.
Join the WaitlistReferences
This article is based on insights from the following sources:
- •Kirk Marple (CEO, Graphlit) — “Context Graphs: What the Ontology Debate Gets Wrong” on X/Twitter
- •Animesh Koratana (CEO, PlayerZero) — “How to build a context graph” on X/Twitter