The workflow runtime
Work that waits. Remembers. Recovers.
toto foundry keeps consequential work moving across people, systems, time, and failure without losing the reason a decision was made.
More than a request
A process can outlast the moment that started it.
Durable state
Conductor OSS retains workflow progress, identity, policy decision, approval state, and correlation across the full life of the work.
Human decisions
Approval waits preserve the proposal, evidence, policy result, approver, and final decision rather than reducing judgment to a checkbox.
Recovery by design
Retries, timeouts, escalation, compensation, and transparent pending states are part of the workflow, not emergency patches.
A clean division of work
Commands change state. Events carry facts. Workflows coordinate time.
- Own the commandA domain service validates, authorizes, and changes its authoritative business state.
- Publish the factKafka distributes a versioned event through a reliable outbox, ready for replay and correlation.
- Coordinate the outcomeConductor OSS drives the durable process and invokes bounded AI only where reasoning is genuinely useful.
Correctness over appearances
No false success.
When a dependency is unavailable, toto foundry waits, retries, compensates, escalates, or makes the pending state clear. It does not invent a completed outcome, silently lose the work, or let a model choose an irreversible shortcut.
Traceable by default
Every outcome has a path back to its evidence.
Workflow history connects the initiating identity, event, policy, approvals, agent activity, exception handling, and result. Operations teams can intervene with context, and auditors can understand what happened without reconstructing the story from logs.
Return to the platform overview