Change & Motion
Separate receipt readiness, bounded release change, provisional motion, and verified trajectory evidence.
Not assignedEvidence detailsChecking
Change & Motion content
Upload receipt time selects the window. Schedule Data Date orders the motion read. A receipt without a parseable schedule stays visible but does not become a release.
Receipt count, analyzable releases, and unique Data Date samples are separate facts.
Older-date corrections remain visible by receipt time; only the newest parseable receipt for each Data Date enters the derivative series.
Choose a project.
Stable task-code membership supports a provisional reading. A governed mapping is required before a series conclusion is verified.
Load a project to compare releases.
Rates use elapsed calendar days between schedule Data Dates. They are schedule movement signals, not causes or finish commitments.
The project’s own updates cut it into windows. Each window shows how far the forecast completion moved, the Longest Path at both ends, and the changes and rewritten actual dates inside it. The windows add up to the whole movement; any part they cannot carry is shown as a residual. It reads what moved and when, not whose it was.
Read a project to see its windows.
Practice history gaps and re-declaration — synthetic, resettable demo
Review legacy subjects before declaring them again. A new declaration seals today's attestation; unavailable older content stays a history gap.
Reading authorized projects…
Review status and evidence steps
Steps of the decision on this page.
