A read, running
Bounded agents read it. They disagree. You decide.
Four bounded agents deliberate. One refuses out of lane. Your call seals into a local, inspectable record.
See the judgment loop →Agents produce answers. Nobody governs what was trusted, corrected, or refused.
- For
- Teams accountable for AI-assisted decisions: founders first, then owners of frontier-model spend.
- What's real here
- Prototype choreography over deterministic fixtures. Receipts labeled where earned. Vault writes are real, device-local. Roadmap is marked.
- Check it yourself
- In Judgment, judge one AI result, download its proof bundle, and run the bundled verifier with Node, no Liminal app. The signature uses a demonstration key made in your browser: it shows the record is unchanged since signing, not who signed it.
Start here
The slate & tray: the core mechanic
prototype · fixture
Drag a Slack thread, a doc, a transcript into the tray. Bounded agents read it, disagree, and stage one next move. You correct the read; the vault keeps the record.
Govern: Opus 4.8 spend against company goals prototype · deterministic fixture · receipts labeledA recorded governance run: four registers read the fleet's spend, one refuses out-of-lane, the operator corrects a finding and ratifies policy; the result seals to an append-only decision log.
Sequences: the catalog, played wraps the surfaces below · claims labeled per beatThe cuts compressed into three played runs: one decision crosses the loop, the loop turns on the agent fleet, and the record proves it travels. Same loop, every subject; arrow keys advance.
Explore the prototype
14 surfaces
Margin-read · the founder's handThe re-entry loop, narrated in the founder's own hand over the running UI.
Agency · the subject is a parameterThe proof it's infrastructure: one loop, pointed at spend, custody, OSINT, a contradiction.
Today · what came back overnightThe daemon re-reads held compositions; you say how it landed. The loop, made a place.
Govern · correction is the interactionThe loop turned on the agent fleet itself. Where you correct is first-party data.
Judgment · accept, correct, reject, deferOne AI result judged as one record: the agent's words and yours kept apart, then back on Today.
Operating plane · the desktop, as builtReal captures of the shipped shell at ce2b62a1: eight states of one decision, every surface it ships today.
OSINT Custody · concept cutINGEST→READ→GUARD→REVIEW→VAULT, the custody flow as design concept. The guard refuses the intent claim.
Liminal Custody · defense surfaceSame architecture under maximum constraint. NatSec, top 16 of 102 projects in the judges’ scoring, in 48 hours.
Calibration · the moat, made visible12 weeks × 4 registers. Corrections compound into a record that reads as pattern.
The thread · diffuse contextGmail + Calendar as diffuse context: open loops surfaced in five minutes, each with a receipt.
Team Drift · coherence as a pipeGovernance as a pipe, not a flag. The correction-stream substrate, turned on the team.
Molehunt · analyst consoleHigh-assurance counterintelligence: statutory gate, append-only chain-of-custody.
Slate & Tray · composition demoDrag any window in. The agents read what's there. No pipes, no integrations.
Vault + Agents · four-register readBounded agents across four registers. Each reads one surface, refuses the rest.