THE GUILDS
Where the standards live.
THE SPECIALISTS SIT INSIDE THEM. CLICK A GUILD TO OPEN ITS DOSSIER BELOW.
THE STANDARDS TABLE · WHERE CHARTERS GET WRITTEN
GUILD DOSSIER
He runs a working firm of AI specialists for Listening Post. Every request goes to a specialist with a written charter. Someone who didn't do the work checks it. Anything irreversible waits for a human yes. This page is live.
1.33BReal token usagecounted tokensA guild does not do the work. It defines what excellence means in its domain: it owns the craft standards, governs the specialist charters inside it, maintains benchmarks, and reviews evidence. The map shows the chartered guilds and the fallback coverage honestly.
THE STANDARDS TABLE · WHERE CHARTERS GET WRITTEN
THE HANDOFF · CHARTERED WORK ONLY
A brief lands in natural language with context attached.
Chip classifies it and assigns a chartered specialist with a deadline.
A fast check before anyone types a word: is this clear, and should we do it at all?
The specialist applies the guild's standards, states assumptions, and saves receipts as they go.
Truth: claims supported, numbers check. Reasoning: logic holds. Craft: presentation quality. Outcome: it actually answers the brief.
A different agent, on a fresh context, with no stake in the result. It can send work back.
Anything that spends money or leaves the building waits for a human yes. Everything gets logged either way.
Request, standards applied, output, review, and measurement, written to the record.
THE ARCHIVE · EXPECTED VS OBSERVED, MEASURED
Every piece of work links request, standards, output, review, and measurement. This page's own artifacts are records, not illustrations.
Every specialist action lands in an append-only log with a timestamp. The register above is a live window into the same habit.
The system checks its own claims: domain verification, DNS checks, behavior probes. Certification is earned by the machine, not asserted by the page.
The system runs on Hermes today. The kernel is portable, and the proof is written down, so no vendor gets to hold it hostage.
Chip measures provider usage, reliability, and cost inside the authenticated operating environment.
The whole system is a repo: charters, standards, gates, operations. Clone it, read it, run it. Or write to us and we'll build one with you.
$ git clone https://github.com/listeningpost-dsteele/lposv3.git
CLICK TO COPY
We built LPOS for ourselves because we wanted to trust the work. This page was designed to pass the same gates it describes: intent, truth, reasoning, craft, outcome.