Technical notes

Checking the figures

Every figure on the main page is typed into it by hand. This page says where each one comes from and how to reproduce it, so nobody has to take them on trust.

Why they are typed in at all

The ten wikis are private. Neither a visitor's browser nor the build that publishes this site can reach them, so there is no version of the page that computes its own figures. What there is instead is a script that recomputes them from the wikis and compares each one against what the page says.

It only runs on a machine that has the wikis checked out beside this repository, which means it is a pre-flight somebody runs before editing the page, not an automatic check. The dates on the page are the real protection. They tell you these are a snapshot rather than a live claim. The script exists to make moving those dates cheap enough that nobody skips it.

Run it with python3 counts.py for the comparison, or python3 counts.py --check to exit non-zero if anything has drifted.

It was written after a drift, not before one. On 10 September the diagram said 37 pages had been contributed on the day the 38th merged, and four of the five figures in the statistics block had been overtaken. Each measure below is defined exactly, so the next person gets the same answer.

What each figure means

On the page	How it is counted
wikis	The wikis in daily use. The shared template is an eleventh repository and is deliberately left out: a template is not in use.
maintained pages	Every markdown page in every wiki, excluding the daily log files and the catalogue shelves, which are bookkeeping rather than knowledge.
skills	The named routines Claude can be asked to run.
cross-links	Every link from one page to another, counted across all ten. The broken figure is links whose target does not resolve.
jobs that run on their own	Scheduled jobs across the wikis.
pages received	Pages in a shared wiki that carry both a record of who sent them and a record of which wiki they came from. Both marks together are what the sharing step writes; a page written straight into a shared wiki can carry the first on its own, so counting that alone overstates it.

Counted per shared wiki, never per person. Until 21 September the diagram on the main page printed a page count beside each colleague's first name, on the open web, about people who had not agreed to publish it. The figure now says what each shared wiki has received. The script still measures each person's wiki, because that is the only way to reach a total, but nothing it states is attributed to anyone.

The suggestions that reach your board

Each row written to the board names the tool that produced it, so you can go and re-derive it yourself. goals.py is the one that reads goals and the promises made against them; when a row says eight of nine goals have nothing committed, that is where the figure came from and the command that reproduces it.

None of these tools can write to a wiki. They read the pages and print what they find. Everything they produce is a suggestion until a person acts on it.

What it is built out of

Markdown files in a Git repository. Every page is a plain text file with a version history. If every piece of software around it disappeared, the knowledge would still open in any text editor.
Claude, doing the writing and the filing. Replaceable. The memory is the files, and the files outlast whichever model is reading them.
Checks that run on every change. Each rule the system refuses to break is enforced by one of these rather than by a line in a document.