Technology
How the checking
actually works.
This is the one page where the engine gets to be the subject. If you are evaluating whether the central claim holds, this is the page for you.
The property, stated plainly
Records are written into an append-only chain as events happen. Each record is bound to the ones before it, so altering an earlier record changes what every later record should look like. That is what makes tampering visible rather than prevented — we are not claiming nobody can change a record, we are claiming you can tell.
Verification is a walk over that structure, performed by whoever holds the bundle. It re-derives what the chain should look like and compares. If the walk completes, the report says so. If it cannot, the report says that instead.
The property is verifiability, not invincibility.
Why it does not need us
The verifier is software the recipient runs. It takes the exported bundle and produces a verdict without contacting us, without an account, and without our permission. That is deliberate and it is the reason the whole thing is worth anything: a check that the checked party can influence is not a check.
It also means the evidence outlives the relationship. If you stop paying us, your reports stay downloadable. If we stopped existing, an exported bundle you already hold would still verify.
External witnessing
A chain's interior walk proves internal consistency. It does not, by itself, prove that a given root existed at a given time in the eyes of anyone outside your organisation.
Records can be replicated to the data owner, to a third-party transparency log, or to a regulator directly. On hosted plans this is off by default and turning it on is a conversation, not a switch — publishing to a public transparency log means publishing metadata about your fleet to a log anyone can read, and that decision belongs to you rather than to us.
We would rather describe this as a capability you can choose than imply every record you produce is already published somewhere public. It is not.
What we are not claiming
Not unbreakable, not guaranteed, not a certificate, and not a statement that your organisation is compliant. The claim is narrow on purpose: given a bundle, a third party can determine whether the record is intact, without trusting us.
The underlying primitives are not exotic and we are not going to pretend they are. What is unusual is applying them to compliance evidence and then handing the check to the person who most needs it.
Autopliance is built on EdSSA — a cryptographic authentication and evidence technology with an active patent family, developed by the same team. EdSSA is the engine; Autopliance is the product you buy.