Bleeps and Bloops
Bleeps runs the crew.Bloops merges, then learns.
Bleeps is the doer, built for the Orca agent harness. Bleeps runs the crew and gets the work done. Bloops is the agent that merges pull requests through a script and studies each run so every agent's skills improve. You use it on your own projects. You file the issue and steer, and you promote develop to main.
Bleeps, runs the crew
Bloops, merges and improves
In short
- Doer
- Bleeps
- Merges
- Bloops
- Harness
- Orca
- Lands on
- develop
- Main
- You promote it
Two ways in
- NewStart a new projectCreate the repository, the branches, and the files the line expects.Start
- ExistingAdd Bleeps to an existing projectKeep the repository you have. Add develop, the router, and the gates.Start
- InA ticketA GitHub issue, from you or from Chip.
- CrewBleepsRuns the crew. You steer.
- MergeBloopsMerges to develop, then studies the run.
Phase 1. The shared orca.yaml is in the repo. The home server is not running the factory yet. scripts/merge-pr checks the gates and does not turn on GitHub auto-merge. That setting is still an open question.
From an issue to develop
This is the line, from a GitHub issue to a merge on develop. The day-to-day page walks each step.
Step Gate Holds
1. A GitHub issue
You file an issue, or Chip files one. That issue is the ticket.
2. Spec and tasks
Beep writes spec.md in specs/<issue>-<slug>/, and design.md only when the approach is the risky part. tasks.md is the checklist, and it includes the tests.
3. Build in an Orca worktree
Buzz builds, tests, and fixes in an isolated worktree, with a round limit. Blip writes the tests. A guardrail change waits for you.
4. Independent verify
Echo reads the work and writes verify.md. Echo is read-only, does not share the builder's context, and does not edit.
Gate: Ready to ship?
The verdict has to be “Ready to ship”. That is the verdict that opens a pull request.
Holds. Any other verdict stops the line before a pull request.
5. Pull request and review
The pull request targets develop. CodeRabbit, optionally Devin, and Claude Code review it. Grok Bot watches the queue, failing CI, and review nudges.
Gate: All clear?
Tests and the other required checks are green, verify says Ready to ship, reviews have no blocking findings, and a guardrail change has your sign-off.
Holds. A failed gate leaves the work on the branch.
6. Merge to develop
When the gates pass, Bloops reports the merge through scripts/merge-pr, then studies the run. The script does not turn on GitHub auto-merge. That setting is still an open question.
7. You promote main
You merge develop into main. Bleeps never touches main.
It also goes looking
Chip patrols the project on a schedule: failing tests, CI breaks, lint and type errors, dependency advisories, and friction-log items. Chip files an issue and the same crew takes it through the line, with the same sign-off on guardrails.
A project turns the patrol on or off in orca.project.yaml. Meet the crew, including how the switch works.
Bleeps stops and asks
Five areas wait for you before they change, and again before they merge. Everything else can move once the gates pass.
- Auth
- Billing
- Payments
- Data deletion
- Migrations