Evidence
Evidence for every record.
Every check leaves a result with a fingerprint of exactly what was checked, in a tamper-evident record the app can add to and never rewrite. Each week the results arrive as one report, with a PDF pack to hand to an auditor, an insurer or a customer.
The weekly pack
Each Monday the week's report goes to the admins, in the app and by email, and in the app the same report downloads as a PDF. This one is for a demonstration business, made by the same code from a week of its records.
FourWinds
Weekly report
A demonstration business
26 Oct to 2 Nov 2026 · every name and number made up
Controls
- Access a review removed is gone within a week0 pass · 0 fail · evidence for dora.art9, iso27001:A.5.18, iso27001:A.6.5…
- Each system's access is reviewed and signed off each quarter0 pass · 0 fail · evidence for dora.art9, gdpr.art32, iso27001:A.5.18…
- Admin access is approved and uses two-step sign-in2 pass · 0 fail · evidence for dora.art9, gdpr.art32, iso27001:A.5.15…
- Automations finish, or a person takes over0 pass · 0 fail · evidence for iso27001:A.8.16
The ledger
- fw.build.systems-monitored · pass · verifieda1c9d7b9badaf56f2e470685…
- fw.build.checks-evidenced · pass · verified1f0f8b51f26bd23f980d9f20…
- fw.build.access-review · pass · simulatedb39d4b74b19d1fb31f21bd6e…
- fw.build.payment-reconciled · pass · simulatede115e7cf8436174487c1dbf5…
- fw.build.invoice-details · pass · simulated504ec8321c560816eae439a4…
- fw.build.no-card-numbers · pass · simulated1603f4b957443be6ea799c9b…
What the pack carries
Connected systems
Each system, sandbox or live, connected or failing, with its last error.
Activity
The week's events from the connected systems, the failures, and the workflow runs.
Controls
Each control's passes and failures, those still failing, and the laws it gives evidence for.
Issues and tasks
Open issues by severity, and the tasks open, done and past due.
The assistants
Each assistant's runs and issues, and how many of its decided issues were accepted.
The ledger
The period's checks, each kept with a SHA-256 of exactly what was checked, and the latest of them.
Check a fingerprint yourself
One row of the ledger: a CRM gave a contractor admin access with no named approver and two-step sign-in off, and the check failed. This is the text the ledger hashed and the fingerprint it kept. Your browser hashes the text as you edit it: change one character and the fingerprint changes.
The fingerprint the ledger kept
a970ade19c0e4718077dafbd2c0de126970ec4d5f88c43dd72d64313da8656f3
This text, hashed in your browser
…
Hashing…
Try this in a copy of your own, for two hours, with nothing to sign up for.
Open your own copyHow the record is kept
Added to, never rewritten
The app's own login can add a result to the record and cannot change or delete one.
Chained, tamper-evident
Each result is a link that holds the hash of the one before it. A result changed, removed or slipped in breaks the chain from that link on, even when it is done with the owner's own login.
Checked outside the database
The chain the database writes checks out with code that runs outside it: no part of the check needs the database it came from.
Each result once
An event is recorded once, and each check on it carries a fingerprint that recomputes.
Simulated apart from verified
Results from the sandbox are labelled simulated and counted apart from verified ones.
Erasure keeps the proof
After a person is erased, every check's fingerprint still verifies.
Start here
See it on a business of your own.
Open your own copy in a few seconds and use it for two hours, with nothing to sign up for. When you want it on your own systems, we start with an audit.