Build log

Progress Is a Measurement Too

A progress chart on a research site should count what it can prove: one mark for each page, drawn from the same queue that governs publication.

Three index pages now show the article programme

The article plan commissions 233 pages: 29 temple and site studies, 191 unit dossiers, six articles, five topics and two case studies. Until this release that count lived only in the project's queue file. Three index pages now show it.

The homepage carries the whole programme as a pyramid of 233 stones. The temples index shows a dial with one ring for each block of sites. The units index lays the programme out as three measuring rods on one scale. Each plate states the date of the queue it was drawn from.

One page, one mark

Every mark on these plates is a page. A stone, a ring segment or a rod graduation turns solid gold when its page is published. The next page in the plan has a dashed outline; queued pages stay open. No plate shows a percentage. Eight of 233 is 3.4 per cent, and a bar filled to 3.4 per cent says less than eight gold stones do.

The states follow the site's element register. Published, next and queued each carry a text label and a line style as well as a colour, so the key still works for a reader who cannot rely on colour.

Each plate answers its own page

The homepage plate shows the whole plan, because the homepage is where a visitor meets the whole site. Stones are laid from the base in plan order, so the lower courses hold the pages the plan reaches first. The apex is the last page the plan will publish.

The temples dial shows only temple and site studies. Seventeen sites have pages now; twelve more will arrive as new pages. Giza, the first block, is complete. The outer ring holds the twelve planned sites, so the dial shows the collection's future size as well as its progress.

The units plate is the least flattering, and it says so: 0 of 191. Every unit already has a dossier with its value, basis and uncertainty. The programme rewrites each one to a fuller standard, starting with the Egyptian royal cubit. The three rods share one scale, so the short temple rod beside the long unit rod shows where most of the remaining work lies.

Drawn from the instrument kit

The plates reuse the instrument card that frames the pyramid profiles on the temple pages: the tick ring, the serif nameplate, the mono data rows and the evidence badge. Leader-line callouts come from the kit's hero infographics. The unit rods borrow the graduated cubit rod from the kit's unit dossier. A block table beside each plate repeats its figures as text and links every rebuilt page.

The plates are inline SVG and HTML with one new stylesheet, progress.20260919.css. They need no chart library and no script, so they render with the page and do not shift the layout while it loads.

The queue is the only source

A build script, build_progress_plates.py, reads the article queue and rewrites a marked section on each of the three pages. It overwrites any hand edit inside those sections, and its check mode fails a release when a plate is out of date. The article plan's closing step now runs it, so a page is counted only after it has passed its own evidence and release checks.

The plates measure publication, not quality. They do not say that a queued page is wrong. They record which pages have been rebuilt to the current standard and which are still waiting.

What was checked

The plates were checked in a browser at desktop width, 360 px and 320 px, with no horizontal overflow. The generator was run twice to confirm that a second run changes nothing. The homepage validator, the typography gates, and the sitemap and structured-data checks passed before the release tree was mirrored and published.