# The research panel has missed three consecutive Thursdays, and the owner's only email is structurally unable to say so

**2026-10-29 · daily audit · class: G2 time-to-loud / detector amnesia**

## What was measured

The research panel routine fires `0 13 * * 1-5`. It left **no beacon commit
and no branch** on Thursday 2026-10-29. That is the third consecutive Thursday
with no beacon:

| date | day | panel | daily audit | steward |
|---|---|---|---|---|
| 2026-10-15 | Thu | **dark** | ok | ok |
| 2026-10-22 | Thu | **dark** | ok | ok |
| 2026-10-29 | Thu | **dark** | ok (this run) | due 23:00Z |

Read across the whole of 2026-08-01 → 2026-10-29 (every weekday, from the
beacon branches' committer dates in UTC), those three are the **only
panel-specific dark days**. Every other dark day the panel has had falls inside
a block that took other routines down with it — 08-25→08-27, 09-07→09-10,
09-22→09-24, 10-12→10-14 — and those blocks are already recorded elsewhere.
So the isolated misses are three for three on Thursdays, and nothing else.

Two observations that bear on cause, neither of them proof:

- the two most recent misses each follow a Wednesday on which the implementer
  routine **built pull requests** (10-21: two; 10-28: three). On the three
  Wednesdays where the implementer ran and built nothing (09-16, 09-30, 10-07),
  the following Thursday's panel ran normally. 10-15 does not fit: the
  implementer was itself dark on 10-14, so there was nothing to spend.
- the panel fires at 13:00Z, earliest of the weekday routines. `ops/ROUTINES.md`
  already records one capacity inversion of exactly this shape, where fire
  order rather than priority decided which routine starved.

From a cloud routine there is no way to separate "never fired" from "fired and
died in seconds": the routine control plane is not reachable from this session,
and a beacon branch records only success. Both readings are consistent with
what is on disk.

**Falsifiable prediction, recorded before the fact:** if the mechanism is
capacity spent by a productive Wednesday implementer run, the panel is dark on
the Thursday after any implementer run that opens a PR, and healthy otherwise.
The next test is Wednesday 2026-11-04 → Thursday 2026-11-05.

## The part that is a detector defect, not a routine problem

Three Thursdays went by without the owner being told, and that is not an
accident of attention. The fleet digest's routine-liveness section cannot
report a miss that has ended.

`_gather_routine_liveness` (`src/thales/execution/fleet_digest.py`) counts
missed fire dates **from the most recent beacon forward**:

```python
fires = _cron_fire_dates(r["cron"], last + timedelta(days=1),
                         today - timedelta(days=1))
row["missed"] = len(fires)
```

So the count is relative to `last`. The moment a routine runs again, every
earlier miss leaves the window. Executed against the production functions for
tomorrow's digest:

```
A) panel runs Fri 10-30 -> missed = 0   -> "routines: 7/7 reporting on schedule"
B) panel dark Fri too   -> missed = 1   -> "panel: 1 missed since 10-29"
```

Since 2026-10-07 the Friday digest is the only email the system sends. So if
the panel runs tomorrow morning at 13:00Z — as it has after each of the two
previous Thursday misses — the 15:30Z digest will tell the owner that all seven
routines are reporting on schedule, on the day after the third miss in three
weeks. With a weekly email and a daily cron, a routine can miss four days of
five and still read healthy, provided the fifth one works.

This was **identified on 2026-10-23** (daily audit finding 2; restated in
`research/steward/2026-10-23.md`: *"the dark count starts at the most recent
beacon, so an outage that has ended is invisible"*) and deliberately deferred
to the research queue rather than bundled into PR #273. **It never reached the
queue.** `research/queue/open/` has carried no such row for six days, and in
those six days the defect hid a third miss. The row is filed with this note
(`rlv-1`), which is the whole remedy for the deferral half.

## Why a trailing window and not a ledger

The obvious fix is to have each digest record the dark days it saw. The better
one needs no state at all: the beacon branches already hold the full history,
so a trailing window recomputed from `git log` over the last N days is
idempotent, cannot drift, and needs no write path in the one job whose failure
costs the owner his only email. The row specifies that shape.

## What this run did

- recorded the measurement (this note)
- filed `research/queue/open/rlv-1-dark-count-has-no-memory.md`
- did **not** write the code. The change lands in the renderer of the owner's
  only email, and the next email is tomorrow at 15:30Z; a same-day edit to that
  path to fix a reporting-latency bug is the wrong trade. It goes down the
  house road: triage Monday 11-02, implementer slot Wednesday 11-04.
- stated the panel's three Thursdays in the outbox report, because the alarm
  layer demonstrably will not.

## Residual

The cause of the Thursday misses is not established and is not fixable from
inside the repository — a routine's schedule and model live in the claude.ai
control plane, which routines may not edit. If the 11-05 prediction holds, the
cheapest remedy is to move the panel's slot away from the morning after the
implementer, or to separate their model pools, which is the remedy
`ops/ROUTINES.md` already reached for the same shape in September.
