ReadonlyfactThe contract fact this field belongs to — the provenance that ties the line back to
CHANNEL_CONTRACT and decides whether the apply's clear pass governs it at all.
ReadonlyfieldThe snapshot field that moves. A fact carrying several (align rides delay + reference,
headAmp rides phantom + pad + gain) reports one entry PER MOVING FIELD, because the
operator is warned about the 48 V, not about "the head amp".
Optional ReadonlyfromWhat the channel holds now. Absent when the desk does not KNOW (a head-amp fact on a
channel whose preamp has never reported — onAbsent: 'leave' means absence is ignorance,
not zero) or when the field has no scalar face.
Optional ReadonlyrefusedWhy the desk will NOT land this field — the same coded refusal the field's own row answers
a live PATCH with, resolved through the same contract ownership expression (ownerOf). A
head-stage fact a PEER owns is the one case today: on a sens-capable input the head-amp
entity owns gain, /channel/{kind}/{index}/gain answers OWNED_BY_PEER, and a config
carrying a digital gain must not reach the preamp by the back door.
A refused move carries from and NEVER to: nothing lands, and a predicted landing value is exactly the lie this field exists to stop. The move is still listed, because the operator is entitled to know the config asked for something the desk refuses.
Optional ReadonlytoWhat the apply would land. Absent on a structured field, same rule as from.
One fact-field this apply would move off what the channel currently holds.