Six moments, and one reading of the code.
A number is challenged, a change is waiting for approval, or a system is about to be switched off. A deal needs diligence, two computations disagree, or the one person who understands a system is leaving. Each of those moments has its own page, and they are the audit, the change, the migration, the transaction, the reconciliation and the departure.
Six moments
Every one of them starts with read access to the source, under your controls. In the deployment you run, the reading runs on infrastructure you control and the record stays there. How the reading works across your systems is set out on the Product page.
Can we trace this reported value and defend the answer?
A reported value is challenged.
A source-linked route from the reported value to its producing expression, including the conditions and dependencies established by the supplied materials.
Bring The code, configuration and job schedules on the path to the figure, under your access controls.
Explore the auditWhat can this proposed change reach?
A release or remediation proposes a source change.
The changed relationships and their bounded downstream structural reach, separated from unchanged and unresolved paths.
Bring The current code and the proposed change, with the configuration and job schedules that connect them.
Explore the changeWhat must be preserved before this system is replaced?
A system is being replaced, retired or moved.
A source-linked inventory of the logic, dependencies and unresolved areas that must be considered before replacement or retirement.
Bring The code, configuration and job schedules of the system being replaced, and of the systems it talks to where available.
Explore the migrationWhat do the supplied materials establish, and what remains unavailable?
A transaction requires technical diligence.
The relationships the accessible materials support, the evidence that can be inspected and the gaps that prevent a conclusion.
Bring The repositories, configuration and workflow definitions in the data room, and the requests that went unanswered.
Explore the transactionWhere do these two computations first diverge?
Two computations that should agree give different answers.
The earliest structural divergence the supplied materials establish, with the relevant source spans and conditions retained for review.
Bring The code, configuration and schedules behind both computations, and the shared inputs they start from.
Explore the reconciliationWhat knowledge needs to remain when the author leaves?
A key system author is leaving.
Source-linked documentation of the relationships in scope, with the author's answers, unresolved questions and disagreements retained.
Bring The code, configuration and schedules of the system, and time with its author before they go.
Explore the departure