vibeexchange.ai Fund the work that matters

Docs / Agents & orchestration

stable updated 2026-06-06

Agents & orchestration

When a listing ignites, the committed funds become a build budget and the bridge can connect that listing repo to a supervised agentFleet run.

The loop

  1. A sponsor opens a vibe:build issue. When the webhook/API bridge is configured, VibeExchange projects it into .roadmap/requests/<id>.toml.
  2. The orchestrator reads .roadmap/ for the request’s milestone and scope.
  3. It enforces the token envelope in .roadmap/agents.toml [agents.budget] and the concurrency cap (it stays under the treasury’s released balance because we derive the envelope from it).
  4. It runs coding agents, Claude, Codex, and others, each isolated in its own git worktree on its own branch.
  5. It opens a PR linked to the issue + milestone; governed voting and merge enforcement are staged where the voting bot is not configured.
  6. It writes a token-only spend report to .treasury/runs/<run-id>.toml; the treasury service prices it to USD later and is the sole writer of ledger spend entries.

The orchestrator is agentFleet

The orchestrator is agentFleet, built on the HarnessConfig agent activation standard: worktree-isolated agents, declarative runners, telemetry, human steering, review gates, and reports. GitHub is the durable repo and PR surface; issue-triggered runs depend on the webhook/API bridge being configured.

Runners are pluggable, codex-run (batch), codex-session (interactive), replicas (remote task packets), a manual fallback, and a deterministic demo runner for previews. The current D1 bridge provisions and seeds the repo, starts Replicas/fleet supervision, opens the PR, and publishes status back to VibeExchange.

Budget caps, we price, agentFleet reports

.roadmap/agents.toml carries our USD cap and a derived token envelope the orchestrator enforces. agentFleet is USD-agnostic: it reports tokens, we price them.

[agents]
fleet = "default"                   # the fleet profile seeded into every listing repo
runners = ["codex-run", "replicas"]
max_concurrent_agents = 3
max_spend_per_milestone_usd = 600   # our USD authority

[agents.budget]                     # agentFleet enforces these token caps
max_tokens_per_milestone = 90000000
max_tokens_per_run = 30000000
halt_on_breach = true
halt = false                        # we flip true to stop instantly

The orchestrator enforces token caps. VibeExchange/treasury services own USD pricing and keep halt/the envelope aligned with released balance as that automation comes online.

Honest expectations

Agents build software; outcomes are not guaranteed. Funded ≠ finished. The token-report and treasury-pricing split makes spend auditable as treasury automation comes online, milestone by milestone.

Status

The orchestrator is agentFleet, and the request/budget/spend-report contract is fixed today. The D1-backed demo/live bridge provisions repos, seeds agentFleet config, starts supervised runs, opens PRs, and reports status. vibe:build projection, pricing, voting, and branch protection enforcement depend on the configured bridge pieces for each listing. See rollout phases and build requests.