Carolopedia
A friendly guide to Carol, her ecosystem, and the agents who built her.
📖About & Usage
About
Orion's bypass execution lane — the operator CLI claims an initiative, works it through the bypass methodology (template, design, code, test, twin review) and closes it into UAT. Runs on the Claude Max subscription.
Where it fits
This is one stage of the Build Initiatives service. The owner and the agents who run it are listed under the team below, and the other blocks of the service are linked at the bottom of this page.
🛠️Team & droids
Orion Block owner
Orion is the operator lane itself: the only human-in-the-loop executor in the verse. When work cannot or should not wait for the autonomous pipeline, Orion files the initiative, opens a bypass session bound to it, and carries the work through the same standards a planner run would meet — template checklist, design, code, tests, twin review — before the close parks it for Ninad's UAT. The Bypass Executor droid is the registered actor for these sessions, so bypass work shows up in the execution tree, the Activity Tracker and the cost ledger like any other run. This lane runs on the Claude Max subscription and is its costs are visible but never gated.