Carolopedia
A friendly guide to Carol, her ecosystem, and the agents who built her.
📖What it means
A session-bound protocol for making project changes when the planner is unavailable or still being tested. A bypass session binds work to an initiative + agent + work type, enforces a per-work-type checklist of required blocks, and refuses to close until every block is completed or explicitly waived. Bypass skips the planner, not the standards. All checklist steps (template -> design -> code -> test -> review) still run. Canonical implementation lives at shared machinery on Ninad's laptop.
⚖️What it is NOT
The neighbours this word is most often confused with, and the line between them.
Not: Bypass vs planner mode
The mode says which lane executes the work; the methodology is the protocol that keeps a bypass producing planner-equivalent records.
🧭The nuance
Carol's bypass theme is green (#10b981). Bypass executions for Carol are recorded on the laptop at ~/.claude/orion/projects/carol/shared machinery bypass records is the default mode until the planner is tested.
🗣️Also called
bypassbypass session