Make the calculation reproducible
Keep the schedule inputs, recorded configuration and computed answers together so another reviewer can check what was run. Schedule Forensics provides a JSON record and a verifier that recomputes the values it supports.
Inspect an actual replay
Open the guided demonstration and choose Reproduce the recorded calculation. Download the generated inputs and JSON record, then read the saved verifier transcript. It reports REPRODUCED and also states what was not checked.
The same report is available as HTML and Markdown for review. The JSON form is the machine-readable record used by the verifier.
What is recorded
- Digests identifying the input bytes.
- The parsed schedule network and recorded settings.
- Computed dates, floats and flags that can be compared on replay.
- Engine information and limitations needed to interpret the record.
The verification-format reference describes the structure. For an agreed enterprise deployment, retain the delivered engine revision and establish which environment was used.
What a replay proves
A successful replay establishes agreement for the values the verifier actually checks. Read its warnings: an evidence record does not automatically re-derive conformance verdicts or validate method choices.
Where a supported value diverges, the verifier identifies the affected activity and field. A divergence can follow from different inputs, settings or an engine revision; it is not an accusation of misconduct.
What it does not prove
Reproduction does not establish that the inputs are the contractual submission, that the calculation is correct, that its assumptions are true or that the record predates a dispute. Two runs can reproduce the same error. Compare relevant computed fields with the source scheduling application and read the measured evidence.
The record's preparation date comes from the local clock. No independent timestamp authority is supplied. Any draft certification text requires review and adoption by a qualified person; the software does not certify itself.
The sample replay runs on one environment. Cross-platform and cross-version acceptance belong in the deployment verification plan, not inferences from that single result.
Put it into your review process
Use the demonstration to agree what your organization needs to retain, reproduce and hand over. Request an enterprise package or arrange a walkthrough.
Source: web/pages/verification.md. Source commit date: 2026-09-11.