Canonical archive — live

Stonewall

Artifacts, patterns, matters, and cast in one searchable manifest. Every number links to the file that produced it.

Open public portal Capabilities Platform elite Innovations book Showcase
2,701 artifacts 557 patterns 151 matters 529 cast v12.5 brain

Read the corpus.

Six surfaces. One archive.

One archive, six ways in. The public pages, the operator console, the engineering writeups, the platform contract — each one points at the same files. Drift on any of them gets caught by the next.

Public graph demo

The pattern graph, the counts, the atlas views — everything's a click into the actual data.

Open graph →

Operator console

The signed-in workspace. Live matters, readers, workflows, billing, command search — the room where the work actually happens.

Open console →

Innovations book

How the thing got built. The control plane, the verification spine, the OCR floor, the May 2026 push that hardened all of it.

Read the book →

Platform elite practices

Five Azure pillars. Each one points at a file in this repo and a CI gate that fails if the file lies.

Open contract →

Engineering showcase

Architecture, stack, topology — what runs underneath, in plain English. Built for an engineer skimming on a phone.

Open showcase →

Engineering digest

The build log. Recent verification runs, documentation drift, what changed and why.

Read digest →
Feature spotlight · automation

The watch that keeps the prose honest about the code.

A schedule trigger runs daily. The routine scans every PR merged since the previous run, flags every document that still references an API surface those merges changed, and opens a single rolling pull request against the docs repository for an editor to review. The flag is the deliverable. The prose fix stays with the editor.

  • One rolling PR
  • Drafts by default
  • Line-number receipts
  • Stdlib only
Open the spotlight → Read the walkthrough

Where the work lives

Three places, one record. The repo holds the canon, the workspace holds the work in progress, and the upstream reservoirs are where new evidence comes in from. None of them are snapshots — all three move with the cases.

Repository

The catalog, the codex, the source artifacts, the static site. A flat-file database you can grep. Version-controlled and inspectable to the byte.

Workspace

Matter registry, archive, message thread, task backlog — relations wired across, morning brief on top.

Evidence reservoirs

Documents, transcripts, exports, screenshots. Pulled in from upstream sources, normalized, then read.

Public portal

Search the corpus, count the deadlines, see how patterns reach across matters. The signed-in console holds the live record.

Open portal →