Composable workflows
Recipes.
Formulas chain into Chains.
Atomic steps bond into single-Engine Formulas. Formulas chain into multi-Engine Chains with HITL checkpoints between them. Author them in plain English. Compile them down to a deterministic, replayable step list.
Chains
Natural-language recipes for multi-Formula workflows. Each Chain compiles into a step list of Formulas + HITL gates.
From English to step list
A Chain is a deterministic plan you can read.
Author it in natural language. Quadrazene compiles to an explicit, versioned step list — Formulas + HITL gates — that runs the same way every time.
What ships in Recipes
Built around how teams actually work.
Atom registry
Narrow-scope agents register input/output schemas (Zod). The compiler binds them safely.
Reaction registry
Ordered atom sequences with cost + token telemetry per step.
HITL gates
Pause for an audience role or specific user, with SLA, channel, and decision notes.
Versioned recipes
Every change gets a version. Roll forward or pin previous versions for stable runs.
Replayable runs
Open any past run, step through, edit a prompt, re-run safely. Diff old vs new.
Cost & latency
Per-step token cost + duration captured. Budget guardrails throttle runaway runs.
Param defaults
Skills carry editable defaults — a chain is one click to launch with sensible inputs.
Failure-mode policy
Per chain: stop, skip, retry, or fall back to an alternate path.
Schedule + trigger
Cron, calendar, event-driven, or upstream-chain-completed. First-class.
Two ways to build
Drag the boxes, or just describe it.
Formulas support full control flow — branch, forEach, try-catch, and sub-formula — authored either visually or in plain English.
Beyond Formulas and Chains
More ways to start and shape a run.
Five kinds of trigger
A Chain starts on a schedule, an event, a completion, a manual click or an API call.
Stream events
Durable Redis Streams and Kafka consumers can fire a Formula per message, or batch-load a table without the reaction engine.
Alerts start Chains
A Radar threshold breach or a Resolver ticket can auto-start a Chain, so the response is a process, not a page.
Agents and APIs
Author background Agents and hosted REST endpoints beside your Formulas, under the same versioning and audit.
Agent teams
A supervisor-planned step dispatches specialist Formulas in parallel, with each member traced as its own run.
Portable
Formulas, Chains and Skills travel as signed Reagent bundles with a diff on import.