🤝 Top Collaborators
.png&w=640&q=75)
🤓 Latest Submissions
The Arrow Arch - Proof-First AI Dev Crew
Once an arrow leaves the bow you cannot change its path - and with The Arrow Arch you never need to. You type one prompt. You never type again. No "now write the tests", no "that's the wrong folder", no "try again". Whether it is a big project or a one-line fix, the crew takes it from your sentence to finished, tested work. The problem > Using AI on real code today means babysitting it. You keep re-prompting because: - On a big repository it loses the thread - it forgets the middle of its own work while still sounding confident. - It picks the wrong way to fix something - a quick patch where the codebase needed a proper change. - It writes the wrong file format, or puts files in the wrong folder, against how the project is laid out. - When many APIs or services are meshed together, it calls the wrong one, or wires them up in a way the project does not follow. - Run several at once and they edit the same files and collide. - It says "Done" when it only said so, and forgets your project by the next session. Our solution: a full crew behind one prompt The Arrow Arch works like a real engineering team, with each role stopping a different kind of mistake: - Business / PM works out what you actually want and why, so the work solves the real problem, not a guessed one. - Architect decides the right way before anyone builds: which files and folders, which of the existing APIs to use, what shape the change takes. Wrong-format, wrong-folder and wrong-API mistakes are stopped here, on paper. - Workers each build one small, clearly bounded piece in their own private copy of the project, so several can work at once without touching the same file. They write and run the tests too - you never have to ask. - The Orchestrator (Mission Control) keeps the map of who is doing what, keeps every worker inside its lane, and re-runs every check itself instead of trusting a "Done." How you use it > Open the dashboard and fire the Arrow: one sentence. When the plan is ready you glance at it and click approve - it shows green when no company rule is at stake. That is the moment of aiming. After that the trajectory is locked: the crew builds, tests, fixes and lands the work on its own, while you watch a clean status and a Ledger of everything that was proven. No wall of logs. It scales with the size of the job > A small fix becomes one small piece and lands in minutes. A big feature is planned in phases, grouped into modules, and split into many small pieces that run in parallel wherever their files do not overlap. That is worked out by plain arithmetic on the file lists, never by an AI's guess. If a piece fails, the architect re-plans that piece instead of dropping it. Before anything lands, a final check confirms the result matches what you asked for. The impact > In our own test runs on IBM Bob, a from-scratch task was split into two pieces that both landed on the first attempt, every test passing and the main branch untouched, in about eight minutes - a strong model planning, a cheaper one building. To prove the gain we run the same task two ways, Bob Shell alone and Bob Shell inside The Arrow Arch, then compare time, token cost, rules followed and the real output. Who it's for > Developers and teams who want to hand off a whole task on a real codebase - onboarding a new repo, adding a feature, fixing a bug with tests - and get it back done, without steering it every step.
27 Sep 2026
