Brightwater Provisions, Inc.
LedgerPro to new ERP
- Cutover
- Go-live
- Books
- USD
Loading this view
Public demoView-only · fictional data
Brightwater Provisions, Inc.
LedgerPro to new ERP
Relay verified this migration , triggered by an approved change. It was computed from the inputs as they stand now.
Everything below is recorded by the run itself. Relay recomputes all of it from the inputs on every run; nobody types these numbers in.
Findings by severity
What it did to the issue log
An issue is resolved only when a run stops producing its finding — never by hand.
{
"counts": {
"findings": 65,
"issues_created": 65,
"staged_records": 24472,
"issues_reopened": 0,
"entity_candidates": 4,
"findings_by_severity": {
"low": 2,
"high": 10,
"medium": 7,
"critical": 46
},
"issues_verified_resolved": 0,
"reconciliation_discrepancies": 37
},
"stage_timings_ms": {
"load_ms": 75,
"total_ms": 7482,
"engine_ms": 3144,
"issues_ms": 1643,
"persist_ms": 2559
}
}The stages of the run, in the order Relay performs them, with how long each one took.
Total7,482 ms
Put this run beside an earlier one to see what a correction changed: which findings went away, which appeared, and which gates and reconciliations moved.
No other successful runs
A comparison needs a second successful run of this migration.
The input fingerprint identifies the exact inputs; the result fingerprint identifies what the engine produced from them. Identical inputs must produce an identical result fingerprint — that is how a run can be re-verified rather than trusted.