Cerebrus
From spec to pull request without you in the loop. The plan is an executor that watches a queue, picks up an approved spec, runs Claude inside an isolated workspace, and opens a reviewed PR back to the source repo. Today it is scaffolding and intent — most of the moving parts haven't been built yet.
The bottleneck of an operator-builder is rarely the writing of code — it is the supervising of code. Sitting at the keyboard while an agent works. Watching it succeed. Watching it stall. Pulling it back when it veers.
Cerebrus is the speculative answer to that bottleneck. You text a spec to Nova on Telegram. Opus expands it into something structured. You glance and approve. From that point on, you don't have to be there. A queued task gets picked up by a worker, given the spec and the codebase context, and run to completion in its own workspace. When it finishes, a pull request shows up — already self-reviewed — and lands back in your inbox for one final yes or no.
That is the destination. Today most of those words are aspirations on a whiteboard.
Cerebrus is the planned execution plane for HPFHQ's autonomous CC Pipeline. HPFHQ holds the control plane: a Telegram /spec command pipes user intent through Opus into a structured spec, which lands in cc_specs after operator approval and gets queued in cc_queue. Cerebrus would poll that queue, spawn claude -p against a sandboxed worktree with the spec and the relevant CLAUDE.md as context, run a build + reviewer pass, then open a pull request on hpf-command-center when the gates are green.
Status is honest: the spec builder and queue tables exist in HPFHQ today. The execution side — runner daemon, reviewer agent, context checker, GitHub Action or local launchd worker — is scaffold-only. The repo lives at ~/Code/hpf-sandbox/, intentionally outside HPFHQ so a runaway build can't touch the source plane.
The reason it exists as a category, not yet as code, is that the rest of the stack has to mature first. Sentinel must be reliable enough to catch hallucinated changes. Pathfinder must surface the right context for any spec. Compass must produce specs that are actually well-shaped. Once those are sharp, Cerebrus becomes the layer where they all converge.