Flows
The unit of routing: a task, paired with the model, effort, and playbook it should run with.
A flow is the core object in Verybear. It pairs a task ("review pull request," "draft customer reply," "reconcile ledger to bank") with everything that task should run with: a model, an effort level, a playbook, and, optionally, a breakdown into subagents.
Requests are matched to flows by what the person is trying to do, not by exact wording. "review PR 1182" and "look over my branch before I open the PR" both match the same flow, because they're the same task described two different ways.
What's inside a flow
| Field | Meaning |
|---|---|
| model | Which model runs the task: sonnet, opus, gpt, gpt-mini, gemini, or a local model. |
| effort | low, medium, or high: how much the model should reason before answering. |
| playbook | The way-of-working instruction injected before the model sees the request. |
| subagents | Optional breakdown for tasks with real steps: plan, implement, verify. |
| examples | Phrasings used to match real requests to this flow. |
Status and versioning
A flow is active, draft, or paused. Every edit creates a new version, so you can see exactly what changed and when, and, on Business and Enterprise plans, stage that version to one team before it syncs everywhere.