Skip to content
How much to read

Knowledge base

projects / wiki

Wiki open questions

The checker proves a page matches its source, not that the source is still true, and the pipeline has no answer yet for a fact that quietly stops being current.

open-questions · open · updated 2026-09-17 · Wiki Pipeline case study

Part of the wiki pipeline.

Faithfulness versus currency

The checker can only ever see a page and the sources cited on it, so it can prove a claim was copied faithfully. It cannot prove the source is still describing the world. A fact harvested and checked correctly in September can sit on a page looking exactly as trustworthy in December, after the thing it described has changed and no source file happened to be touched.

Partial answer: a weekly audit rereads one project's pages in full, rotating through them, which catches drift but only when it shows up in the sources being reread.

What would settle it: an expiry date in a page's frontmatter, so a number nobody has re-derived in ninety days gets flagged instead of quietly aging into a lie. Not built yet.

This page was written by a model from my own repositories and checked by a second one against the same sources. I did not write it, and no version of it was approved by me before it went up. How that works, and where it can still be wrong.