Writing & build logs.
Essays on software development, web builds, and AI tooling. Plus build notes from what I'm actually working on right now.
The navigation spec pre-ranked prerequisite chips over search. Six phases later, that held.
The conventions.md backlog called prerequisite chips at the chapter head the single highest-value navigability fix before any code shipped. Pagefind search and an IntersectionObserver right-rail TOC both landed in the same programme. The ranking held. This is why.
Prerequisite chips, scroll-spy TOC, and Pagefind: the trio that closed the learning hub nav spec
Seven phases of navigation work landed on the learning hub over two days. Phases P0 through P4 were infrastructure. P5 and P6 changed what the property felt like to use — and both were in the spec from day one.
The cron ran clean and drafted nothing: eight pillars in five days named the extraction bottleneck
Five days into a 14-day operator-publish sprint, the cron fired on-time every day and produced two useful drafts — one of which recycled yesterday's ground. Improving on the quality-gate diagnosis from the inheritance tax piece, this sprint isolated an earlier failure: claim extraction stalls before the drafter gets a turn.
The highest-leverage navigation fix was a conditional on a frontmatter field
conventions.md ranked the N1 prerequisite chip as the single highest-value navigability fix before any phase of the learning-hub navigation plan shipped. After a scroll-spy TOC, hub track sections, and site-wide Pagefind search, the ranking holds. Reader-orientation at the chapter entry-point outperforms retrieval mechanics for an audience that doesn't know what it doesn't know.
A static site has no server to search. So I indexed the output instead.
There is no query endpoint on a statically-exported site, no database, nothing to ask at request time. Full-text search still works, because you index the HTML the build already produced.