Knowledge requires
a Clock
The dashboard is accurate. It is also describing a world that has already changed. Truth needs a time boundary.
Part of Trustworthy Autonomy ↗Chapters in this collection 06 / 09
Operational knowledge has a time dimension. A fact needs to say when it held, when the system learned it, and how long it can support a decision.
Imagine an agent checks a service at 14:00. Everything looks healthy. At 14:03, a feature flag sends requests through a new dependency. At 14:06, a delayed dashboard sample arrives, still showing the quiet period before the switch.
The sample was retrieved recently. The world it describes is older.
The service kept its name#
The Ship of Theseus asks what remains the same when a vessel's parts are replaced over time. Software gives that question an operational twist: a service keeps its name while its code, dependencies, traffic, and owners change beneath it.
Identity gives us continuity. It does not guarantee that yesterday's description still fits.
A remembered latency baseline can be useful under one architecture and misleading under another. A dependency map can become obsolete with a feature flag. Even an approval can expire while an agent is preparing an action.
Three clocks, three questions#
Valid time: when was this true in the world?
Recorded time: when did the system learn it?
Validity horizon: until when—or until which event—may it support this decision?
Keeping these separate lets us assess a past decision fairly. Information that arrived later should not be smuggled into the record of what an agent knew earlier.
A fresh delivery of old evidence
An illustrative timeline. Follow the sample's time, not just its arrival.
- Observed window
- 13:55–14:00
- Topology
- Version A
Healthy under the current topology
- What happens
- The service is within its expected range. The assessment is valid for this topology until the next check or a relevant change.
- What it means
- The verdict has conditions; its label is not a permanent property of the service.
- What the system does
- Record both a reassessment deadline and invalidating events.
Inspect the example record
{
"verdict": "healthy",
"valid_from": "14:00",
"valid_through": "14:05",
"reassess_if": [
"dependency change",
"traffic shift"
],
"topology_version": "A"
}- New dependency
- Risk service
- Topology
- Version B
A flag changes the request path
- What happens
- A feature flag begins routing checkout requests through an additional service.
- What it means
- The previous assessment no longer covers the current dependency graph, even though its scheduled deadline has not arrived.
- What the system does
- Invalidate the earlier verdict and gather evidence for the new path.
Inspect the example record
{
"event": "feature flag enabled",
"effective_at": "14:03",
"previous_verdict": "invalidated by topology change",
"next_action": "reassess"
}- Sample covers
- 13:58–14:02
- Received
- 14:06
Recent retrieval, older reality
- What happens
- A delayed sample shows normal behavior before the feature flag changed the topology.
- What it means
- It can help reconstruct the earlier period. It cannot establish the health of the new request path.
- What the system does
- Retain the sample as historical evidence and declare the current coverage gap.
Inspect the example record
{
"valid_from": "13:58",
"valid_to": "14:02",
"recorded_at": "14:06",
"covers_current_topology": false,
"current_verdict": "insufficient evidence"
}Expiry is part of meaning#
Some facts expire after minutes. Others remain useful until a particular change: a new architecture, a transferred ownership role, or a revoked approval. The right horizon depends on the claim and the decision.
Store topology, configuration, exposure, and ownership as they were at each checkpoint. Compare explicit baseline and evaluation windows. Mark delayed or incomplete telemetry instead of treating retrieval time as freshness.
Memory should arrive as a dated prior: a reason to investigate, with conditions under which the lesson applies. Live evidence must establish what is happening now.
Test the clock by replaying an incident with late telemetry and a midstream configuration change. The agent should distinguish what was true, what was knowable, and what is still safe to rely on.
A fact can remain historically true long after it stops being useful permission to act.
Further reading: Plutarch's Life of Theseus recounts the ship whose timbers were gradually replaced.