Liminal the judgment layer for AI-assisted work · local-first · refusal as output
A read, running

Bounded agents read it. They disagree. You decide.

Watch one read run: four bounded agents deliberate, one refuses out-of-lane, you decide. The decision seals into an inspectable, local record. That loop is the whole product.

See the judgment loop
DILIGENCE Auditor JUDGMENT Skeptic SYNTHESIS Weaver OUTREACH Envoy
sealed · packet in the vault
sealed
the record stays inspectable
Who it's forTeams accountable for AI-assisted decisions: founders first, then owners of frontier-model spend.
The problemAgents produce answers. Nobody governs what was trusted, corrected, or refused. Nobody can prove it later.
The mechanicBounded agents read; they disagree or refuse; the accountable human decides; the record seals and stays inspectable.
What's real herePrototype choreography over deterministic fixtures. Receipts labeled where earned. Vault writes are real, device-local. Roadmap is marked.
Start here · the judgment loop prototype · fixture
The slate & tray · the core mechanic

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.

The commercial wedge prototype · deterministic fixture · receipts labeled
Govern · Opus 4.8 spend against company goals

A 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.

Play · three sequences, one system wraps the surfaces below · claims labeled per beat
Sequences · the catalog, played

The 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 prototype13 surfaces
Margin-read · the founder's handThe re-entry loop, narrated in the founder's own hand over the live UI.explainer Agency · the subject is a parameterThe proof it's infrastructure: one loop, pointed at spend, custody, OSINT, a contradiction.substrate Today · what came back overnightThe daemon re-reads held compositions; you say how it landed. The loop, made a place.re-entry Govern · correction is the interactionThe loop turned on the agent fleet itself. Where you correct is first-party data.govern Operating plane · the whole loop, one screenSix togglable scenes end to end: at rest, brain-dump, loop running, judgment, closure, vault.sketch OSINT Custody · concept cutINGEST→READ→GUARD→REVIEW→VAULT, the custody flow as design concept. The guard refuses the intent claim.archived concept Liminal Custody · defense surfaceSame architecture under maximum constraint. NatSec, top 16 of 102 finalists (200 teams at start), in 48 hours.natsec Calibration · the moat, made visible12 weeks × 4 registers. Corrections compound into a record that reads as pattern.record The thread · diffuse contextGmail + Calendar as diffuse context: open loops surfaced in five minutes, each with a receipt.design intent Team Drift · coherence as a pipeGovernance as a pipe, not a flag. The correction-stream substrate, turned on the team.telemetry Molehunt · analyst consoleHigh-assurance counterintelligence: statutory gate, append-only chain-of-custody.counterintel Slate & Tray · composition demoDrag any window in. The agents read what's there. No pipes, no integrations.composition Vault + Agents · four-register readBounded agents across four registers. Each reads one surface, refuses the rest.vault