Local-first · Multi-agent · Governed
HYVECODE is a governed workspace where people and agents plan, build, review, approve, test, and release — with escrowed authority, durable evidence, and a release gate that stays honestly locked until every blocker clears.
Run the full check before this ships to Bravo Team.
The doctrine
An agent's word is not evidence. In HYVECODE, every claim is tied to a command and its output, every authority is written down in plain language, and a human holds the release.
Agents report actions taken and results, not intentions. A run closes with a verdict — never a vibe. Every line in a run is a real command and its real output.
unit_tests(cart) → 42/42 passinggrep_scan(spec) → 2 flags foundAgents hold exactly what they're granted, written in plain language and visible to everyone: read & verify only, draft & format, no deploy. Nothing implicit, nothing admin-shaped.
warden — read & verify onlyforge — draft & format, no deployThe release gate stays honestly disabled until every real blocker clears. Failed and pending items are never hidden to make the list look cleaner — that's the point.
release gate → 2/3 passing · 1 blockerbutton: lockedOnce decided, a decision stays visible as text — who decided, when, and what the evidence showed. Approvals don't vanish into state; they become history you can grep.
approved · mina cho · 3:04 PMheld · needs privacy reviewThe workspace
A shared queue where work moves through proposal, verification, approval, execution, and release. People and agents sit in the same hive, under the same rules.
Ship Checkout Revamp v2 · CHK-214 → apply promo codes
Add promo-code application at cart with server-side validation — no client-only discount math.
WWarden · verification trace
@@ -18,6 +18,9 @@ const [code, setCode] = useState("");+ const [error, setError] = useState<string|null>(null); async function apply() {- const ok = validateLocally(code);+ const ok = await validateOnServer(code);
chk-214bill-71chk-198bill-88Release gate · checkout v2
The button stays honestly disabled until every real blocker clears. Nothing is hidden to make the list look cleaner.
Agents in the hive
Each agent carries a plain-language grant of what it may do, a named model, and a budget you set. Presence, spend, and scope are always visible — the same way a teammate's would be.
Latest run · chk-214
chk-198bill-88Bring an agent into the hive with a named model, a dollar budget, and a scope a human can read in one sentence.
Local-first
HYVE is a local-first execution environment. The hive — people, agents, queues, approvals, and durable workflows — lives on your machine, alongside your repo and your keys. Model calls are metered per agent, per exact model id.
Questions, answered plainly
HYVECODE is HYVE's primary product: a governed workspace where people and agents plan, build, review, approve, test, and release software together. HYVE is the underlying local-first execution environment — shared queues, approvals, model routing, and durable workflows.
Only what its escrow says. A verification agent might hold read & verify only; a build agent draft & format, no deploy. Scopes are written in plain language, visible to everyone, and revocable at any point.
A person. Agents run the checks and report results — 42/42 passing, contrast AA, grep sweeps clean — but the release gate stays disabled until every real blocker clears, and a human makes the call. The decision is recorded with a name and a time.
Each agent names its exact model id — for example claude-sonnet-4-6 — and carries a dollar budget you set. Spend is metered and visible per agent, the same way task progress is.
The hive runs on your machine: your repo, your keys, your workflow state. Agents coordinate through the workspace — shared queues, approvals, and a durable timeline — rather than living inside someone else's cloud project.
Clean to ship
Bring your repo, invite your people, escrow your agents. First run verified before you finish your coffee.