v1.4

SCL Workflow Engine

Deterministic workflows for AI systems.

Execute stage-based pipelines with verifiable state, crash-safe recovery, and automatic invalidation when upstream data changes.

No hidden state. No guesswork. No silent corruption.

SCL defines identity and canonical execution.

This engine enforces it.

What this is

A workflow engine where execution is driven by explicit state, not implicit runtime behavior.

Each stage:

The system always knows where it is and what is valid.

What makes it different

Identity enforced at the protocol layer

SCL-bound stages must match canonical hashes or execution is blocked. No exceptions.

Deterministic recovery

After a crash, execution resumes from the earliest valid stage. No replay guessing.

Automatic invalidation

If upstream data changes, dependent stages are invalidated transitively. Nothing stays stale.

Append-only state

Every transition is recorded. Nothing is overwritten. Completed outputs are immutable.

What you're seeing

This is a reference implementation of the SCL-Orchestrated Workflow State Contract.

The demo shows:

Why this exists

Most workflow systems rely on implicit state, logs, and retries.

When things break:

This system removes that ambiguity.

If the state is valid, the workflow is valid.
If the state is invalid, execution stops.
Validate Workflow Object

Validates structural and semantic integrity of workflow objects against the v1.4 contract. Returns spec-defined error codes: ERR_REQUIRED_FIELD_MISSING, ERR_ENUM_INVALID, ERR_STATE_INVALID, ERR_SCL_NOT_BOUND. Edit the JSON directly to test your own objects.

Execute Workflow

Executes dependency-ordered stages with checkpointing. Validates the full job, resolves the dependency graph, enforces SCL canonical identity invariants on bound stages, and emits append-only checkpoints for each state transition.

SCL Binding Verification

Enforces the canonical byte invariant: bytes flow from scl_parse to scl_sha256 with zero transformation. Try the correct hash, then try a wrong hash to see ERR_SCL_CANONICAL_MISMATCH.

Deterministic Recovery

Simulates crash recovery following the exact 7-step process from §12. Execution is interrupted after parse-input completes. The recovery engine applies the 6 deterministic revalidation triggers and resolves the earliest safe resumption point. No guessing.

parse-input
scl-transform [SCL]
finalize
Invalidation Cascade

Simulates an upstream artifact change that breaks the canonical hash on scl-transform. The engine raises ERR_SCL_CANONICAL_MISMATCH and transitively invalidates all downstream dependents. Unaffected stages keep their valid state.

parse-input
scl-transform [SCL]
finalize

Break the workflow