Documentation / Execution Environments
Follow one workflow across domains
Ingest → validate → publish: keep the definition, configure execution for each target.
Download the shared example
This small DAG passes JSON through three phases. The handler adapts edge input to the local/cloud runner context. It passes a sample document pointer through each phase. Download all files into one directory; Python 3 is required.
document.workflow.yaml · document.handlers.json · document.py · document.input.json
name: document-journey
version: 1.0.0
default_group: python-standard
phases:
ingest:
service: document
mode: sync_lambda
scope: root
validate:
service: document
mode: sync_lambda
scope: root
requires: [ingest]
publish:
service: document
mode: sync_lambda
scope: root
requires: [validate]
terminal: true1. Start local
rippflow validate document.workflow.yaml --handlers document.handlers.json
rippflow dev document.workflow.yaml --handlers document.handlers.json --input document.input.json --report report.jsonExpected: a completed report with the terminal publish phase.
2. Run on device / edge
On matching-architecture CI, set RIPPFLOW_EDGE_SDK to the SDK checkout built in the edge guide, then package the same definition and handler. This script example declares Python 3 as a target dependency; the native sensor example packages a static handler.
"$RIPPFLOW_EDGE_SDK/target/debug/rippflow" build edge --target x86_64-unknown-linux-musl --runtime-source "$RIPPFLOW_EDGE_SDK" --build-cache "$RIPPFLOW_EDGE_SDK/target" --workflow-def document.workflow.yaml --handlers document.handlers.json --external-runtime python3 --env dev --features sqlite,license --out dist/document-edge
./document-edge run --input '{"document":"sample.pdf"}' --db state.db --json
./document-edge recover --db state.db --jsonCopy the executable to the matching target with Python 3 installed. Expected: JSON reports a completed workflow with the document pointer preserved.
3. Scale in the cloud
Keep the DAG; package handlers for AWS and configure service/runtime group bindings through the cloud deployment journey. Admission and target-installation checks remain required. Cloud-only features added later can make the definition incompatible with edge.
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