01 / Read a report against a moment
Arrived recently.
Still an old observation.
Move the reference time backwards. A later report cannot become evidence for an earlier decision.
Follow one report
A report is “fresh enough” if it has arrived by the reference and describes an event no more than the selected horizon earlier. The four labels are not a proportional time axis. This is a display rule, not a guarantee that the situation has stayed the same.
02 / Inspect the whole picture
Which reports belong
in this review?
Readiness snapshots
Each snapshot compares planned and reported overall readiness at the same event time. Select a bar to set the decision reference to that time. Reports received later are withheld.
Planned and reported progress
Plan and actual refer to the task’s event time. A stale report describes that earlier point; this page does not project it forward. Open a task to author its full report, including values that may not yet be available to the organiser.
| Task | Planned / actual | Reported gap | Evidence at reference |
|---|
Author a task report — including later values
Editing replaces this report. It does not record that work was performed. Download the trace before replacing anything you want to keep.
Six signals, different delays
Inspect a signal without changing the log. A draft refresh request remains a draft until you choose to add it to the event records.
| Signal | Value | Event age | Arrival age | Evidence |
|---|
What was done, and what followed?
A record joins context, an action and an observed outcome or pending response. Their order and delay do not establish that the action caused the outcome.
Add an event record
Try a different trace or download this one
The seeded generator replaces the readiness snapshots, task reports and signal values; it keeps the reference, horizon and existing event records. Slower arrival changes only signal receipt times. Reset restores the initial example and removes edits and added records.
Data stays in this page’s memory. Reloading starts again. The download includes the full trace, including reports after the selected reference.
The distinction
An information state has a history.
At a decision moment, a report can be unavailable, available but old, or available and recent enough for the stated purpose. Keeping those distinctions in the state lets a later review ask what the organiser could have known, instead of silently giving an earlier decision a later report.
A freshness horizon is a modelling choice. The same delay may matter differently for a fast-changing wind reading and a completed briefing. This deliberately simple example applies one horizon to expose the question; it does not choose a useful horizon for real operations.
Framework, temporal binding and what is established
A place for arriving information
Powell’s framework distinguishes state, action, new information, transition and objective. The decision view carries the reference and received reports with their times; the surrounding authoring trace also retains later reports for exploration. A refresh request is a possible information-gathering action; a later report could change the next state.
This page inspects the information boundary. It does not solve a shuttle dispatch policy or compute an optimal freshness horizon.
A separate line of research
Research on temporal perception asks how experienced timing relates to events and actions. It motivates care with time labels, but does not validate a minute-scale project control threshold. Temporal recalibration and intentional binding are also distinct phenomena.
The horizon, data and review flags here are authored rules. Checks establish how this finite implementation classifies records and preserves timing; they do not establish causation or improved decisions.
Cai, Stetson and Eagleman (2012): temporal recalibration and intentional binding · Construction and verification · Inspect the model