Keeper
A human in charge. You own a plan and the agents that carry it out, and you stay the one who decides.
Overlapping edits, the same work done twice, pull requests that conflict, and nobody who can say who is on what. Waggle is a hive for many people and their agent teams on one repository. Each keeper (a human in charge) talks with a queen (an agent that plans the work). She writes each task a lane, called a claim, and the guard fails a merge that leaves it.
The guard works today. The rest of the hive is on the roadmap, and each part says which it is.
A forager (the coding agent doing the work) opens a pull request. The guard, our merge check, reads the lease (the directories the task may change) and tests every commit against it. One commit outside the lease blocks the merge.
Waggle talks in bees on purpose. Every role is a plain job underneath, so here is each one in a line. Most of the work comes from the agent team: keepers talk with their queens, and the queens open the GitHub issues and write the claims. A person can also write an issue.
A human in charge. You own a plan and the agents that carry it out, and you stay the one who decides.
An agent you talk with. She plans the work, opens the issue and writes the claim. She does not write feature code.
The coding agent doing the work. It goes out, changes the files and brings a pull request back. It never writes its own claim.
The gate that checks the lease. It reads every commit and says pass or must-fix. Built
A worker that implements a task inside its claim. waggle dispatch runs one today. Built
A planner that searches ahead and writes the task brief. The instructions ship, but Waggle does not run scouts for you yet. Coming soon
The whole hive, built and coming · Glossary of every bee word
Two foragers change the same files. One overwrites the other, or the pull requests will not merge.
Nothing records that a task is already taken, so a second agent starts it and the effort is wasted.
Branches pile up. A keeper has to reconstruct the plan from the diff.
A record of one task: the directories it may change and the branches its pull request may come from. You talk with your queen and she writes the claim. The forager doing the work never writes its own. A queen opening issues straight from your conversation is Coming soon; a person can also write an issue.Claims and leases
Those directories. That is the lane the forager is supposed to stay inside, like a bee on its own comb.
A GitHub merge check, verify-leases-and-tiers. It fails a pull request whose commits change a path outside the lease, or whose claim does not name that pull request's branch. It checks every commit, not only the final diff.The gate spec
A keeper is the person who works with the queen. Paths you list as protected still need an approver's approval. Control files such as workflows fail no matter what the claim says. Waggle does not run your foragers; it guards the hive they work in.Protected paths
Teams, and open-source projects, where more than one keeper runs an agent team on the same repository. Today the gate holds the line for all of them. Next come guidance for many keepers on one repo, thenhoney: a contributor's standing, earned from merged work that lasts, with Nectar (reputation) and Quorum (voting on priorities). Honey is Roadmap. If that sounds like your hive, the quick start is the place to begin.
It does not schedule or run foragers, and it is not a sandbox. It binds only on PRs that must pass the check, an admin bypass merges without it, and the required check can be forged by a workflow or token with the right permissions. The limits are written down, with the tests that show them, inthe gate spec.
Waggle is pre-1.0 and supports GitHub only. The spec describes what the code does today, and the recipes have not been run end to end with each tool.