The unified input port
The rule
Normative: this is the rule
- A unified
inputport is prepended to a node's ports where its node type exposes one. - It carries the
jsonlane, and its description enumerates the node's connectable parameter keys only.
What it means
The unified input port's description is not a list of every input the node declares — it lists only the keys reachable through it. A parameter can be declared and even shown in the config form without ever appearing there: what qualifies is the connectable gate flag alone, nothing else about how the parameter is otherwise exposed.
Example
A node type declares two input parameters, visible_in and hidden_in, and
marks only visible_in connectable.
"All inputs as JSON object. Available keys: visible_in""All inputs as JSON object. No connectable parameters available"hidden_in never enumerates, whether or not it appears in the config form.
Rule identifiers are permanent and are never renumbered. Each implementation publishes its own standing against these rules; this specification does not.spec 1.0-draft · SCH-17 · changed in spec 1.0