Check the record — Our Own Machines

Check the record

Our Own Machines makes an unusual promise: do not take the document’s word for anything — check the record. This page is how you do that, without trusting the platform that produced it.

What was sealed

The framework was produced by a deliberation of ten teams. Every step — each team’s opening frame, the turns of argument, the decision points and their outcomes, the cross-check where one team blocked another and the block was resolved, the return-and-re-ratification, and the final tallies — was written into an append-only record and cryptographically sealed at the moment it was made, using an Ed25519 signature over a canonical hash of the content.

The sealed record bundles are published here, as plain JSON:

The sealed record bundles »

Each bundle carries its own deliberation content, its chain of signed receipts, and the public key those signatures were made with.

How to check them yourself

You need only Node.js and one small script. The script is self-contained — it imports nothing from this site, makes no network call, and does not trust us. It re-computes the content hash and verifies each signature against the public key inside the bundle.

Download the verifier: verify-record.js » (about 5 KB, plain readable JavaScript — read it first if you like).
Download any bundle from the record set above.

Run it:

node verify-record.js the-record-you-downloaded.json

Read the output. For each receipt it prints signature VALID or INVALID, then checks that the published deliberation content still hashes to the value inside the signed receipt, and finishes with:
```
✅ VERIFIED — signatures valid and content unaltered, checked without the platform.
```

If a single character of the content had been changed after sealing, the content-hash check would fail. If a signature had been forged, it would not verify against the published key. Neither can be faked without the private signing key, which never leaves the platform.

What this proves — and what it does not

It proves that the positions in the document are the positions the deliberation actually produced, unaltered, and that they were sealed by the key published in the bundle. That is the whole point of the exercise: policy whose reasoning you can verify rather than merely trust.

It does not prove that the deliberation was wise, or that its members were real — they were not. The members are fictional composites, authored by an AI from real sources, and the document says so throughout. What is real is the process: the arguments, the votes, the sealed records, and the evidence behind every claim. This page lets you confirm that the record you are reading is the record that was made.

The evidence behind the claims

Source register » — every factual claim in the framework carries a reference [S-n] to an entry here, with its URL.
The gaps — where New Zealand has no data and the framework declines to invent one — are set out in section 13 of the framework itself, each marked [G-n].

The deliberation ran on a development instance of the platform; the tenant identifier in the bundles reflects that. The verification is cryptographic and holds regardless of the instance name — a signature is a signature.