BUILD / RUN LOOP
Frontier → Build → Run → back to Build. Eleven stages, closed loop. Sourced verbatim from the founder's vision doc.
// Flow 1 — Build/Run Feedback Loop
The construction-to-usage cycle. Starts at Frontier scouting, ends at Performer usage data flowing back to Architects. Closed loop by design — usage shapes the next pitch.
01
Frontier Scouts
Scouts watch the edges. Surface signals worth tracking — new tools, threats, opportunities.
02
Convergence Packages
Convergence consolidates scout findings into coherent packages worth pitching.
03
Architects Pitch
Architects propose what to build, why, for whom. Concrete blueprint with success criteria.
04
Critics Red-Team
Critics tear the pitch apart. Stress-test assumptions, find structural weaknesses.
05
Killer Screens
Eulogists' kill gate. Does the project deserve to live? Apply the Revival Gate.
06
Executioner Ships
Executioner is the ship gate — the actual builder turning blueprint into deployed code.
07
Auditors Verify
Auditors confirm the shipped thing matches the blueprint. Catch regressions before release.
08
Run Operates
Run takes over once shipped. Day-to-day operational ownership.
09
Concierges Face Users
Concierges are the user-facing layer. Onboarding, support, listening.
10
Operators Handle Ops
Operators handle the moving pieces — infrastructure, queues, batches, watchdogs.
11
Performers Use → Loop Closes
Performers actually use the system. Usage data flows back to Architects. The loop closes.
no instances logged yet · flow timeline activates when first verdict cites this loop