A boundary that improves both sections
The site has two editorial jobs. Articles examine ancient measures, monuments, source problems, and interpretations. The Build Log records decisions about the website: its structure, data handling, testing, releases, and standards. Combining them made neither section clearer. Separating them gives a reader one dependable place for research writing and another for the work behind it.
What makes an entry worth keeping
Each entry should leave a trace a reader can inspect: a dated decision, a bounded change, the evidence that prompted it, and the verification that followed. The useful unit is not an announcement. It is a small decision record. That is why the early entries are reconstructed from the project plan and release history rather than invented as diary prose.
Depth without padding
Doubling a log does not mean manufacturing activity. It means recovering distinct decisions that were already recorded but compressed into release notes: route migrations, data-path repairs, cache behaviour, navigation changes, and evidence controls. Gaps remain gaps. A weekly cadence begins from the current operating period; it is not permission to backfill fiction.
The operating rule
Future posts will state the date, scope, reason, and check. They will link readers back to the relevant public surface, especially the editorial standards, source register, and affected tool or library page. That keeps this log useful to a reader and accountable to the project.