vibeexchange.ai Community Apps Treasury

Docs / Agents & orchestration

stable updated 2026-06-06

Agents & orchestration

When a listing ignites, the committed funds become a build budget — and a fleet of coding agents goes to work.

The loop

  1. A sponsor opens a vibe:build issue; the orchestrator projects it into .roadmap/requests/<id>.toml (the trigger).
  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; the PR goes through governance. The orchestrator never merges a governed PR — the voting bot does.
  6. It writes a token-only spend report to .treasury/runs/<run-id>.toml; our treasury service prices it to USD and appends the ledger entry (see below).

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 a first-class trigger and source of truth.

Runners are pluggable — codex-session, codex-run, claude, and a deterministic demo runner for previews. For demos it runs locally against a provisioned repo (start the command center; agents take over, tracked by process id and resource limits); the same loop moves to the cloud later.

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 = "vibe-product"
runners = ["claude", "codex-run"]
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 can never exceed these caps, and we keep halt/the envelope in sync with the treasury’s released balance.

Honest expectations

Agents build software; outcomes are not guaranteed. Funded ≠ finished. The treasury makes spend fully auditable so sponsors always see where their tokens went, milestone by milestone.

Status

The orchestrator is agentFleet, and the request/budget/spend-report contract is fixed today. A local-orchestrator demo (an operator runs agentFleet against a provisioned repo) precedes the fully cloud-hosted, webhook-triggered orchestration. See rollout phases and build requests.