ReadonlycontrolWhat KIND of control carries it. Neither fact is numeric — role is one of two declared
words and model is a string the desk reports — so neither has a travel to declare, and
the census reads them as EXEMPT rather than as gaps. That distinction only exists because
this column does.
ReadonlyownerWHO owns the fact, in the shared OwnershipRule vocabulary. Both facts today are
{ kind: 'device' }: the connected ADAPTER carries them, and the rule's own words fit
exactly — "an external actuator outside the native lane array, gated on THAT actuator's own
presence". The gating is not decorative here: with no adapter connected the row has no
instance at all, which is that clause holding rather than a special case.
ReadonlypersistedRides the session file. Both are false: a session restored onto a different desk must
describe the desk it is ON, never the desk it was saved from — restoring model: "X32"
onto this console would make every client draw a mixer that is not here.
ReadonlywritableWhether a client may write it. Both facts today are false: they are properties of the
ADAPTER this console booted with, not settings — a desk does not become a Midas because
someone PATCHed model. OPTIONS publishes the reason so a surface can say why.
What one console-level fact declares.