The Transparency Page, What Lives There and Why

Most sites tell you what they believe. This family of sites tells you why, and shows you the receipt. The transparency page is where those receipts live. This is a slow tour of it, in plain language, so you can read it, use it, and push back on it.

Why the page exists at all

There is a working hypothesis under all of this. UNI is on the attainable path toward General Natural Intelligence, natural not artificial, and we are testing that hypothesis in the open. Do not take the claim on faith. Test the build, inspect the gates, and help us find where it fails. If a public sentence of consequence cannot be tied to a source you can open, it does not belong on the page. That rule holds whether the sentence is about a data-center water bill or about a mathematical claim (Class C).

What an evidence class actually is

Every claim on the transparency page carries a tag. The tag is short on purpose. You do not need a research method to read it, and you do not need our permission to challenge it.

• Class A, empirical in session. Something we observed live in a run: a log line, a measured output, a captured trace. It happened, we watched, and the artifact is on file.
• Class B, code or inspection. The claim is anchored in a file you can open: a function, a schema, a config. If the file changes, the claim is required to change with it.
• Class C, configuration or integration. The claim rides on how two systems are wired: a route, a firewall rule, a signed handoff. Break the wire, break the claim (Class C).
• Class E, expert citation. Someone whose work is in the peer literature says the thing, and we quote them with the citation attached. Their name, our summary in our own voice, no paraphrasing of their prose (Class E).
• Class F, falsifier present. The claim ships with the specific result that would prove it wrong. If that result arrives, we retract, in public, on this page.
• Class U, unverified. We are saying the thing, and we are telling you we have not yet earned the right to say it. This is where honesty about the fog lives.

A well-formed claim usually carries two of these. A code claim without a falsifier is fragile. A citation without a code anchor is decorative. The pairs are how the page keeps itself honest.

How to actually read a row

Every row on the transparency page has the same three questions behind it. What is being claimed. What class of evidence backs it. What would count as proof it is wrong. If any of those three is missing, the row is doing less than it should, and you should tell us. There is a link to reach the author at the bottom of every page in this family.

When you read a row tagged Class E, the honest move is to click through and check the citation says what we say it says. When you read a row tagged Class F, the honest move is to imagine the falsifier and ask whether we would actually publish the retraction if it arrived. If the answer is no, the row is worth nothing.

How to challenge a claim

The transparency page is not the end of the conversation. It is the start. Bring a better source, a broken link, a wrong number, a mislabeled class, or a falsifier we did not think of, and the row changes. That is the deal. This is what the phrase human in the loop actually means on this site: the loop is you, the record, and the author, and no one is allowed to close it silently.

When we correct something, we say so on the page and we keep the history visible. A quiet edit is the same shape as a lie, and we do not want to be in that shape.

What the transparency page is not

It is not a verdict on any person or company. It is not a settled science page. It is not a marketing surface. It is the working notebook where we say what we believe, why we believe it, and what would change our minds. Anything on it that reads like a boast is a bug, and we would like the report.

Keep reading

Two callouts, one invitation.

• Read the transparency page itself, with the classes now in your hand.
• Receipts, not vibes, on why the whole family is built this way in the first place.
• The workshop is where we teach the read-a-claim habit to teams who want their own transparency page, in their own voice.