Runs the way it's written, never crashes.

SPEC × RUNTIME

The spec and the runtime are two different things.

FlitFlow is defined as a common specification, independent of any single language. The Python runtime is one official implementation that conforms to it. The same AST script produces the same result on any implementation that follows the spec.

CORE GUARANTEES

Four things the spec guarantees.

Every conforming implementation is required to hold these.

QUICK LOOK

Your first flow, in four lines of AST.

Full usage is covered in the documentation. This is just the shape of it.

# 1. Define a workflow as an AST
ast = {
    "main": [
        { "function": "set_variables", "args": { "message": "Hello, FlitFlow!" } }
    ]
}

# 2. Validate against the spec, then run it
engine = RuntimeEngine(ast)
register_builtin_functions(engine)

state = {}
result = engine.run(state)

print(state["message"])   # Hello, FlitFlow!
print(result.status)     # Status.SUCCESS

SPEC COMPLIANCE

Verified by tests, not by assumption.

FlitFlow treats compatibility as something to prove, not promise.

USE CASES

Where FlitFlow fits.

ROADMAP

Where the spec stands.