OutcomeOS documentation

Define the business result you want, attach workflows that work toward it, and let OutcomeOS verify — from real events — whether it happened.

Core ideas

Outcome: a measurable goal (e.g. every qualified lead replies within 24h) with success criteria and trusted event sources.
Workflow: a versioned graph of steps (trigger, HTTP request, condition, delay, wait for event…). Running a workflow never marks an outcome achieved by itself.
Outcome event: evidence such as customer.reply_received. Only events from sources the outcome trusts count.
Execution: one durable run of a published workflow version, coordinated step by step with retries, idempotency keys and replay.