The FlowDrop Workflow Specification

The rules a FlowDrop workflow obeys (how a workflow is written, stored, validated, and executed), stated independently of any one implementation.

What this is, and what it is not

This specification is a target. It states what a conforming implementation must do. Where an implementation disagrees with a rule, the rule is what is intended and the implementation has a defect, unless the rule itself is wrong, which is a reportable bug.

It is informative only. It confers no status, issues no certification, and grants no mark. It carries no implementation status: nothing here records which implementation meets which rule. Each implementation publishes its own standing against these rules in its own documentation.

How to read it

• All rules: every rule, filterable by family, profile, level and posture.
• Conventions: must/may, HTTP refusals, JSON, how text is counted. Stated once so no rule repeats it.
• Glossary: the vocabulary the rules are written in.

Rules are grouped into families and cited by identifier (STORE-2, SCH-10). An identifier is permanent: never renumbered, never reused, still citable after the rule is withdrawn. Identifiers appearing in rule text link to the rule they name.

Reading it by machine

The specification is quoted into issues, reviews and model context as often as it is read in a browser, so every page has a markdown twin at its own URL with .md appended — /rules/gr-store/store-2.md, and the same for conventions and the glossary. Each one carries its identifier, its facets and a link back to the rule it came from, so a quotation stays traceable to its source.

• llms.txt: every rule, one line each, with links. An index.
• llms-full.txt: the whole specification as one document, conventions first, rules in the order they were issued.
• rules.json: the corpus as data — every field a rule file carries, plus backlinks and the identifiers this specification has declined, so a tool resolving MIG-1 can tell "not ours" from "unknown".

Cite a rule by identifier rather than by URL where you can. Identifiers are permanent; a URL is only a way of reaching one.

Licence

The specification text is licensed CC BY 4.0. Quote it, translate it, build on it; attribute it.