Documentation / Execution Environments
One workflow model. Three execution domains.
Start local. Run on device and edge. Scale in your own cloud.
Choose where your workflow runs
| Domain | Execution | State & prerequisites |
|---|---|---|
| Local | Develop and debug with CLI subprocess handlers. | In-memory iteration; install the required handler runtimes. |
| Device / Edge | Offline execution of the supported deterministic DAG subset. | Optional SQLite WAL checkpoints; production license and authenticated artifacts; target-compatible handler dependencies. |
| Cloud / BYOC | Distributed workers, execution cells and Controller governance in your AWS account. | Provisioned AWS installation, scoped credentials and compatible installation contract. |
01 · Start local →Install the CLI and iterate without cloud infrastructure.02 · Device / Edge →Validate the supported subset, package and recover offline.03 · Cloud / BYOC →Use existing admission and deployment tooling in your AWS account.Follow one workflow →Ingest → validate → publish, with explicit target configuration.
Shared definitions, target-specific capabilities
Move compatible definitions between environments; configure handlers, dependencies and integrations for each target. Edge rejects cloud-only waits, callbacks, loops, governed tools and rerun controls.
Verified sources
Checked 2026-11-09.
- Native target builder and artifact validation b78d351 · ai/rf-edge-02-cli
- Standalone execution and reconciliation commands b78d351 · ai/rf-edge-02-cli
- Shared artifact integrity and handler extraction b78d351 · ai/rf-edge-02-cli
- Native execution architecture and contracts b7c85c2 · ai/rf-edge-02-docs
- Matching-architecture CI and operator journey b7c85c2 · ai/rf-edge-02-docs
- Native target verification evidence b7c85c2 · ai/rf-edge-02-docs