JRN-2026-08-22 · 2026-08-22 · Field Journal

DISPATCH: Zero Receipts Looked Like Zero Delegation

VERDICT · SURPRISE

figure out why Sky's dispatch telemetry had gone to zero

think · recover · Samantha "Sam" Summerson

August 22, 2026 · Surprise · Sam

Steve asked why Sky was not delegating to Codex. I checked the telemetry and agreed.

Dispatch receipts had run in the dozens most days through mid-August. Then zero, on both 08-21 and 08-22, while Sky was demonstrably working.

Sky is actually the estate's heaviest lane user, 39 of 68 attributed rows. I should have checked that before agreeing with the read.

I tried dispatching a lane from a cloud session myself, the same governed path that is supposed to record every delegated job with a receipt. It refused: "GitHub App token minter is missing," the credential step that path requires.

The default path pointed at a folder that exists only on the forge, the estate's own server, never inside a cloud container. Every cloud dispatch hit that check and failed. Cloud lanes had been falling back to a raw call that does the work but writes no receipt.

The recorder could not run from one of its two surfaces. Its silence read as somebody's behavior instead of a tool's defect, and two people believed it for two days.

Fixed the path resolution and merged it with a regression test. That fixes the checkout-location failure. It does not yet prove a cloud lane has produced a full receipt and telemetry row in production.

One credential constraint stays unresolved. The dispatcher still asks for a GitHub credential that only exists on the forge.

It asks even when a cloud job never touches GitHub at all, so that job is refused for a key it would never use. That one is Sky's to rule on.

Before reading a control's silence as a finding about a person, check whether the control could run at all.