Antifailure documentation

Antifailure gives a branch its own environment: a masked copy of your production database, your services built and running, and a network that reaches nothing you did not name. Agents drive your real workflows against it and return verdicts with evidence. Then it is destroyed, and the destruction is proved rather than assumed.

Everything here runs on your own machine first. The hosted pieces are optional and come later.

Start here Quickstart From an empty machine to a running environment, and what each command actually did. Needs Docker and a Postgres connection string. No account. Then An environment per pull request The same run inside GitHub Actions, with one comment on the pull request that is edited in place. One file, which af init already wrote, and no server. When you need it When one machine is not enough What a control plane adds, why nothing depends on it, and the shortest path to running one.

Install it

curl -fsSL https://antifailure.dev/install.sh | sh
af init            # reads your repo, writes antifailure.yaml
af golden refresh  # only if the manifest names a production database: set
                   # that variable first, and this makes the masked copy once
af up              # database branch from the golden, built services, sealed network
af test            # agents run your workflows and return verdicts with evidence
af down            # every resource it created, gone

af start reports each of those as observed on this machine and names the next one, so it is the command to run when you are unsure where you are.

The installer puts af under ~/.antifailure and puts that on your PATH by appending one line to the startup file your login shell reads, printing the line and naming the file. Quickstart has the detail, including how to decline it.

The ideas the rest depends on

These pages carry the guarantees. Everything else is a consequence of them.

Goldens How a masked copy of production is built once and branched cheaply. Masking How identifiers are replaced, deterministically, and how that is proved. Verification Why an unverified golden cannot be branched, enforced in code. Egress What an environment can reach, and the mode each host is given. Agents How a workflow written as a sentence becomes a run with evidence. The journal How a killed engine reconciles instead of leaking.

Look something up

If you arrived from an error message, the code in it has its own page. The error reference lists every code the engine can return, what causes it, and what to do next.

Three of the four reference pages are checked against the thing they document, so they cannot drift: the command reference against the command tree, the error reference against the catalogue, and the transform reference against the registry. A build gate fails if any of those stops matching.

The manifest reference is written by hand and no gate compares it to schemas/manifest.v1.json. The generated rendering of the schema is the manifest schema page, and that is the one to trust where the two disagree.

The rest of the documentation is in the sidebar: guides for a stack or a task, database providers, security, self-hosting, and the enterprise edition.

Hand it to an agent

Every page on this site is available as plain text, and the whole of it is one file.

The whole documentation, as one file Every page here as plain text, in the order the sidebar reads. Paste the address into an assistant, or fetch it. https://antifailure.dev/docs/llms-full.txt The index, for a crawler What this product is and where each part of the site lives, in the llms.txt convention. https://antifailure.dev/llms.txt

One page on its own works the same way: add .md to any documentation address, or use the copy control in the bar at the top of every page. The address of this page as Markdown is /docs/index.md.