Product Surfaces

Build, Teammates, Rooms, Routines, Skill Studio, Activity, and Advanced → Runtime Extensions organize client navigation over one node. They are not independent backends, harnesses, or sources of truth. Approvals and resources are related node concerns, not extra brains.

Build

Status: planned. The complete user-facing ADE for projects, Workspaces, Sessions, terminals, Tasks, diffs, and artifacts. Headless primitives exist for project, workspace, receipt, and idle session records. Session start, turns, and the macOS live terminal remain source-implemented candidates. Desktop and mobile ADE parity is planned.

Teammates

Status: planned. Durable Agents with replaceable harness, model, and placement. ADR-013 is accepted. No public Agent surface is implemented.

Rooms

Status: planned. Durable human-Agent collaboration with explicit membership. A message is untrusted input. It is never an Approval, grant, receipt, or proof of an external effect.

Routines

Status: planned. Reusable binding from one immutable Skill entry point to policy, target, inputs, budgets, and at most one optional trigger. There is no standalone Schedule aggregate.

Skill Studio

Status: planned. Author, review, test, and version user-owned Skill revisions. Generated executable code cannot activate itself or run in the node. Recommended maia-cli and maia-orchestration Skill bundle sync is planned.

Activity

Status: planned. Durable events, receipts, outcomes, resource and cost observations, and audit projections. The local-v1 orchestration candidate is source-implemented and blocked. It is not an Activity product surface.

Advanced → Runtime Extensions

Status: planned. Higher-trust runtime-specific executable extensions, initially for Pi. Unsupported as a substitute for Skills. No public Runtime Extension surface is implemented.

Approvals

Status: planned. Privileged authorization required before a capability or effect may proceed. Distinct from a Question/reply or a DecisionGate. Not present in the installed command registry.

Resources

Status: planned as a product surface. Cooperative Skill-level admission and a user-facing resource view are not implemented. The macOS ProcessResourceManager and the compact node.status projection are source-implemented candidates: cooperative, not implemented as a release-gated surface, with no enabled Codex, Git, or turn consumer. Hard containment is not claimed.

Next action

Canonical behavior lives in Agents, Skills, Routines, and Rooms and orchestration. Use Getting started and the CLI notes for what the built executable actually exposes.