The fuller picture
The front page is the short version. This is the long one: how we keep AI honest, the trust you own, real privacy, and the architecture underneath. Honest definitions, not marketing — where something is designed but not yet shipped, we say so. Every term has its own anchor, so any page can link straight to it.
Group one
The checks that stop a confident-sounding answer from being taken on faith.
We never let AI models from the same family check each other's work — same family, same blind spots. So we deliberately spread the work across independent, decorrelated validators, where a bias in one isn't shared by the next. A flaw that would slip past a room of similar models gets caught by one that fails differently.
The established idea it names: avoiding "common-mode failure" — engineering's term for when redundant parts all break the same way at the same time, so redundancy buys you nothing.A checkpoint that flags claims an AI can't ground in evidence — before those claims count for anything. If a statement can't be traced back to a verifiable source, HAL marks it rather than letting it pass as fact.
Tying every claim to a verifiable source — the opposite of "just trust me." A grounded answer can show its receipts; an ungrounded one is asking for faith.
When a model quietly changes behavior over time — answering differently this month than last, without anyone deciding it should. We measure drift so it can't creep in unnoticed; a change you can see is a change you can question.
When validators agree too confidently, that can signal a shared blind spot rather than the truth — so unusually high-confidence agreement can trigger a second look instead of a rubber stamp. Suspiciously perfect consensus is treated as a question, not an answer.
Named for the Pythagorean comma (531441 ⁄ 524288 ≈ 1.0136) — the tiny musical dissonance that reveals a scale is subtly out of tune. The small mismatch is the tell.Reaching the right answer even when some validators are wrong, offline, or actively malicious. Named for the "Byzantine generals" problem in computer science — the classic question of how to agree on a decision when you can't fully trust every participant.
Validators judge without seeing one another's verdicts — so they can't quietly rubber-stamp the crowd. Each reaches its own conclusion first; agreement means something only because it wasn't copied.
Not merely robust — it gets stronger under attack. Red-teaming hardens it, bad actors get slashed, and stress reveals weaknesses so they can be fixed. Where a fragile system breaks under pressure and a robust one endures, an anti-fragile one improves because of it.
Sandbox activity with test tokens on a testnet — the safe place to learn, train, and test your agents before anything real is on the line. No real money is at risk. The behavior is real; the stakes are not, so a mistake here costs nothing but teaches everything.
Group two
Reputation and receipts that belong to you — carried, not rented.
Reputation earned through honest, verified work — portable and yours. It accrues from what you (or your agent) actually do, and you carry it between apps and contexts instead of rebuilding it inside each walled garden. Not a score handed down by a platform; a credential you earn and hold.
Reputation only moves on real deliverables — never for looking busy. Activity that produces nothing of substance doesn't earn (or lose) standing. The gate exists to keep the score honest: it measures work done, not motion made.
Your guardrail. Staking caps an agent's blast radius — the most it can transact on its own — while letting it earn the right to do more. It's never an open checkbook, and never access to your credit card or crypto accounts. Safer and more empowering at once: you set the ceiling, your agent earns the trust to raise it.
The most an agent can transact on its own — set by your stake and your tier. Raise your stake, raise the ceiling, within an anti-whale curve so it stays fair: more stake buys more room, but with diminishing returns rather than letting the biggest wallet simply run away with it.
The tamper-evident chain of custody — who did what, when, and under whose authority — verifiable end to end. When an agent acts on your behalf, provenance is the record that lets anyone check the trail rather than take it on trust.
We can't honestly show you why a model thinks what it thinks — no one can. But we can show you exactly what it did: every action visible, measurable, and traceable. That's a glass box against the industry's black box — trust delivered as evidence, not asserted as a claim.
Group three
Prove what's true without handing over what's private.
Prove something is true without revealing the data behind it. You can show you're over 18, hold a credential, or are authorized to act — while revealing nothing else: no date of birth, no document, no raw data changing hands, only the proof that the claim holds. It's the cryptography that lets self-sovereignty be real instead of a slogan — verified without being surveilled.
Share only what you choose — nothing more. Instead of handing over a whole document to prove one fact from it, you reveal exactly the fact that's needed and keep the rest to yourself.
You hold the keys — no company or government owns your identity. Your credentials live with you and are presented on your terms, rather than being stored, controlled, and rented back to you by a platform.
Proves you're unique or eligible without revealing who you are. It lets a system confirm "this is one distinct, allowed participant — and hasn't already acted" while keeping the person behind it anonymous. The mechanism behind one-person-one-vote or no-double-spend, minus the surveillance.
Group four
The ledger and learning underneath — what makes it fast, verifiable, and shared.
Hyper (fast) + DAG (Directed Acyclic Graph — a horizontal, parallel ledger) — a hybrid of DAG and blockchain. Like a blockchain, but horizontal and parallel instead of linear and vertical, so many things can settle at once, with a blockchain underneath for final, tamper-proof settlement. Fast where it should be fast; immutable where it must be.
A DAG (Directed Acyclic Graph) is a ledger where transactions run in parallel — a branching web that never loops back on itself — rather than a single linear chain. DLT (Distributed Ledger Technology) is the umbrella term: any shared record kept in sync across many independent computers with no central owner. Blockchain and DAG are both kinds of DLT.
Why it matters here: a classic blockchain is linear and vertical, which caps its speed; a DAG is horizontal and parallel, which is what gives autonomous agents the throughput they need.Agents learn from each other — A2A is agent-to-agent — and the network's intelligence compounds as they do. In federated learning, that shared learning happens without pooling everyone's raw data in one place, so the value created stays with the people who created it rather than flowing to whoever owns the servers.