01
Ask
Describe what you need to verify or start from a defined assessment.
→How it works
From evidence to assurance, without losing the chain of proof.
LedgerProof keeps the interface conversational while the assurance layer underneath remains governed, deterministic and evidence-led.
Workflow
A clear path from question to governed output.
02
Add evidence
Upload the operational records needed to test the requirement.
→03
Confirm scope
Confirm jurisdiction, assessment scope and field mapping before the governed run.
→04
Run governed tests
Deterministic controls evaluate the evidence. AI does not decide regulatory PASS or FAIL.
→05
Review the result
Open findings and trace every conclusion back to requirement, test and source evidence.
→06
Receive outputs
Download the Regulatory Assurance Report and retain the Evidence Pack.
Evidence chain
Every material conclusion stays traceable.
A reviewer should be able to move from the result back to the source records that supported it.
RequirementSR Code 3.4.3
→Governed testControl evaluation
→Source evidenceOperational records
→ResultRecorded outcome
Synthetic example
See what a governed result looks like.
This example uses synthetic data and mirrors the current public sample assessment for GB remote customer interaction.
GB · Remote customer interactionSR Code 3.4.3
R2-SYNTHETIC-RUN-001Example findingGB-CI-05 · Automated action absent
A required protective action was not evidenced after the governed trigger condition occurred.
Readable for people. Reconstructable for review.
Regulatory Assurance Report
Executive summary, control outcomes and detailed findings in a human-readable format.
Evidence Pack
Machine-readable provenance, source references and result identity for reconstruction.
Assessment workspace
Continue asking questions about findings and evidence after the governed run.