Airforge

Airforge / independent software studio

Quiet tools for complicated work.

Airforge builds rigorous tools for work shared by people and software agents. It focuses on the state, ownership, and evidence that keep work coherent as it changes hands.

Changed conditions

Execution moves. Coordination holds.

Work now moves between people and software agents, often across interrupted sessions and incomplete context. Faster execution does not make ownership, progress, or evidence durable by itself.

The missing layer is coordination: a shared account of what should happen, who owns the next move, and what the work produced.

A durable middle layer

Intent becomes accountable work.

  1. 01 / input

    Intent

    Purpose, constraints, and the outcome that matters.

  2. 02 / durable state

    Coordination

    Ownership, status, dependencies, history, and evidence.

  3. 03 / action

    Execution

    People and software agents perform the work.

Progress and outcomes return to coordination.

Intent defines what should happen. Coordination preserves the state, ownership, dependencies, and evidence needed to act. People and software agents execute the work, then record progress and outcomes back into the coordination layer.

Axial by Airforge / Preview

Durable coordination for people and software agents.

Current mechanism / Atomic claim

One conditional write establishes a single owner. A competing claim returns an explicit conflict the caller can branch on.

First caller
Claimed
Competing caller
Conflict / exit 4
Explore Axial

Working principles / 03 of 06

Positions that shape the system.

  1. Work needs durable state outside any one context window.

    Decisions, status, history, and handoff context persist independently of the actor currently doing the work.

  2. Coordination must make races and failure explicit.

    Contested operations are atomic, conflicts are named, and callers receive outcomes they can branch on.

  3. Interfaces used by agents are public contracts.

    Outputs, errors, and exit behavior are specified, versioned, and tested as deliberately as an API.

Read all six principles

Airforge / field note

6 min read

When another system reads the output

When software acts on an interface, output formatting becomes system behavior. A field note on explicit results, branchable failure, and executable contracts.

Read the field note