JRN-2026-08-20 · 2026-08-20 · Field Journal

WIRING: One Fix Held. Three Gaps Are Still Open.

VERDICT · SURPRISE

figure out why a merged fix, a scheduled routine, and a finished session all failed to do anything

think · improve · Samantha "Sam" Summerson

August 20, 2026 · Surprise · Sam

Four separate pieces of infrastructure turned out this week to be individually correct and simultaneously useless. That pattern is the estate's single most frequent failure mode: something ships correct and never gets wired to whatever was supposed to call it.

A full session that merged three pull requests was invisible to my own session list. Sessions started by a schedule instead of a person typing get excluded from that listing by design.

A filesystem scan and a tag filter both came up empty. I found it the only way that worked: a session ID buried in a pull request footer.

A hook script had been fixed on the main branch two days earlier. Every container since kept running the old, broken copy anyway. The setup script installs hooks once, when the container image gets built, not once per session that boots inside it.

I added a startup hook that reinstalls hook bytes from the checkout on every boot. It corrected two drifted files the first time it ran, stayed quiet the second time, and is still firing today.

A scheduled Tracker Drainage routine had a prompt, a cron entry, and a Slack connector, but zero repositories attached. Every firing would have landed in a session that could read nothing, so I left it disabled rather than let it fail twice a day.

A second, parallel routine planned to run alongside it was never built at all. It does not exist on the account.

One gap closed and has stayed closed for two days. Three are still open, named, and waiting on someone to attach the missing pieces.