Trust & Governance

These hold today. Any change to them is dated here.

AEIIEA keeps records of what AI systems do and lets anyone check them later. This page says what holds today about those records, who holds the keys, how we handle being wrong, and how to check any of it with no special access. Nothing here is a count.

A record stays checkable as long as we hold it: its seal is published and can be checked with any ordinary SHA-256 tool, with no code of ours. The full check of its evidence bundle uses our verifier, which today comes from this site, and from the repository once that is public (How to check, below). We never edit a sealed record. If one has to be withdrawn, for example to protect someone's privacy, we stop serving it and say so in a dated note; its line in the index stays.

How a record is made never changes silently. A change to the instruments fails our own tests until it is written down, and an old record is still checked against the instrument it was made with. The checks we run on it are today's.

Every score and ranking we show names who made it and how, and is compared only with the same grader's. We never add different graders' scores into one number, and AEIIEA signs no ordering of models or of people.

Corrections, and any change to these promises, are disclosed in a dated public record, not made quietly. If the project stops, we say so in public and link to whatever carries it on.

Today the Explorer is read-only: nothing you send changes the archive. Since 2026-10-10 the identity it runs under cannot write to the archive either. It has no accounts, no login, no cookies, no analytics and no third-party scripts. Your theme and font choices, and whether a panel is folded, are kept on your own device and nowhere else. If any of that changes, this page says so first, with the date.

When the Judging Room opens, a person's judgment will be sealed on their own device first, and nothing about it will go public without their say.

AEIIEA is operated by Discriminology. Today the repository, the storage, the domains and the keys are held by one person. We say that plainly rather than hide it, and the remedy is written down: the system is documented so a competent engineer could pick it up, and the list of what a successor would need is kept in the repository.

Today, that we never edit a sealed record is a rule we keep: the storage does not yet enforce it. The lock that will is written down and not yet applied.

Decisions that are not yet settled live in a registry with a status and the condition that would settle them. Settled decisions, instrument changes and known defects are written down with the date and the commit. A change to anything that touches real people goes through a named human reviewer first.

Mistakes are entered in the disclosures record: what was claimed, what was true, how many records or readers it touched, and the fix. The record is appended, never rewritten. Security concerns go to the address below.

• Download a record's evidence bundle from its card on the Explorer (the EVIDENCE button) or from the Readout, and check it at /verify. The verification runs in your browser; the page does not upload your evidence bundle, and once the page and its rules history have loaded you can check offline. AEIIEA supplies the browser verifier and its rules history, so this check does not require trusting the live archive's verdict, but it still requires trusting the code served by this website; for verification with nothing of ours, obtain the command-line verifier from a deploy commit of the repository and run it without this site, as VERIFY.md inside every bundle says. The rules history a release carries says which instrument each version of the code ran, and the verifier uses it to resolve which rules a record was made under. A successful check establishes what the evidence bundle's files support, not who published the record, when it was made, or whether what it says is true.
• Open any record on the Explorer and it recomputes the seal in your browser. That shows the bytes you received are the bytes that were sealed. The record and its expected seal come from the same server, so it does not yet show the index itself; checking without trusting us at all becomes possible once each day's index hash is published somewhere we do not control. That is planned, not done. Until then, an independent reader with its own access re-hashes the whole archive against the index and records the result in the repository.
• The machine specification describes the system as it is right now, including what is not built. The same document is served as JSON.
• The health page shows the archive's live state.
• The System names the seven responsibilities, what each establishes and does not, what runs today and what is only named, and who can see whom inside the harness.
• The disclosures record and the registry are in the repository, which will be public.

AEIIEA is a project of Discriminology. Write to the address on the front door.

• 2026-10-28. The second promise said old records keep checking under the rules they were made with. That holds for the instrument a record was made with, which the verifier still works out for each record from the version of the code it names. It did not hold for the checks themselves: an evidence bundle made under an earlier version of the checks is checked under today's. It now says so.
• 2026-10-23. The first promise said the way to check a record needs nothing from this site. That holds for its seal, which any ordinary SHA-256 tool can check with no code of ours; the full check of its evidence bundle uses our verifier, which today comes from this site, and from the repository once that is public. It now says so.
• 2026-10-22, later the same day. "Who holds what" no longer describes the cloud account the archive is kept in, or who else can write to it. It says only what matters to a reader: that we never edit a sealed record is a rule we keep, and the storage does not yet enforce it.
• 2026-10-22. Rewritten from the owner's review of every promise on it. What changed from the page of 2026-10-14:
• it now says what holds today, and that any change is dated here;
• "We publish no rankings, scores or badges" became the rule that every score and ranking names who made it and is compared only with the same grader's;
• "Sealed records are never edited or deleted" became "We never edit a sealed record", with how a withdrawal would be said, and the storage lock's state;
• "What we never do" became what the Explorer does today;
• the Judging Room's way of working is said as a plan, and no longer promises that nothing is sent to an AI company;
• corrections now include any change to these promises.