Schedule History
Inspect bitemporal schedule observations without flattening history.
Not assignedEvidence detailsChecking
Schedule History content
An unknown value is never shown as zero.
Keep the schedule story intact.
Snapshots are observations, not replacements. Compare what was true in the project with what the team knew at the time.
Each release keeps its own identity. The Data Date is when the schedule was statused; Received is when this account got the file. A late or re-issued release sits beside the earlier ones and never replaces them.
Waiting for the selected project.
Start with one activity and two knowledge clocks. Keep the frame explicit.
Corrections move along knowledge time; they do not erase the earlier frame.
What we believe now
How to explain a temporal change
- 1. Release pair
- The two immutable reviews or knowledge frames selected for comparison.
- 2. Identity basis
- The release-scoped activity identity and any governed cross-release mapping.
- 3. Fields changed
- Only fields observed in both selected frames; unavailable values remain unknown.
- 4. Calculation and units
- The explicit then-versus-now calculation, retaining native date, hour, and count units.
- 5. Interpretation limits
- A temporal difference does not establish cause, responsibility, entitlement, commitment, or P6 verification.
A bounded list of accepted observations, with identity and provenance only.
Hierarchy lens and evidence states
Use the hierarchy and membership evidence that existed at the historical frame.
Use a later/current hierarchy to restate historical evidence. It is a different answer, not a correction.
Evidence is absent or incomplete. The product keeps that distinction visible.
Contradictory assertions are held for review instead of choosing by insertion order.
Only reading order changes. Values, citations, authority, and review provenance stay fixed.
Reactions are observations; they never change the champion by themselves.
Review status and evidence steps
Steps of the decision on this page.
