---
id: SCH-2
family: GR-SCHEMA
level: extended
profiles: [storage-api, editor-client]
posture: normative-target
added: "1.0"
changed: "1.0"
source: https://flowdrop.io/spec/rules/gr-schema/sch-2
specification: FlowDrop Workflow Specification 1.0-draft
licence: CC BY 4.0
---

# SCH-2 — Gate flags come from the node type, and default off

*GR-SCHEMA (Part I) · level: extended · profiles: storage-api, editor-client · added in 1.0*

Whether a parameter is connectable, configurable or required is the node type's answer, not the declared schema's. A parameter the node type never mentions reaches neither derived schema.

## The rule

> **Normative.** This is the rule.
>
> 1. The `connectable`, `configurable` and `required` gate flags for a parameter are read from the node type's own parameter configuration only, each defaulting to false where the node type declares no entry for that parameter.
>
> 2. A parameter the node type does not declare therefore appears in neither derived schema and in neither `required` list.
>
> 3. Same-named keys written in the declared schema are not read by the gate, and are not stripped either: they survive verbatim into the served schemas.
>
> 4. A property-level `required: true` is read on exactly one path: where a node is exposed as a model-facing tool, it is lifted into the enclosing object's `required` array before the schema is handed to the model.

## Related rules

- Names: SCH-3, SCH-6
- Referenced by: SCH-3, SCH-6

---

Rule identifiers are permanent and are never renumbered. This specification carries
no implementation status: each implementation publishes its own standing against
these rules. Licensed CC BY 4.0.