The build log went quiet for a week because the build itself became scheduled. Working sessions now run on a timer rather than on enthusiasm: each one re-verifies the previous session’s page against the printed sources before it may touch a new one, enriches the next page in the cluster, tags a page for the connection graph, and deploys. 10 July was Ask Me Why; 16 July was Misery. The rhythm is weekly now, and the plan file, not any session’s memory, carries the state between beats.
Corrections are the content
Ask Me Why is routinely described as an eighteen-take recording; the session documentation supports six. The console on these early-1963 dates was the REDD.37, not the REDD.51 that later sessions made famous; an error so common it gets patched almost weekly. Misery’s main recording session moved from the oft-quoted 20 February to the documented 11 February, and a quote long attributed to McCartney was returned to Lennon. None of this is glamorous. All of it is the difference between a reference site and an echo of other websites.
The gate at the end of the pipe
Portfolio news this site earned the hard way: after a sibling site’s homepage was clipped by the same silent-truncation hazard and pushed live on 11 July, the shared deploy script gained a pre-push integrity gate. It refuses to push if any tracked text file contains NUL bytes or any HTML page opens without closing. Alongside it, a verified-write helper (staged write, byte and checksum comparison on disk, restore on failure) became the canonical way sessions write to this project, and a snapshot tool bundles the plan and standards into restorable history at session start and end. The checks that lied in June are now surrounded on all sides.
Scoreboard, as of this post: 54 of 214 song pages have been through the full dual-source enrichment under the locked v2 structure, and the tag graph behind the analysis page spans 18 songs. One page re-verified, one enriched, one tagged, one push; per week, on schedule.