Skip to content
orch8.io

Portable Continuity

Portable Continuity keeps one durable execution coherent while work moves between server, edge, mobile, or federated runtimes. It combines ownership fencing, effect evidence, signed state transfer, placement, migration, and bounded diagnostic history. These capabilities shipped in Orch8 0.7.0 and are included in the current 0.7.1 stable release.

Note
Orch8 checkpoint inspection is intentionally bounded by retained checkpoints and redacted diffs. It is not an immutable replay of every workflow event. Use the audit log and handler telemetry when you need application-internal event evidence.

Continuity model

Stable identity and ownership

A continuity ID follows an execution across runtimes. Monotonic ownership epochs fence stale owners during handoff, recovery, and failover.

Effect safety

The universal effect ledger records dispatch and commit evidence for built-ins, plugins, WASM, ActivePieces, gRPC, and external workers. Commit guards and provider idempotency prevent unsafe duplicate effects.

Portable handoff

Signed capsules carry bounded execution state. Placement previews account for capabilities, trust, residency, connectivity, battery, cost, latency, and drain state before a destination takes ownership.

Inspectable evidence

Checkpoint indexes, redacted state diffs, provenance verification, effect-free what-if runs, deterministic fault scenarios, and extracted production tests make recovery decisions reviewable.

Controlled change

Live migration uses explicit plans, bounded transforms, approval evidence, resumable transfer, and narrow rollback instead of silently changing an in-flight execution.

Receipt-backed compensation

Compensation is a new recorded effect. Plans reverse only effects known to have committed and retain unresolved residuals for an operator.

Inspect an execution

Bash
# List retained checkpoints
GET /api/v1/continuity/executions/{continuity_id}/checkpoints?tenant_id=acme

# Inspect one checkpoint and its redacted diff
GET /api/v1/continuity/executions/{continuity_id}/checkpoints/{checkpoint_id}?tenant_id=acme

# List and verify cryptographic provenance
GET /api/v1/continuity/executions/{continuity_id}/provenance?tenant_id=acme
POST /api/v1/continuity/executions/{continuity_id}/provenance/verify

Effect-free what-if analysis

What-if runs evaluate a retained state against controlled inputs without dispatching provider effects. Use them to explore recovery choices, compare migration outcomes, or turn an observed production state into a deterministic test before applying a change.

Live migration and rollback

Bash
orch8 execution migration-plan plan.json
orch8 execution migration-get <plan-id> --tenant-id acme
orch8 execution migration-apply <plan-id> approval.json
orch8 execution migration-rollback <plan-id> rollback.json

Create and review a placement or migration plan from fresh runtime facts. Applying a plan revalidates its evidence, transfers bounded state, and advances ownership. Rollback is deliberately narrow and cannot erase an external side effect that already happened.

Related guides

The running server's /api-docs/openapi.json is authoritative for the exact wire contract of the version you deploy.

Ready to try Orch8?

One command to install. Then run your first local sequence.

Bash
curl -fsSL https://orch8.io/start.sh | sh
Quick Start GuideOr skip the setup with Cloud →
Previous← Versioning & MigrationNextAdvanced Features →
Was this helpful?