Teams (durable runtime)

naive teams is the CLI for the durable runtime. A team is a declared team({ runtime, lead, agents, edges, brain }) in your naive.config.ts; this command group addresses one of those teams for one tenant and drives it.

What works depends on which runtime the tenant is on, and every one of the 28 subcommands addresses a mounted route. 19 of them return real rows for a durable tenant. 12 do for a hermes tenant. The other 9 answer 501 not_configured and name the missing dependency — for the runtime that tenant is actually on. That split is measured against this build, not aspirational: ci/runtime-surface-counts.test.ts derives it from routes/teams.ts and fails the build if this sentence disagrees.Which of the two you get is decided by naive up, not by this command group. A tenant lands on the durable runtime when a teams: block declares runtime.durable(...) and the operator exports NAIVE_DURABLE_CREDENTIAL_<TEAM> — that is the one production path to registerVettaRuntime(), and it refuses any tenant that already has a live Hermes container. naive teams migrate remains one of the 9 that refuse: registering overwrites the tenant’s legacy coordinates and the way back is not symmetric, so moving an existing tenant stays an operator act rather than a subcommand. Every tenant naive up did not place answers provider: "hermes" and gets the 12.Run naive teams plan <team> --tenant <id> to see which runtime a tenant is on. Every response carries provider; every refusal carries error.details.runtime.

The addressing tuple

The durable runtime addresses work as (company, tenant, team).

company comes from your API key. You never pass it.
team is the first positional argument — the key you gave the team in naive.config.ts.
tenant is --tenant <tenant-user-id>, and it is required on every subcommand except list. There is no default and no fallback.

--tenant @self is the one shorthand. It resolves to the subject you selected with naive use <id> — not to a server-side default. If nothing is selected it is an error:

naive teams board support --tenant tu_8f21     # explicit
naive use tu_8f21 && naive teams board support --tenant @self
naive teams board support                      # error: --tenant is required. There is no default.

That refusal is deliberate. A defaulted tenant on a multi-tenant board is how one customer’s work ends up in another customer’s ledger.

Subcommands

Every subcommand takes <team> as its first argument and --tenant (except list). Both verdict columns are the measured ones. A single “does it work” column could not be true — the answer depends on which runtime the tenant is on, and provider on every response tells you which you are reading.

Reading the board

Command	What it does	durable tenant	hermes tenant
`naive teams list`	List the declared teams	501	501
`naive teams show <team>`	The team/tenant header — status, runtime, counts	serves	serves
`naive teams plan <team>`	The honesty report: digests, fence, caps, attestation parity	serves	serves
`naive teams roster <team>`	The declared agents, and with `--edges` the edges between them	serves	serves
`naive teams board <team>`	The board, as columns	serves	serves
`naive teams tasks <team>`	The same board, as a flat task list	serves	serves
`naive teams task <team> <id>`	One card	serves	serves
`naive teams events <team>`	The team’s event log	serves	serves
`naive teams runs <team>`	The team’s runs	serves	serves
`naive teams cost <team>`	What the team spent (`--by`, `--period`)	serves	serves
`naive teams approvals <team>`	Approvals this team is waiting on	serves	serves
`naive teams sessions <team>`	The team’s sessions	501	501
`naive teams read <team> <channel>`	Read one session channel	501	501
`naive teams effects <team>`	Outstanding effects	501	501
`naive teams diagnose <team>`	Diagnostics for a team that is misbehaving	serves	serves
`naive teams watch <team> --run <id>`	The run transcript, NDJSON, resumable	serves	501

Changing something

Command	What it does	durable tenant	hermes tenant
`naive teams decide <team> <id>`	Allow or deny one approval (`--allow` / `--deny`)	serves	serves
`naive teams submit <team> "<goal>"`	The work verb	serves	501
`naive teams say <team> "<text>"`	Say something into a team session	serves	501
`naive teams unblock <team> <id>`	Unblock a card	serves	501
`naive teams settle <team> <id>`	Settle an effect — `--done` / `--compensate` / `--reject`	501	501
`naive teams schedule <team> <cron> "<goal>"`	Schedule recurring work	serves	501
`naive teams unschedule <team> <id>`	Remove a schedule	serves	501
`naive teams apply <team> --expected-digest <d>`	Record that an operator applied this exact manifest digest; refuses a stale one. `naive teams plan` prints the digest to pass	501	501
`naive teams model <team> <modelId>`	Change the model a team runs on	501	501
`naive teams stop <team>`	Stop the team’s dispatch loop — a pause, not a decommission: cards keep their leases, and the answer carries `in_flight` for attempts already handed to a member	serves	501
`naive teams migrate <team>`	Move this tenant onto the durable runtime — there is no path to it from this command group. Placement happens in `naive up`, from a declared `runtime.durable(...)` team plus an out-of-band `NAIVE_DURABLE_CREDENTIAL_<TEAM>`	501	501
`naive teams rollback <team>`	Move this tenant back off it — destroys the workspace	501	501

Submit is the one work verb

There is exactly one way to give a team work, and it is submit. It carries the same name on every surface that offers it:

Surface	Form
CLI	`naive teams submit <team> "<goal>" --tenant <tu>`
REST	`POST /v1/teams/{team}/tenants/{tenantUserId}/submit`
Governance	ActionId `teams.submit`
MCP	not exposed — the MCP server registers `naive_teams_status`, `naive_teams_board`, `naive_teams_run`, `naive_teams_comment` and `naive_teams_unblock`, and no submit tool

naive teams submit support "refund the duplicate charge on invoice 4471" --tenant tu_8f21
naive teams submit support "$(cat brief.md)" --tenant tu_8f21 --brief ./brief.md
naive teams submit support "rerun the audit" --tenant tu_8f21 --task card_19 --parent run_88

