A Style Fix Must Survive Regeneration
Semantic progress classes and a full-tree CSS check now keep generated pages within the shared style system; unchanged renders verify the extraction of legacy styles.
Read the entryTechnical history
Build log
20 entries · Updated 17 October 2026
How ancientmeasures.com is planned, built, verified, and shipped. The Case Studies cover ancient measurement; this log covers the engineering. Entries reconstructed from the project’s dated planning and release history say so; nothing is invented. The record now covers twenty distinct decisions, newest first.
A Source Gate Must Name Its Source
Specific passage requirements now govern research readiness, so generic catalogue matches cannot release a blocked study or put it next in the queue.
Read the entryAn Analysis Page Must Answer to the Queue
A generated public report now ties every research commission, publication milestone and source holding to the same checked queue as the progress displays.
Read the entryProgress Is a Measurement Too
Three instrument plates now show the article programme page by page: a pyramid of 233 stones, a dial for temples and measuring rods for units.
Read the entryA Homepage Is a Map, Not a Landing Page
The homepage now directs visitors from six converters to a preserved pyramid diagram, a rotating unit dossier, focused studies, and the latest build-log entries.
Read the entryTypography Is a Contract, Not a Decoration
A typography release is complete only when its character scope, fallback metrics, responsive rendering, cache key, and public requests all pass together.
Read the entryThe Blog Is an Evidence Trail, Not a Magazine
A build log earns its place by showing what changed, why it changed, and what was checked; it is not a second home for ancient-history essays.
Read the entryA Test Route Is Not a Test Result
A successful HTTP response can still be a fallback document; route checks must confirm the page’s identity, not merely its status code.
Read the entryWhen a Data File Turns Into a Web Page
A relative asset path in a nested converter can resolve to an HTML fallback; the fix is to correct the depth and verify every sibling tool.
Read the entryCache Keys Are Part of a Release
When an immutable JavaScript asset remains cached after a correct deploy, the HTML reference needs a new version key and the public route needs a later check.
Read the entryA Library Needs Routes, Not Just Cards
The Study Library became a connected information architecture: named collections, stable routes, redirects, and a navigation system that exposes the research surface.
Read the entryOne Rule for Every Card
When card badges needed clearance, the correction was a scoped shared rule across the library, not a series of hand-positioned exceptions.
Read the entryA Redirect Is Part of the Research Record
Renaming a case study or consolidating a page changes labels, not the obligation to preserve its address and the reader’s path to it.
Read the entryThe Journal Becomes the Articles
Topical essays moved to Articles, while the blog address became the technical build log.
Read the entryThe Editor Steps Forward
Version 5 changed no tools and no essays; it changed who visibly answers for them.
Read the entryEight Pyramids, One Menu
The pyramid tool stopped asking users to type dimensions and began offering documented monuments.
Read the entryA Domain of Its Own
The site took its name and domain, then made unit dossiers account for their sources or gaps.
Read the entryThe Converter Suite Day
One converter became five tools and 189 standards with the source register reconciled.
Read the entryForty-Four Pages, Zero Placeholders
Version 1 was built, frozen, and staged; version 2 hardened it before midnight.
Read the entryA Plan Before a Page
The scaffold came first: a brief, palette, port band, and fact-versus-interpretation spine.
Read the entryReturn to the field guide · Open the converter · Audit the sources