What we knew then
Waiting for a query.
Checking your session...
Schedule History
Inspect bitemporal schedule observations without flattening history.
Data DateNot read yet
Evidence detailsChecking
Project ID
Not assignedData Date sourceLoading the accepted schedule date.Checking effective role and scopeBounded evidence only · original schedule source remains protectedSchedule History content
Bitemporal contractValid time and knowledge time answer different questions
UnknownA later correction changes current belief without rewriting what evidence was available earlier.
Never zero
Evidence timeline
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.
Valid timeWhen the work or fact appliesKnowledge timeWhen the system could know it
Read-only history surface. Unknown is not zero, a late correction does not rewrite earlier belief, and source bodies are never shown.
Choose the question
bounded readStart with one activity and two knowledge clocks. Keep the frame explicit.
Choose an activity to begin. The page will not infer a date or baseline.
Knowledge timewhat the system could know →
thennow
Corrections move along knowledge time; they do not erase the earlier frame.
Valid timewhen the schedule fact applies →
What we believe now
Waiting for a query.
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.
Observed import ledger
A bounded list of accepted observations, with identity and provenance only.
Loading temporal imports...
Hierarchy lens and evidence states
AS_WAS
Use the hierarchy and membership evidence that existed at the historical frame.
RESTATED
Use a later/current hierarchy to restate historical evidence. It is a different answer, not a correction.
Unknown
Evidence is absent or incomplete. The product keeps that distinction visible.
Conflict
Contradictory assertions are held for review instead of choosing by insertion order.
Champion / challengerCompare evidence-equivalent report layouts
Loading layoutsOnly 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
Decision roadmapEvidence readiness, not project progress
Checking evidenceSteps update from visible page evidence. Blocked and withheld states name the boundary; no completion percentage is inferred.
Discussion questions and talking points
Discussion guideQuestions and talking points
bitemporal read not rewritten historyObserved → derived → withheld remains explicit. These talking points stay tied to the selected evidence; they are not an unrestricted database question box.
Observed selected source valuesDerived visible inputs and formulaWithheld unsupported or unavailable
Current context
Unavailable context remains explicitly not supplied.
This talking point preserves the page’s evidence and authority boundary.