VibeFlock: the principles
By Soumen Sarkar · October 2026
Move as one at agent speed. Nobody waits.
Every generation of builders inherits tools that change what's possible. Ours has inherited something new: tools that build alongside us. Today a single engineer directs a team of agents. A small group of people ships dozens of changes before lunch. The work has never moved this fast.
But speed alone is not progress. When everyone moves at once, the hardest part is no longer writing the code. It's making sure that what one of us builds, the rest of us can build on. A question that waits an hour now waits behind a hundred changes. A decision made in one session is lost to the next. And the cost isn't counted in minutes. It's counted in work done twice, and in trust spent.
So we have a choice to make about the kind of team we want to be. We can slow down to the speed of our conversations. Or we can do something harder, and better: build a way of working where context moves as fast as the code, where every person and every agent can rely on the work of every other.
Nature solved this long ago. A flock of starlings, thousands strong, turns in an instant and never collides. A school of fish moves as one body. Nobody leads them and nobody waits for orders. Each one watches its nearest neighbours: it heads where they're heading, it stays with the group, and it keeps its own space. Alignment comes from everyone reading the same signals at once, not from someone in charge.
That is VibeFlock. It is not a tool, and it is not a process. It is a promise we make to each other: that nobody will ever have to wait for us, and we will never have to wait for them. Seven principles hold that promise together.
The seven principles
- Keep moving: The work never waits, and neither do we.
- Build on what's coming: Unfinished work is a promise, and a promise can be built on.
- Fix forward: We don't guard the gate. We correct the course.
- Turn unknowns into calls: Nothing we don't know gets to stop us. We name our assumption, and we move.
- Answer it yourself: Look first. If the answer isn't there, assume it or decide it.
- Let the work speak: Our work explains itself, so nobody ever has to come and ask us.
- Decide by doing: Our decisions live in what we do, not in what we say.
1. Keep moving
The work never waits, and neither do we.
At the speed we now build, waiting is the most expensive thing a team can do. Not because people are slow, but because everything around them is fast. So we make a simple commitment: nobody stops the work to wait for anybody else. Not for an answer. Not for a review slot. Not for a teammate on the other side of the world to wake up. The work moves, and the context moves with it.
- People: You keep moving, and you trust your teammates to keep moving too.
- Agents: An agent finishes what it can with what it knows, and leaves the rest ready for whoever comes next.
- Campfyrr: Campfyrr brings the context to the work: what's changing, what was decided and what was assumed, at the very moment it's needed.
2. Build on what's coming
Unfinished work is a promise, and a promise can be built on.
We don't wait for each other to finish. When a teammate tells us what their work will become, we build toward it today, side by side. And when it lands, we see exactly how it turned out against the promise, and we adjust in minutes, together. Nobody's progress is held hostage by anybody else's.
- People: You say what your work will become, so others can build on it before it's done.
- Agents: An agent builds against the plan of work in progress, and adapts the moment that work lands.
- Campfyrr: Work in progress is visible where it lands, with its plan. When it finishes, everything built on it hears what landed and what changed.
3. Fix forward
We don't guard the gate. We correct the course.
No team that moves this fast will be perfect, and we don't pretend to be. What we can be is honest, quick and accountable. We catch our mistakes early, while they're small, and we fix them in the flow of the work instead of stopping the work out of fear of them. That isn't lowering the bar. That's how the bar gets raised, every single day.
- People: You fix what you find, where you find it, and you say why.
- Agents: An agent changes course the moment it learns it was wrong, and says what it changed.
- Campfyrr: Wrong assumptions and clashing decisions surface the moment they appear, with exactly what relied on them, so every fix stays small.
4. Turn unknowns into calls
Nothing we don't know gets to stop us. We name our assumption, and we move.
There will always be things we don't know. What defines us is what we do in that moment. We don't freeze, and we don't guess in silence. We make the best call we can, we say it plainly, and we keep going, confident that if we're wrong, someone who knows better will set it right without stopping anyone.
- People: You make the reasonable call, state it in a sentence, and carry on.
- Agents: An agent states its working assumption and keeps going, instead of stopping to ask.
- Campfyrr: Assumptions travel with the work, are settled from what the team already knows whenever possible, and are corrected without stopping anyone.
5. Answer it yourself
Look first. If the answer isn't there, assume it or decide it.
Every question we ask hands our progress to someone else's calendar. So before we ask, we look, because the answer is so often already written down. And if it isn't, we don't hand the moment away: we state our assumption, or we make the call that is ours to make. This isn't about working alone. It's about respecting each other's time enough never to spend it carelessly.
- People: You look first, then you decide. You never ask permission to make a call that's yours to make.
- Agents: An agent searches the team's record before anything else, and states its assumption when the record is silent.
- Campfyrr: Every decision, rule and handoff can be found by every agent, and briefs arrive before an agent would think to ask.
6. Let the work speak
Our work explains itself, so nobody ever has to come and ask us.
If a teammate has to stop and ask what we did, we haven't finished the job. The work isn't done when the code runs. It's done when the next person can pick it up without us: what it's for, what we decided, what we assumed, and what's left. That is how we take care of each other.
- People: You never have to stop to explain your work. It already explains itself.
- Agents: An agent leaves its reasons and its handoff with the work, every time it stops.
- Campfyrr: Handoffs write themselves when work stops, every change carries its reasons to its reviewer, and each day's work is told in plain words that nobody had to write.
7. Decide by doing
Our decisions live in what we do, not in what we say.
Decisions are not made in rooms we have to be invited into, or in documents written after the fact. They are made in the work, in the moment, with the reason spoken plainly, and they travel with the work to everyone it touches. A team's values aren't what it says. They're what it ships.
- People: You make the call in the work and say why in a sentence. That sentence is the record.
- Agents: An agent records every call it makes, with its reason, at the moment it makes it.
- Campfyrr: Decisions are captured with their reasons as the work happens, checked against the ones that stand, and handed to every agent that touches the same ground.
None of this is about doing more with less. It's about doing more, together.
A flock doesn't wait for a leader to turn. Neither do we. When nobody waits, everybody builds. When the work explains itself, trust grows. When every person and every agent can count on the work of every other, a small team can do something remarkable.
That is the promise of VibeFlock. It's the way we've chosen to work. And we believe it's the way the best teams will build from here.
Everything is derived from this
- Product: Every feature removes a reason for work to stop. If it adds a wait, a step, or a question, it doesn't ship.
- Words: We say assumption, not question; correct, not approve; picks up, not handed to; landed, not done-pending-review.
- Content: Every piece shows one principle at work today, at agent pace, with a concrete example. We write about how work is done now.
- Marketing: We promise outcomes the principles produce: less waiting, less rework, faster pick-up. We show the product doing it, never invented proof.
- Measures: We count waiting time, rework, pick-up time and late surprises. A number that doesn't move one of these isn't a measure we use.
The words we use
- VibeFlock: Building one product with a team of people and AI agents at agent pace, moving as one like a flock: context travels with the work, so nobody waits and nobody steers.
- Assumption: The best available answer to an unknown, stated and acted on, kept visible so anyone can correct it.
- Handoff: What unfinished work carries for whoever continues it: what's done, what's left, the next step, and what to watch out for.
- Area brief: What a person or agent is told the first time they touch a part of the code: what's changing there now, what was decided, what was tried.
- Work in progress: Work under way, shown with its plan, so others build on it rather than around it.
- Landed: Work that finished, with what it turned out to be compared with its plan.
- Reasons: What a change is for, the calls made in it, and what was assumed, attached to the change for whoever reviews it.
Read more
Each principle at length:
- Keep moving: work that never waits
- Build on what's coming: unfinished work is a promise
- Fix forward: correct the course, don't guard the gate
- Turn unknowns into calls: nothing we don't know gets to stop us
- Answer it yourself: look first, then decide
- Let the work speak: work that explains itself
- Decide by doing: our decisions live in what we do
Playbooks: VibeFlock in two minutes: connecting Claude, Claude Code and Codex · Instructing agents to state assumptions and keep going · Making a team's knowledge findable by every agent · Handoffs that write themselves · Working in parallel on dependent changes · Reviewing agent-made changes by their reasons · Recording decisions as agents work · Leading a team where everyone runs several agents · Measuring a team at agent pace: waiting, rework, pick-up time · Claude Code hooks for VibeFlock · Codex, Cursor and other MCP clients · Agent instructions for a never-blocked team
Scenarios: One feature, four people, twelve agents · A day of VibeFlock, minute by minute · Joining a codebase that changes 200 times a day · A weekend of agents, a Monday with nothing to catch up on · From idea to landed in one afternoon
Also: Answers · Glossary · Templates · Trust
Move as one at agent speed. Nobody waits. Add Campfyrr to Claude: it briefs every agent before it touches the code, keeps assumptions and handoffs where the team can see them, and never takes your code (what it keeps).