GR-SCHEMA

47 rules. Part I of the specification.

• SCH-1A node's ports come from its two declared schemascore
• SCH-2Gate flags come from the node type, and default offextended
• SCH-3One parameter schema splits into two derived schemascore
• SCH-4A hidden parameter is dropped from everythingcore
• SCH-5Reserved config-only parameters always carry a defaultcore
• SCH-6Which required list a required parameter lands incore
• SCH-7An output is exposed unless the node type says otherwisecore
• SCH-8How a schema property becomes a portcore
• SCH-9A union type resolves to its first non-null membercore
• SCH-10The map from a schema type to a port lanecore
• SCH-10.aA site's lane configuration overlays the shipped oneextended
• SCH-11Every node but a start node gets a trigger inputcore
• SCH-12Every node but a terminal node gets a trigger outputcore
• SCH-13A tool-exposed node gets a tool outputextended
• SCH-14Every executable node gets a hidden error outputcore
• SCH-15A reserved port states its exposure only when it divergesextended
• SCH-16What each reserved port defaults to on the canvascore
• SCH-17The unified input portextended
• SCH-18The unified output portextended
• SCH-19A unified port's description skips trigger and hidden keysextended
• SCH-20Visual type is the node type's, and is offered where there is a choiceextended
• SCH-21The reserved config properties every node carriesextended
• SCH-22A config-edit descriptor appears only where one is providedoptional
• SCH-23When a node has a ui schema, and when it has noneextended
• SCH-25Enrichment anchors on the node type and changes nothing elsecore
• SCH-26The catalog an editor readscore
• SCH-27A served port omits everything that matches the defaultcore
• SCH-28A node's executor is resolved from its node typecore
• SCH-29Stored metadata is never authoritative at run timecore
• SCH-31Config field order applies inside a ui schema onlyextended
• SCH-32Every re-enterable node gets a hidden loop-back inputextended
• SCH-33A schema that will not load never rewrites stored parametersextended
• SCH-34A property's type is a JSON Schema type, not a port lanecore
• SCH-35Lane derivation is total, and an undeclared port is the sinkcore
• SCH-36One declaration site for the shipped lane vocabularycore
• SCH-37A control port declares its lane, never a schema typecore
• SCH-38A loop-back input is a control sink, and any is retiredextended
• SCH-38.aA retired lane keeps one release of served-but-disabled compatibilityextended
• SCH-39Compatibility is asymmetric, and the sink needs rules both waysextended
• SCH-40A port's lane is consumed at a public boundaryextended
• SCH-41The lane vocabulary is the served payload, not the shipped setcore
• SCH-42A shape is a named JSON Schema, and the shape id is the lane idextended
• SCH-43Shape compatibility is nominal and mostly derivedextended
• SCH-44A shape refines another declaration of its lane; four ids are reservedextended
• SCH-46A shape's schema is served on the lane, not on every portextended
• SCH-24A node type that fails to build does not fail the requestcore
• SCH-45A stored lane overlay is checked when it is storedextended