Verifiable coding agent runtime
Defines the runtime, loop, workflow, and software-factory layers, then explains what the runtime controls.
Use this index to find the right Atomic reference without reading the same material twice. Product explainers define concepts. Maintained documentation specifies current behavior. Source links expose the implementation. Selected field notes record the engineering context behind particular workflow designs.
Start with the runtime explainer if Atomic is new to you. Use the TypeScript SDK guide when you are ready to author a workflow. Use the built-in workflow catalog to compare shipped control and review shapes. Use the hosted documentation for the complete current API.
Defines the runtime, loop, workflow, and software-factory layers, then explains what the runtime controls.
A conceptual guide to stages, handoffs, dynamic execution, checks, artifacts, review, and recovery conditions.
Provides a practical model for acceptance contracts, evidence, fresh-context review, gates, retries, checkpoints, and human escalation.
Provides current authoring syntax and verified examples for contracts, tasks, parallel branches, artifacts, human input, and composition.
Compares selected workflows built into Atomic, with detailed guides to implementation and design workflows plus six reusable control-flow patterns.
Complete hosted documentation for installation, configuration, agents, tools, extensions, and runtime behavior.
The source of truth for workflow discovery, authoring, primitives, contracts, run controls, composition, and built-ins.
A maintained technical-documentation map for coding agents and other text-first clients.
The open-source repository, README, issue tracker, package source, and contribution history.
Substantial TypeScript workflows used by the Atomic project, including release operations with deterministic gates.
The public authoring surface, runtime implementation, built-ins, and package-level API examples.
Published versions and release notes. Check them when behavior may depend on the installed version.
These articles from the Alex Lavaee blog are historical, opinionated accounts, not API documentation. They provide design context and examples without replacing the maintained Atomic pages above.
Explains why the workflow layer surrounds an existing coding-agent harness and how repo-owned TypeScript makes that process inspectable.
Argues for developer-owned orchestration, explicit handoffs, and workflow visibility beyond a single chat session.
A practical account of separating the agent’s inner reasoning loop from a typed, observable, and resumable outer workflow for production engineering work.
Records the design history of an iterative planning, implementation, and review loop. Treat implementation details as time-bound and verify them against current documentation and source.
Explains why tests must cover semantic and performance claims, not only compilation and happy-path behavior.
This editorial index is an overview; it does not reproduce the full documentation. The complete technical documentation is the source of truth for workflow APIs and current runtime behavior. Use source for implementation evidence, releases for version changes, and field notes for historical reasoning.