Capability
Replay & History
Reconstruct how understanding changed.
Evidence levelE1Architecture Defined
The functional gap
Reviewing the past with today's knowledge rewrites it. What was known then, and what is known now, must stay two different things or the record cannot be trusted.
From inputs to outputs
Takes in
- Every state as it was held at the time
- Later observations and corrections
- A moment chosen by the reviewer
Does
Rebuilds the state as it stood at the chosen moment and, apart from it, shows what later review added. Neither replaces the other.
Hands on
- The state as known then
- What later review added, labelled as later
- A record that is never rewritten
A worked example
Three steps from a synthetic scenario, in relative terms.
| Step | What is seen | What is stated |
|---|---|---|
| 1 | The reviewer picks an earlier moment | The state as held then appears |
| 2 | A later source had also seen the object | It is shown, marked as later knowledge |
| 3 | The reviewer returns to the present | Nothing in the record has changed |
- First observation
- Second source joins
- Gap
- State updated
- Rest state
| Time (relative) | Value |
|---|---|
| 6 | First observation |
| 28 | Second source joins |
| 50 | Gap |
| 72 | State updated |
| 94 | Rest state |
Confidence and uncertainty in this function
The confidence shown for a past moment is the confidence held at that moment. Later confidence appears beside it and is labelled later.
Evidence and maturity
This page claims nothing above the level of the projects it rests on.
- Airspace Intelligence Core PlatformEvidence level: E1 · Architecture Defined
What this does not claim
- Replay shows what the system held; it does not show what really happened.
- The page describes the principle and shows no real recording.
- Stored states are kept as designed, and the page states no retention period.