The two independent facts, exactly as hardwarePresence defines them:
present is stageboxConnected — the box completed the JOIN/HOLD handshake and is
streaming. A bridge probing an empty wire is a node, not a box.
bound is isBound: this rig has THIS box on record as its own. Injected, so the answer
comes from the caller's ledger (the console's MAC-keyed registry) and not from a second read
of the wire — which also means a deliberate unbind drives presence exactly as a pulled cable
does, with nothing to unplug.
A box with no identity cannot be looked up and so is never bound: it reads offered while it is
up, which is right — nothing declared it, so nothing is waiting for it.
absent here means LOST, not merely not-here: a box this rig BOUND and that is no longer
answering. That distinction is load-bearing for what comes next. A hand-declared box that has
never bound to hardware (task #63's virtual stagebox, whose whole point is that an operator can
park gains, EQ and dynamics on it before the truck arrives) is a THIRD thing, and it must not
arrive through this predicate: its controls are live, and calling it absent would disable the
one state that exists to be edited. Nothing collapses today — a box with no reac-pw nodes is not
in this list at all — and when the planned state is built it gets its own name here rather than
reusing this one.
Every device in the list is by construction one the graph reports, so the pair only ever
produces ready / absent / offered — never the fourth non-state. A bound box the graph does
not report AT ALL is not in this list to be overlaid; that is the missing-hardware diff's job
(issue #154), a question asked of the session rather than of the wire.
Overlay each detected box with its StageboxDevice.presence — the third seam beside overlayStageboxNames and overlayStageboxContradictions, for the same reason: one place computes it, so every stagebox-producing path publishes the same answer.
The two independent facts, exactly as hardwarePresence defines them:
isBound: this rig has THIS box on record as its own. Injected, so the answer comes from the caller's ledger (the console's MAC-keyed registry) and not from a second read of the wire — which also means a deliberate unbind drives presence exactly as a pulled cable does, with nothing to unplug.A box with no identity cannot be looked up and so is never bound: it reads
offeredwhile it is up, which is right — nothing declared it, so nothing is waiting for it.absenthere means LOST, not merely not-here: a box this rig BOUND and that is no longer answering. That distinction is load-bearing for what comes next. A hand-declared box that has never bound to hardware (task #63's virtual stagebox, whose whole point is that an operator can park gains, EQ and dynamics on it before the truck arrives) is a THIRD thing, and it must not arrive through this predicate: its controls are live, and calling itabsentwould disable the one state that exists to be edited. Nothing collapses today — a box with no reac-pw nodes is not in this list at all — and when the planned state is built it gets its own name here rather than reusing this one.Every device in the list is by construction one the graph reports, so the pair only ever produces
ready/absent/offered— never the fourth non-state. A bound box the graph does not report AT ALL is not in this list to be overlaid; that is the missing-hardware diff's job (issue #154), a question asked of the session rather than of the wire.