Four steps, one file.
This is EVP-1 as designed. The packet below and the Status section show what the proof of concept verifies today.
01
The control is written down.
A readable plan, signed by a governance authority.
02
The population is committed.
A signed extraction states the rule, the time window and the totals. Every record left out is counted and tied to a stated reason.
03
One fixed runtime executes it.
A published program. The plan is data, not new code for each control.
04
The Evidence Packet is handed over.
The recipient runs a standalone verifier: offline, with no account and no call to Ellipe 3.
- source rows read
- Oct 2 run: 5,078,345
- Oct 16 run: 5,078,345
- anchored (in population)
- Oct 2 run: 4,932,279
- Oct 16 run: 5,078,345
- of which marked malformed
- Oct 2 run: 78
- Oct 16 run: 146,144
- excluded
- Oct 2 run: 0
- Oct 16 run: 0
- rejected at ingest
- Oct 2 run: 146,066
- Oct 16 run: 0
- population vs signed commitment
- Oct 2 run: ✓
- Oct 16 run: ✓
- epochs
- Oct 2 run: 18 / 18
- Oct 16 run: 18 / 18
In the Oct 2 run, 146,066 rows with an unmapped currency were rejected at ingest and reported in an unsigned report. Since Oct 16 those rows are anchored and marked malformed, so every row read is inside the signed population.
What the verifier checks today
- Scope and evidence signatures are valid, and the scope covers the period.
- The population matches its signed commitment, in both root and count.
- Classification counts reconcile within each daily epoch.
Planned
- The rule behind each exclusion, and each remaining ingest rejection, is signed, not only stated.
- The source total is reconciled inside signed evidence.
- Signatures come from a governance authority with validity periods.
- The runtime matches a published, reproducible build.