Parameters
- fact:
| "fader"
| "gain"
| "pan"
| "divergence"
| "trim"
| "polarity"
| "align"
| "name"
| "colour"
| "instrument"
| "hrp"
| "eq"
| "gate"
| "dynamics"
| "drive"
| "delay"
| "reverb"
| "width"
| "order"
| "chain"
| "sends"
| "mute"
| "soloSafe"
| "link"
| "gateKey"
| "fbs"
| "record"
| "toMain"
| "sources"
| "sourceRef"
| "sourceStereo"
| "solo"
| "headAmp"
| "inserts"
| "meter"
| "rta"
| "recallSafe"
| "members"
| "parents"
| "clip"
| "source"
Returns readonly (
| "fader"
| "gain"
| "pan"
| "trim"
| "phantom"
| "polarity"
| "name"
| "comp"
| "eq"
| "gate"
| "width"
| "mute"
| "pad"
| "solo"
| "inserts"
| "meter"
| "sens"
)[]
its feature words, in declaration order; empty when it projects into none
The capability WORDS a fact projects into the 15-word feature vocabulary — empty for the majority of facts, which is the asymmetry this spec names outright ("the contract serves ~30 facts through 15 feature words").
Exported because a consumer that must ask a LIVE capability row about a fact first needs to know whether the row can be asked at all: a fact WITH words is answered by the row, a fact without one by this table's
kindscolumn. Both readings then come from this file, so the correspondence has no second place to be spelled (channel-clipboard-carriage.tsis the consumer, and #57's paste refusal is what needs it).