Which rows are PUMP-FED — the rows a client must DECLARE before it is sent them, keyed by path
template, each true (demand gate §3d, an internal spec).
A pump-fed row (/meters, a channel's /rta and /spectrum, /telemetry/*) is produced only
while somebody watches it and reaches a root-stream subscriber only for the entries in that
subscriber's demand. Which rows those are was, until this sheet, knowledge only the server held
— its pump table — and every client painted them from a hand-placed declaration a widget author
had to remember; the analyser panel drew nothing the night one was forgotten. So the fact is
published as CONTRACT, in the same index body the travels ride, and the generic row client
declares any flagged row it displays without the widget naming anything beyond the row it reads.
A row-wide fact, so it lives BESIDE ResourceTravels rather than inside a row's field
map: a row may well have a FIELD called demand, and a row-level key inside the field map
would collide with it. Derived from the pump table by the router that answers OPTIONS — there
is no second list to keep in step, and a row absent here is board state needing no declaration.
Which rows are PUMP-FED — the rows a client must DECLARE before it is sent them, keyed by path template, each
true(demand gate §3d,an internal spec).A pump-fed row (
/meters, a channel's/rtaand/spectrum,/telemetry/*) is produced only while somebody watches it and reaches a root-stream subscriber only for the entries in that subscriber's demand. Which rows those are was, until this sheet, knowledge only the server held — its pump table — and every client painted them from a hand-placed declaration a widget author had to remember; the analyser panel drew nothing the night one was forgotten. So the fact is published as CONTRACT, in the same index body the travels ride, and the generic row client declares any flagged row it displays without the widget naming anything beyond the row it reads.A row-wide fact, so it lives BESIDE ResourceTravels rather than inside a row's field map: a row may well have a FIELD called
demand, and a row-level key inside the field map would collide with it. Derived from the pump table by the router that answersOPTIONS— there is no second list to keep in step, and a row absent here is board state needing no declaration.