---
id: ORC-1
family: RT-ORC
level: core
profiles: [runtime]
posture: normative-target
added: "1.0"
changed: "1.0"
source: https://flowdrop.io/spec/rules/rt-orc/orc-1
specification: FlowDrop Workflow Specification 1.0-draft
licence: CC BY 4.0
---

# ORC-1 — Four execution strategies, each with a stable identifier

*RT-ORC (Part II) · level: core · profiles: runtime · added in 1.0*

The same workflow can be run four ways. Which way is a deployment choice, not a property of the workflow.

## The rule

> **Normative.** This is the rule.
>
> 1. An implementation provides four execution strategies: direct synchronous, synchronous pipeline, asynchronous, and state graph.
>
> 2. Each reports a stable identifier for itself, and that identifier is what callers and stored configuration name it by.

## Related rules

- Names: ORC-2, ORC-5
- Referenced by: ORC-2, ORC-5, ORC-13

---

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.