ariadnev

Local execution control plane

Agent work you can route, gate, and prove.

  • ariadnev installs one curated workflow kit across your coding-agent targets from a single local-first CLI.
  • Then it runs provider-neutral workflow graphs through a durable local executor that enforces policy before a provider ever acts.
  • Every run is event-sourced, resumable, and answerable: which path executed, which gate held, what proof it produced.
Install ariadnev Read the docs
macOS / Linux curl -fsSL https://ariadnev.com/install | bash

Current release ariadnev@1.1.0 · published 2026-08-16

  1. Compile A compiled graph digest
  2. Policy An allow or a denial, decided locally
  3. Execute An append-only event log
  4. Checkpoint A resumable run under ~/.ariadnev/runs/
  5. Proof A stable JSON envelope you can diff
Every av run moves through these five states in this order. The map below narrates each one.

The map

One run, five states you can point at

The documented public pipeline follows one track from compile to proof.

The trace repeats the lifecycle dossier beside it; it never replaces it.

  1. compile

    Compile

    Meaning
    A canonical, provider-neutral graph is compiled and linted from the kit. Provider settings never enter the intermediate representation.
    Evidence
    A compiled graph digest
    Boundary
    Schema drift or an unknown node kind stops the run before policy.

  2. policy

    Policy

    Meaning
    Authority is resolved before any provider is contacted: which capabilities a node may use, whether it causes an effect, and whether a human must approve it.
    Evidence
    An allow or a denial, decided locally
    Boundary
    An effect requested with no matching executor is refused, not silently skipped.

  3. execute

    Execute

    Meaning
    The runner drives the graph through the executor registry. Codex and Claude Code implement the same executor contract behind one interface.
    Evidence
    An append-only event log
    Boundary
    Executor errors and runtime timeouts fail the run instead of degrading its output.

  4. checkpoint

    Checkpoint

    Meaning
    Durable state is written outside the inspected workspace, so a run survives interruption and can be resumed, inspected, or cancelled.
    Evidence
    A resumable run under ~/.ariadnev/runs/
    Boundary
    Envelope corruption or a seal mismatch refuses resume rather than reconciling silently.

  5. proof

    Proof

    Meaning
    Resuming re-checks the instruction digest, workspace identity, graph digest, runner contract, runtime, runtime version, and model. A mismatch is reported rather than silently reconciled.
    Evidence
    A stable JSON envelope you can diff
    Boundary
    Identity drift or a digest mismatch is reported instead of accepted.

Source: Graph execution. Compile, policy, and execute are the documented public pipeline of `av run`; checkpoint and proof name the durable-state and resume behaviour the same document specifies. The five names are this page's vocabulary for that behaviour, not five stages the runtime reports under these labels.

Authority boundary

Where the graph stops, and where the provider stops

Workflow authority and provider projection are recorded separately below.

Canonical workflows

Three graphs, three authority boundaries

The shipped graphs are summarized by authority, human gate, and recovery.

read-only-delivery

Read-only repository delivery

Authority
Reads the workspace and writes run state. No node in the graph declares a workspace effect, so there is nothing for it to mutate.
Gate — held for a human
A verify gate stands between the answer and completion: an answer that cannot cite evidence does not reach a terminal success state.
Recovery
Every non-terminal node can route to failed or cancelled, so an interrupted run ends in a state you can read rather than an unknown one.

Publicly executable today on Codex and Claude Code.

bugfix-delivery

Root-cause bugfix delivery

Authority
Diagnosis is separated from repair. Only the fix node declares a workspace effect, and it cannot be reached without passing the approval node first.
Gate — held for a human
An explicit human approval node sits between diagnosis and any change, so a plausible-sounding root cause never becomes an unreviewed edit.
Recovery
Diagnosis and repair both carry self-edges for bounded retry, and both route to failed or cancelled instead of continuing on a broken premise.

Validates today; active execution is policy-denied until a public side-effect and approval surface exists.

safe-change-delivery

Safe repository change delivery

Authority
A proposal is assessed before authority is granted. The apply node is the only one holding a workspace effect, and it is idempotent so a retry cannot double-apply.
Gate — held for a human
Assessment can decline outright. When it does not, a human approval node still gates the apply, and test and review run after it before completion.
Recovery
Decline is a first-class terminal state, distinct from failure — a change that should not happen is recorded as a decision, not an error.

Validates today; active execution is policy-denied until a public side-effect and approval surface exists.

Source: Workflow reference. Graph structure is a static contract. It does not by itself prove that a given provider behaves correctly at run time.

Provider adaptation

One kit, written only where the path is known

Where a target path or format is not verified, ariadnev skips the artifact and logs it in the install summary rather than writing a guess.

  • claude-code Widest surface: skills, agents, commands, rules, scripts, and hooks.
  • codex Skills and scripts at the shared agent home; agents and commands under the Codex home; rules as AGENTS.md.
  • cursor Commands and rules in Cursor's own conventions; skills, agents, and scripts under the shared agent tree.
  • opencode Skills, agents, commands, and scripts under the opencode tree.
  • antigravity Skills, rules, and scripts; unverified targets are skipped, not guessed.
  • generic The portable floor: skills, rules, and scripts for anything else.

Coverage differs per provider and changes between releases. The generated matrix is the authority; this projection is not. The generated matrix lives in Provider matrix, and the installation guide is in the documentation.

Evidence ledger

What is proven, and where the proof stops

Claim, source, and limit stay together in every record.

Install

One command, then pick your providers

The installer resolves the binary for your platform, verifies its sha256, and links the short `av` alias. The CLI is standalone and needs no Node runtime.

Platform commands

macOS / Linux curl -fsSL https://ariadnev.com/install | bash

Windows (PowerShell) irm https://ariadnev.com/install.ps1 | iex

After installing

First-run guide Release notes

Read the script first

Prefer to inspect the script before piping it into a shell? Open https://ariadnev.com/install — it is the same anonymous path the command above fetches, and no authentication is involved.