Posts on DVLAW.
21 posts tagged "DVLAW".
post_today opens two connections. The test fixture only controlled one.
Three tests in test_post.py broke when auto_mode was turned back on in production. No code had regressed. post_today also opens its own connection to read the auto_mode flag, independent of the connection the fixture supplies, and the test hadn't controlled it.
I fixed four pipeline bugs in three days. The success rate was 20%.
On the morning of 2026-06-13, three articles were blocked or in trouble before 09:00. Working backwards from a 20% autonomous success rate across five slots revealed something individual fix sessions don't surface: every fix had left the adjacent failure mode intact.
The substitute pool stole from future slots because slots didn't exist as rows
Phase B's autonomous publishing pipeline sat at twenty percent success. The substitute pool was recursing through future-scheduled rows to breach — and nothing in the data model could stop it because slots had no identity. Making the slot a first-class entity with explicit state transitions turned six log events into six queryable rows.
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.
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.




