Build reliable
workflows.

Make failures predictable.

An open-source foundation for explicit failure handling, predictable recovery, and verifiable consistency — designed to grow across programming languages.

Public APIs are still evolving. No stable release yet.

When a step fails

  1. Workflow begins

    An order is submitted.

  2. Payment fails

    The external service returns an error.

  3. Recovery is attempted

    The outcome is recorded; side effects are not assumed to roll back automatically.

DESIGNED FORAPPLICATION WORKFLOWSFAILURE VISIBILITYRECOVERY VALIDATION

Failures happen.
Uncertainty doesn't have to.

A workflow can span a database, a service, and an external API. A transaction boundary around one component rarely covers them all. Atomic Flow explores what responsible recovery looks like outside that boundary.

Consistency first

Start with the invariants your application must protect, especially when an operation fails.

Explicit by design

Make execution boundaries, failures, and recovery outcomes observable instead of implicit.

Test the bad days

Validate partial execution and recovery scenarios, not only the happy path.

One philosophy.
Distinct responsibilities.

Keep the execution runtime separate from the tools that challenge it. Build for real failures, not just tidy demonstrations.

⌁

PRODUCTION RUNTIME

Atomic Flow Core

Define and execute workflows with explicit boundaries and recovery semantics. The public API and supported guarantees are under active design.

@atomic-flow/coreLearn more ↗
⌬

TESTING & VALIDATION

Failure Lab

Explore controlled failure injection and invariant checks. A testing-focused companion — not an extra runtime requirement for production.

@atomic-flow/failure-labLearn more ↗

Different languages.
Shared expectations.

The project aims to document common behavioral expectations, while allowing each language implementation to feel native to its ecosystem.

TypeScript / JavaScript

The first implementation lives in its own repository. Core and Failure Lab are managed together using pnpm workspaces.

Explore the TypeScript repository
// Ecosystem packages@atomic-flow/core@atomic-flow/failure-lab// Early development · not yet stable
FUTURE POSSIBILITIES
RustGoPythonMore as needed
Ideas, not announced implementations or release commitments.
“The goal isn't to eliminate failures. It's to make their consequences understandable, manageable, and testable.”

Built in the open.
Still taking shape.

Atomic Flow is in its earliest stage. Follow the design, review the evolving documentation, or browse the source. External contributions are temporarily restricted while foundational contracts are established.