A demo is only useful if you know exactly what you're looking at. Here's what's genuinely live, what's intentionally not yet, and one gap we're not hiding.
The “Trusted live session” panel is a real, signed session against Claude Opus 5 — not a scripted transcript. It's bounded (15 minutes, 20 questions, 500 characters per turn) and it fails closed: an invalid or missing session token gets a hard lock, not a fallback answer.
An unedited, single-take screen recording of the real local una console — the same governed operator shell shown in the architecture notes — running its actual status check, a real deny-by-default refusal, and a real governed proposal draft.
You're not being handed a query console against the live UNA backend tonight, on purpose. The real MCP server doesn't yet scope what a given reviewer can see — a plain, ordinary search could surface unrelated ledger entries that aren't yours to see. That's a known, already-diagnosed gap with a fix already drafted, gated on an independent security review before it ships. We'd rather tell you it's not ready than hand you something that leaks.
Run una status on the real console and it reports on four subsystems. Three — Memory, Proof, and Orchestration — now run genuine, independent checks against the real subsystems behind them. The fourth, Language, reports NOT WIRED: the validator exists, but its data doesn't yet. Rather than fake a pass, it says exactly that. That's the standard the whole system is held to, including with itself.