monad10_console_20260830-020140

In plain words A library keeps three lists: what was delivered, what was catalogued, and who checked it out. A measurement corpus needs the same three, and a gap between them is a fact about the pipeline, not about the room. This is the ledger, per day and receiver, with every session as a row you can open.

The rate ladder

monad10, profile console, 2026-08-30 02:01 to 07:51 (350 minutes), 1 segment. Infrastructure: no card can claim it.

Counts and yields

Records	2,339,894
Frames the radio saw	2,432,057
Empty records	182,655
useful_yield	0.8870
capture_yield	0.9621
Empty share	0.0781
Mean rate	111.5 Hz
Bytes	0
Band / channel / width	5 GHz / 44 / HT20

Quote useful_yield: (records − empty records) ÷ frames the radio saw. capture_yield counts an all-zero record as delivered. A low capture_yield on 2.4 GHz is DSSS/CCK traffic that yields no channel estimate, not a quiet channel. Both are derived ratios from two independent counters and exceed 1.0 on some sessions; the counts are exact, the ratios are not.

State

Sealed	no
Decoded	undecoded (0 of 1 segments)
Projected note	no
Integrity flags	`unsealed` `empty-records`
Run id	`lib-cross-chan-drift-2026-08-29-01`
csid	0.2.0

Record classes

No record class: the lake has not decoded this session's frames, so nothing is known about what the channel carried.

Other sessions on monad10 that day · This session as JSON