arthurblattman.dev
← Side projects
Side project · Closed source

Draidock

Several coding agents working in parallel, with every decision point behind a gate that a person holds or delegates to an agent.

Draidock is a delivery protocol for agent-built software. Work moves through a fixed set of roles and approval gates, and each piece of state lives in a native tool: Beads holds issues and comments, Herdr holds agent terminals and Git worktrees, Go Task runs every check, and Git holds branches and merges. Draidock owns the charts, the approvals, the legs, and which files each agent may change.

01

How a voyage runs

A voyage is one unit of delivery, from an order to a verdict.

01
Order

The Admiral orders work from the backlog, and a brief is drafted from it.

gate: brief
02
Chart

The Navigator plans stations, the files each one owns, and the check each must pass. The chart is approved before anything runs.

gate: chart
03
Legs

Crew agents build each station in its own worktree, and the Mate merges a leg once its check is green.

gate: legs
04
Verdict

The finished voyage is accepted, trimmed with a small fix, or rejected and recharted.

gate: accept
a rejection recharts the voyage and runs new legs
02

Roles

One person and a crew of agents, each with a narrow job.

Admiral

The person. Orders the work, holds every gate not delegated, and ships: merging to main and pushing are always the Admiral's.

Captain

An agent that decides the gates the Admiral delegates to it, and escalates anything it can't decide back to the Admiral.

Navigator

Turns an order into a chart: the brief, mocks or findings, resolved questions, and stations with the files each one owns.

Mate

Runs the voyage. Dispatches the crew, confirms each station changed only its own files, merges green branches, and waits on every gate.

Crew

Coding agents, one per station, each in its own Git worktree with its own files and a check it must pass.

Surveyor

An independent reviewer that judges work it didn't write, from the chart before the first leg to the finished voyage, and changes nothing.

Purser

Keeps the backlog. Turns observations and crew proposals into issues, and files only what the Admiral confirms.

03

Gates

Every decision point is a gate, and a project chooses who holds each one.

Each gate is held by a person or delegated to the Captain agent. A project picks a preset: supervised keeps every gate with the Admiral, and autonomous delegates every gate but accept.

  • questions Answers to the open questions a chart raises.
  • taste The pick among competing mocks.
  • brief Turning an order into the brief a voyage is charted from.
  • chart Approving the plan before the first leg.
  • legs Authorizing each leg, or one go for every leg that stays clean.
  • rechart Replanning after a rejection.
  • accept The verdict on the finished voyage.

Accepting what ships stays with a human. Merging to main and pushing always stay with the Admiral.

04

Built with it

This site is built with Draidock. The page you are reading was charted, built, and merged as a Draidock voyage, and its chart is committed in the repository beside the code it changed.