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

# SCH-36 — One declaration site for the shipped lane vocabulary

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

## The rule

> **Normative.** This is the rule.
>
> 1. The lanes an implementation ships are declared in exactly one place, and every reader derives from that declaration rather than mirroring it: the derivation's range, the served payload and any picker offering an author a lane included.
>
> 2. That set is what is shipped, not a ceiling: a site may add lanes of its own, so a stored lane must never be rejected merely because it is not one of the shipped ones.

## Related rules

- Names: SCH-10.a, SCH-41
- Referenced by: SCH-10, SCH-41

---

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.