The tactician needs it. Stonewall ships it.
Stonewall is a litigation knowledge system: a source-grounded corpus, a live operational data plane, and a retrieval-first chronicler — wired across the public surface, the operator cockpit, and a Telegram bot, on a main branch that is never red.
Four things worth the look
Not a toolchain inventory — the systems that make the record hold. Pick one.
A live Postgres data planeNeon Postgres
A Neon Postgres data plane mirrors the entire corpus and carries Shelby's durable memory. The flat-file manifest stays the source of truth; Postgres is the queryable projection beside it — artifacts, patterns, and source markdowns, indexed for millisecond reads.
- Durable per-operator memory + thread history
- Corpus projection tables (artifacts · patterns · sources)
- Read-only Neon role behind row-level security
- Idempotent, schema-versioned migrator
Every claim anchored.
Shelby does not summarize from memory — it walks the record artifact to artifact, and every factual claim it makes is pinned to a manifest ID, a repo source path, and a line range, rendered as a chip like A0071· L23. Against the live corpus those chips resolve to real artifacts — 2,568 of them — and open the source at the cited line.
Want the whole performance? The full demo exchange — a 1992 courtroom classic cross-examined citation by citation — lives on the landing page.
What the record is made of
Top artifact types across 2,568 indexed items — every one source-grounded and pattern-tagged.