01
Recover the project.
Read source-linked state instead of reconstructing a week of tabs. Every status names where it came from, how old it is, and what it cannot establish.
An evidence-backed command center for delegated technical work
Come back knowing what changed.
Maat puts every project in one source-linked view, sends one finite job to the right model or machine, and counts work done only when a named gate returns evidence you can check.
Open private Maat
Maat: pronounced “maht”
Public surfaceLanding page live
Product stagePrivate first user
ObserverAuthenticated private build live
Action planeLOCAL ONE-USE OPERATOR ONLY
01See the whole field.
The first job is recovery. Open one screen after a day away and answer what advanced, what is blocked, what died, and what deserves attention. The specimen below uses real registered project names and checked-in status labels. It is not a live observer.
Registered12
Status coverage12/12
Act ceiling2
Human only1
Died status0
Live deltaUnknown
COVERAGE · 12 of 12 displayed rows have a checked-in status. No transition ledger is attached to this public specimen, so “what moved since yesterday?” remains UNKNOWN. Zero registered rows carry a dead status; that does not prove zero unobserved deaths.
Can you recover the field in 60 seconds?Three questions, answered by clicking rows above. Scored in your browser. This test can fail.
00:60
02Turn intent into bounded work.
Maat is being built around four capacities. The interface stays simple because the difficult machinery runs on your servers, under explicit authority, with a fixed end condition.
02
Issue one finite job.
Tell Maat the outcome you want. It drafts a contract with one scope, one writer, one isolated worktree, one deadline, and an exit.
03
Send it to the right minds.
Route bulk work to your own machines. Convene independent frontier models when judgment matters. Keep cost in the server layer, not trapped inside an editor tab.
04
Accept evidence.
A worker cannot mark itself done. The named gate runs, known-wrong decoys must fail, and the result returns with a receipt that states exactly what passed.
03Permission expires with the job.
Persistent autonomous writers create hidden authority. Maat gives a worker the smallest temporary power needed for one declared outcome, then takes it away.
01 / INTENTChat drafts
02 / WORKWorker proposes
03 / JUDGMENTPanel advises
04 / CLOSUREGate admits
Humans can override policy only when the override is explicit and attached to the exact work item. Conversation alone authorizes nothing. A panel vote proves nothing. The gate profile on the receipt is the claim.
04Many minds. No groupthink shortcut.
A mixture of agents is useful when the agents can disagree. Each director answers alone, later rounds attack the strongest rival, and a fresh judge picks what survives. What follows is not a diagram. It is the actual panel run that designed this page.
Director 1 · Fable 5 · xhigh
Opened on recovery.
Argued the page must start from the operator’s real problem: many projects, one screen, what changed since yesterday.
Caught in round one: invented status labels. Only checked-in labels survived.
Director 2 · Grok 4.5 · high
Demanded printed coverage.
An event log cannot distinguish “nothing happened” from “nothing was watched.” The coverage line under the specimen above exists because this argument won.
Caught in round one: a replayed-gate claim it could not support.
Director 3 · GPT-5.6 Sol · xhigh
Wanted the seal center stage.
Pushed the register and a self-sealing page as the hero. The judge cut that to a rim and kept its rigor: every honesty rule here is checkable against one data structure.
Held to its own decidability standard: four of its components killed.
Fresh context · Fable 5
The judge killed four ideas.
The seal-first hero. The inverted “do not request access” close. An absolute no-mocks rule. A five-verb feature taxonomy. What you are reading survived three written rounds.
Separate authority
Agreement proves nothing.
The panel chose this page’s direction. It could not make the page true. The deploy, the tests, and the digest below did that.
RECORD · maat/panels/maat_homepage_first_principles_20260710_172419.json · SHA-256 663946b2c6318c01f2930e3e42f3a5cdff87a15659a4786cb577502d71f9d4af · 3 written rounds · 35.9 min
05The seal says what passed.
A Maat mark never means “trust the AI.” It names the artifact, the gate profile, the scope, and the evidence. Change the profile and the claim changes with it.
MAAT · CLAIMS-SCOPE-v1SELF-PUBLISHED · ATTESTED
This page’s claim receipt
A browser demonstration over a small canonical claims payload. It does not sign the HTML and it does not replay a product gate.
Claims payload digestCALCULATING
SignatureSIGNATURE NOT PRESENT
Gate replayGATE REPLAY NOT RUN
AdmissionADMISSION NOT ESTABLISHED
SHA-256 · calculating in browser…
Your browser computed the digest above just now. Change anything in the payload and the mark refuses.
06What exists. What does not. What comes next.
The product has a working research core and a public landing. The conversational command center is the next surface, and it stays labeled as vision until its action boundary passes hostile tests.
Exists now
- A registered project portfolio with authority ceilings
- Finite one-shot research contracts
- Isolated worktrees, fixed gates, and typed receipts
- Independent multi-model panels with fresh-context judgment
- A public static landing at usemaat.dev
Authenticated observer at /app
- A signed read-only portfolio observer
- Twenty-seven passing observer tests
- Twelve operator and hostile-hub tests
- No browser action plane
- No claim that signatures prove writer exclusivity
Being built
- One live view across every project
- Conversation that compiles intent into bounded work
- Dispatch to Elmo and selected model panels
- Transition history that distinguishes silence from no change
- Receipts that travel with every accepted result
Maat is beginning with one demanding operator
Run more work. Lose less truth.
If you direct many technical projects and need agents to work without letting fluent output become fake progress, ask to see the private build.
Open private Maat