Documentation / Modules
Reconciliation
One engine comparing what your tools claim against what is verifiably true. Every other module is an instance of it.
The shape
Every instance answers the same question: something claims a state, something else can verify it, and the difference is a finding with an owner and a dollar consequence where one exists.
What it checks
| Instance | Claimed | Verified against |
|---|---|---|
| Patch | The patch tool says deployed | The patch present on the machine, and not superseded |
| Backup | The vendor says the job succeeded | A restore was actually tested |
| Agreement | The contract says 40 seats | The live count |
| Documentation | The document says this is the config | The observed configuration |
| Coverage | The asset is monitored | The monitor is reporting |
| Distributor | You are buying 44 licences | You are selling 40, and the tenant uses 44 |
Every finding has an owner
A finding with no named person is a finding nobody works. Each carries who, the consequence in money or risk, and what would resolve it.
Nothing auto-corrects
Reconciliation reports. It does not adjust an invoice, change an agreement, or reconcile a difference away. Every correction is a person's decision.
Found is not recovered
A divergence identified is found. Money that actually moved is recovered. They are never summed — and estimated is labelled as estimated wherever it appears beside them.
Not running it yet? Start a thirty-day evaluation — read-only, on your own estate, no card.
Thirty days · read-only · no card
Run it beside what you already have, against your real clients. It tells you what your tools are reporting that is not true.