Build LogDVLAW
#56
2026-06-306 min read

Correct answers, wrong questions: four DVLAW scope errors in 72 hours

Between 2026-06-10 and 2026-06-13, four DVLAW bugs caused cascading slot failures, auto-published style violations, and a near-duplicate article. None threw an exception. All of them were answering the wrong question correctly.

Read post
Build LogPrivacy
#57
2026-06-306 min read

The identifiers I didn't know I'd published

Five fixes across /learning, /now, a published article, the privacy policy page, and a global pre-commit hook — all tracing back to the same root cause. Not tracking, not data harvesting. Just private names in places I'd stopped looking.

Read post
Build LogPrivacy
#58
2026-06-296 min read

The privacy policy was correct. The article body wasn't.

A production audit found the macOS username in a published plist example and private project names on two public pages. Neither would have been caught by a policy document. The fix was a pre-commit hook and an aggregation change — pipeline enforcement that runs whether the author remembers or not.

Read post
Build LogDVLAW
#59
2026-06-285 min read

Five Phase B fixes in 48 hours. They were all patching the same missing type.

Twenty percent autonomous success across five scheduled slots. The same breach shape surfacing twice from different audit trails. Five fixes shipped in 48 hours — and when the sixth investigation opened, the pattern became unmistakable: the slot had never been an entity.

Read post
Build LogEditorial Pipeline
#60
2026-06-265 min read

The sabotage tests passed. The live cycle still found the bug.

Phase X.8 shipped with two hermetic sabotage cycles green. The first live run produced no article — not because the pipeline crashed, but because calculator_scores in ground.py was wrong in a way the fixtures had never exercised. Hermetic tests prove the logic path. Live harnesses prove the integration.

Read post