monad04_chan-6ghz-psc5_20260911-092733

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

monad04, profile chan-6ghz-psc5, 2026-09-11 09:27 to 09:33 (6 minutes), 1 segment. Quarantined. Unclaimed.

Counts and yields

Records	0
Frames the radio saw	0
Empty records	0
useful_yield	—
capture_yield	—
Empty share	—
Mean rate	—
Bytes	0
Band / channel / width	6 GHz / 5 / 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` `no-records`
Run id	`lib-6ghz-probe-2026-09-11-05`
csid	0.3.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 monad04 that day · This session as JSON