Diagram · command tree · cycle phases
Workflow The current Boston Atlas flow uses three explicit levels. L1 coordinates the full assignment. L2 separates architecture, independent review, evidence, and operations. L3 handles focused edits, tests, provider checks, teardown verification, and receipts. Results return through the same chain, and independent reviewers approve implementation.
Who talks to whom HUMAN AUTHORITY L1 L2 L3 Drake Stapleton purpose · limits · final approval L1 · Conductor scope · sequence · authority · synthesis L2 · Architecture design and implementation steward L2 · Independent review challenge · verify · approve L2 · Evidence tests · hashes · sources · verdict L2 · Operations provider state · cost · teardown L3 · Build cells focused edits · focused tests L3 · Review cells threats · mismatch · falsifiers L3 · Proof cells manifests · receipts · readback L3 · Provider cells inventory · lifecycle · cleanup INDEPENDENT REVIEW CLEARS IMPLEMENTATION L3 RECEIPTS → L2 VERDICTS → L1 SYNTHESIS → HUMAN GO WHEN REQUIRED Cycle sequence 01 Admit bind scope cost and authority 02 Conduct reuse prior work coordinate the sequence 03 Separate independent L2 lanes independent review 04 Execute focused L3 cells edits · tests · receipts 05 Verify exact candidate proof and teardown 06 Close L2 verdicts L1 synthesis · human GO Each gate preserves the evidence and returns the exact result to the next focused attempt.