—
—
Rotates daily, identical for every viewer.A litigation intelligence system. Source files, sidecars, manifest rows, patterns, and deadlines — one navigable command surface.
Lex est quod notamus. The cabinet remembers what the operator only suspects — consult the corpus in peace, as the masters did.
Read the corpus.
One product story, with clean separation between public pages, operator console, engineering proof, and deployment status.
Aggregate pattern visuals, counts, and routeable Atlas views.
Open graph →The authenticated operator console for live matter workspaces, readers, workflows, billing, and command search.
Open console →Architecture, capabilities, stack, and topology — the platform tour. Public archive mirror linked at the page footer.
Open showcase →Recent verification runs, documentation updates, and system-level build notes.
Read digest →The control plane spans the repository, the workspace, and external evidence reservoirs. These are the living surfaces, not historical snapshots.
Catalog indexes, codex references, source artifacts, and the analytics site. The flat-file database lives here, version-controlled and inspectable.
Matter registry, archive database, communication surface, and task backlog — with cross-database relations and morning operational briefs.
Source documents, transcripts, exports, and screenshots flow from upstream reservoirs into the repository for normalization and analysis.
Aggregate dashboard with corpus search, deadline counts, pattern reach, and public-facing portfolio views. The operator console carries the authenticated operator record.
Open portal →—
Rotates daily, identical for every viewer.Six surfaces ride the same archive spine. The public portal shows the aggregate shape; the operator console holds the live case record.
All public surfaces use neutral matter labels (Crown Matter 1…) — no real names, no docket numbers.
The artifact ledger is the manifest: one row per indexed item, with type, date, case bucket, and analysis flags. It is the contract between intake and everything downstream.
Matters are the horizontal axis: posture, tier, and cross-links to artifacts and patterns. This public host publishes aggregate counts and neutral matter labels; the operator application resolves full titles and linked records.
The case reference layer enforces consistency—so the same matter string means the same portfolio entry everywhere in the repo.
Matters in the portal.
Deadlines are extracted from manifest metadata and codex rules, then surfaced in runway order. The codex is the source of which dates matter and how they relate to posture.
You see horizon and density without private docket numbers on this surface.
Runway in the portal.