Skip to content

Air traffic control

This workflow defines the "Air Traffic Control" (ATC) protocol. It is designed to ensure "Friendly Skies" by preventing branch stagnation and collision. See Risk Assessment Report for context.

Protocol: The ATC Loop

This cycle must be performed as part of the Morning Protocol (/goodmorning).

1. Scan (Inventory)

Visualize the current airspace. // turbo npx tsx scripts/ops/flight-radar.ts

2. Deep Dive (Risk Analysis)

For every flight measuring Orange (Turbulence/Diverged) or Yellow (Landing/Behind), perform a deep dive:

  1. Check Fuel: Is the code stale (> 3 days)?
  2. Check Cargo: Run git log tst..[branch] to see what is on board.
  3. Check Trajectory: Run git diff --stat tst...[branch] to see the collision risk.

3. Risk Formulation

Categorize each stranded flight:

  • Legacy/Debris: Old experiments, superseded features. -> Recommendation: CRASH (Delete)
  • Stranded Value: Useful code that got left behind. -> Recommendation: LAND (Rebase & Merge)
  • Active Traffic: Currently in flight. -> Recommendation: MONITOR

4. Execute (Clear the Skies)

  • To Crash: git branch -D [branch_name]
  • To Land: 
    git checkout [branch_name]
git rebase tst
git checkout tst
git merge [branch_name]
git branch -d [branch_name]

5. Final Report

Run the Radar one last time to confirm a pristine board. // turbo npx tsx scripts/ops/flight-radar.ts