ATC — Air Traffic Control

ATC is an agent orchestration system that coordinates multiple autonomous agents working on concurrent code changes in a shared repository. It uses aviation terminology as its domain language — changes are "crafts" flown by "pilots" who navigate "vectors" and request "landing clearance" from a "tower" to merge.

Quick Reference

Term	Meaning
Craft	Unit of work tied to a git branch
Pilot	Autonomous agent with certifications
Captain	Pilot-in-command, final authority
First Officer	Certified co-pilot, can modify code
Jumpseat	Observer/advisor, cannot modify code
Vector	Milestone with acceptance criteria
Flight Plan	Ordered sequence of vectors
Black Box	Append-only event log on every craft
Tower	Merge coordinator, one per repo
Controls	Exclusive or shared code modification rights
Intercom	Crew communication channel
Origin Airport	Design stage; emergency return destination

Documentation

Getting Started

• Getting Started — End-to-end walkthrough of the ATC workflow

Concepts

• Crafts — The unit of work, tied to a branch
• Pilots & Seats — Roles, permissions, and certifications
• Craft Categories — How changes are classified
• Controls — Exclusive and shared code modification rights
• Intercom — Crew communication and radio discipline
• Vectors & Flight Plans — Milestones and routes
• Black Box — Append-only audit trail
• Tower — Merge coordination
• Origin Airport — Design stage and emergency returns

Lifecycle

• Craft Lifecycle — States, transitions, and the state diagram

Protocols

• Vector Reporting — Filing milestone completion reports
• Landing Checklist — Pre-merge validation
• Emergency Declaration — When a craft can't land
• Tower Merge Protocol — The merge sequence

Reference

• Formal Specification — The authoritative spec with numbered RULE-* identifiers
• Design Brief — The original informal design notes
• Contributing — Validation checklist for changes
• Agent Operating Manual — Behavioral guidance for pilots