Nine things that run

The instruments

Every one runs in your own browser, against the same engine that would produce a county’s proofs. Nothing is sent to a server; there is no server.

Instrument · Module 1

Map your own custody chain

Enumerate every transfer in your jurisdiction and mark which ones are documented. Most people discover two or three they had never counted.

Instrument · Module 3

Hashing, and the chain built out of it

Change one character and watch half the digest move. Then edit a record inside a chain and watch the break propagate.

Instrument · Module 4

An append-only log, with its refusals showing

There is a delete button. It refuses, and it says why. Reading the refusal is the exercise.

Instrument · Module 5

The tree, and the receipt a voter is handed

A demonstration log is built in this browser and a receipt is issued for one custody event.

Instrument · the point of the whole thing

Check it yourself

Verification runs entirely in your browser, against a root you can replace. Break the receipt on purpose and watch which property fails.

Instrument · Module 3

What that vendor claim actually means

Paste what a vendor wrote. The decoder flags each claim that stands in for a guarantee, and gives you the question that turns it back into one.

Instrument · Module 7

Turn the question bank into a requirements section

Twelve questions, each with requirement language a procurement officer can paste and the evidence that would settle it.

Instrument · Module 6

When must this record still exist?

22 months under federal law, longer under most state schedules, and a privacy obligation that may land inside the window.

Instrument · §6

What this costs

The published rate card, multiplied. Plus the sanity check that the figure which prompted this rebuild fails by roughly forty times.