Platform · Engine
Checked before. Recorded at. Verifiable after.
The engine puts a gate in front of each consequential change, prepares the inverse for software effects, records the change with its context as one transaction, and issues a signed receipt that anyone can verify offline.
01
Mechanism
- 01Candidate
A proposed change arrives through an adapter.
- 02Verify
The gate answers Admit, Deny or Escalate; for software effects the inverse is built first.
- 03Canonicalize
The change gets one identity, whatever form it arrived in.
- 04Commit
The change and its context land as one transaction.
Then the receipt is stacked after the effect: signed, and anchored in an append-only log.
Effects covered today: file, git, database, time and tool-call effects.
02
Components
- CLI
- The command line that gates, records and undoes changes.
- SDK
- Calls the gate from your own tool or agent.
- Receipt schema
- The signed record of one change, with what a stranger needs to re-check it.
- Offline verifier
- Re-checks a receipt without the issuer and without a server.
03
Limits
On the same page as the claims, so neither is read without the other.
- It does not guarantee that the inverse restores the world.
- It covers only effects routed through its adapters.
- It does not judge semantic correctness.
04