Brief · 2026 · Product, specification and review

Wiki Pipeline

A knowledge base that rewrites itself from my own repos every night, checked by a second model that has no tools and cannot go looking for agreement, plus a desktop app I use to drive the whole thing.

Problem: A hand-written knowledge base behind this site that went stale the day the projects moved on, and that I would not keep up by hand.
User: One user, and that user is me. It is the caveat on every number here.
Decision: Let it publish without me. A process that needs me every day is one I abandon, and an abandoned process still looks like it is working.
Number: 200 pages written, and every one of them checked by a model that did not write it. One user, running hourly since 14 September 2026. Separately, 0 of 204 harvested items got past the redaction scan.
Refused: No remote on the repository and no hosting for the vault, and no attempt to have it write anything a reader sees. I write those.

200 pageseach checked by a model that did not write it
0 of 204harvested items leaked past the redaction scan

Read what it wrotewiki

The full case study is about 10 minutes on how it was decided, measured, and where it can still fool me.