--brief <file> (or --brief - for stdin) exists because prose on argv is mangled by every shell that touches it. Use it for anything with quotes, newlines or $.

submit answers 501 not_configured on this build. The refusal names three missing dependencies: there is no durable dispatcher seam to hand a goal to (forwarding to the legacy Hermes dispatcher would open a second write path into a frozen runtime), manifest_digest and required_attestations have no storage, and the idempotency middleware is an in-process Map with no cross-replica sharing — so --idempotency-key cannot be honoured honestly.To send work today, use the legacy surface: naive tasks create or naive ceo run. Both still work and are not going away.

The write fence

Eleven subcommands are fenced — they pass through the manifest write fence and are evaluated under a governance ActionId. The CLI prints which one in hints:

`submit` passes through the write fence (ActionId teams.submit).

Fenced: submit, say, unblock, decide, settle, schedule, unschedule, model, stop, migrate, rollback. Reads are never fenced. decide is the fenced write that works on this build:

naive teams approvals support --tenant tu_8f21 --status pending
naive teams decide support apr_31f --tenant tu_8f21 --allow --because "verified with the customer"
naive teams decide support apr_31f --tenant tu_8f21 --deny  --because "outside the refund window"

--because is a required option on seven subcommands — unblock, decide, settle, model, stop, migrate and rollback. A destructive or overriding act with no recorded reason is a row nobody can audit later, so the command line refuses it rather than review catching it. (watch has one other required option: --run <id>.)

Exit codes

naive teams is the only command group with exit codes beyond 0 and 1.

Exit	When	How to get it
`0`	Success	default
`1`	The command failed	default
`2`	`plan` found a diff	`naive teams plan <team> --tenant <tu> --detailed-exitcode`
`3`	At least one card is `unverified`	`--fail-on-unverified` on `tasks` / `task`, `--fail-on-terminal` on `watch`

Exit 3 exists because unverified is a third terminal state, not a flavour of success. A card whose claims were never attested has finished without having been shown to be right. Nothing exits 3 unless you ask for it.

--fail-on-unverified is a hermes check, and on a durable tenant exit 0 does not mean “attested”.unverified is written by naive’s own completion adjudicator onto its task mirror. A durable tenant’s board is not that mirror — it is the runtime’s own board, translated — and the runtime’s task states are a closed set (todo ready doing review done blocked) with no unverified among them. The flag therefore cannot fire there. It is not finding nothing; it is unable to find anything.naive teams tasks --fail-on-unverified prints a warning on stderr when the board it read came back with provider: "durable", so a CI job does not silently inherit a check that cannot fail. stdout is untouched — still exactly one JSON document.On that runtime the equivalent signal is attempts: a rejected completion is retried rather than recorded, so attempts > 1 on a terminal card means the reviewer turned at least one completion down. See Board & cards.--fail-on-terminal on watch keeps a real reach on both runtimes, but only failed of its three statuses occurs on the durable one.

Exit 2 is opt-in for the same reason terraform made it opt-in: reusing exit 1 for “changes exist” is indistinguishable from a real error in a CI script.

What this build does not serve yet

The 15 subcommands marked 501 above are not 404s and not stubs. Each addresses a mounted route that authorises your request, then refuses with 501 not_configured and an error.details.missing array naming every absent dependency by its real name. For example:

{
  "success": false,
  "error": {
    "code": "not_configured",
    "message": "Team enumeration is not available in this build.",
    "details": {
      "missing": [
        "team storage: a declared team's name lives in `agents.metadata` under a retired key…",
        "durable runtime seam: no manifest, digest or fence storage exists…"
      ]
    }
  }
}

This is deliberate and it is the reason naive teams list does not return {"items": []}. An empty list is a claim about your company — that you declared no teams. A 501 is a claim about this build. They are not the same sentence and a script cannot tell them apart.

If a naive teams command instead reports that the route is absent rather than the team, you are talking to an API build where /v1/teams is not mounted at all. The CLI distinguishes the two: an unmounted path produces the API catch-all’s resource_not_found with a literal Cannot GET /path message, and the CLI rewrites that into a message naming the missing mount rather than sending you to check your team name.

Coming from the legacy runtime

Legacy	Durable runtime
`naive ceo run` / `ceo message`	`naive teams say` · `show` · `runs` · `watch`
`naive tasks create`	`naive teams submit`
`naive tasks list` / `show`	`naive teams board` · `tasks` · `task`
`naive tasks unblock`	`naive teams unblock`
`naive objectives create`	`naive teams submit --task <id>`
`naive employees list`	`naive teams roster`
`naive cron create` · `naive loops create`	`naive teams schedule`
`naive memory add`	`naive brain remember`

Four legacy capabilities have no replacement, and that is by design rather than an oversight — see each page for the recorded reason: tasks complete, tasks dispatch, tasks run, the employees provisioning verbs (hire / fire / configure), and cron pause / cron resume.

naive brain — the company brain a team reads and writes
naive approvals — the company-wide approval queue
naive use — selecting the subject --tenant @self resolves to

CLI Reference

Durable runtime

Multi-tenant

Legacy orchestration (deprecated)

Primitives

Teams (durable runtime)

The addressing tuple

Subcommands

Reading the board

Changing something

Submit is the one work verb

The write fence

Exit codes

What this build does not serve yet

Coming from the legacy runtime

​The addressing tuple

​Subcommands

​Reading the board

​Changing something

​Submit is the one work verb

​The write fence

​Exit codes

​What this build does not serve yet

​Coming from the legacy runtime

​Related

The addressing tuple

Subcommands

Reading the board

Changing something

Submit is the one work verb

The write fence

Exit codes

What this build does not serve yet

Coming from the legacy runtime

Related