Aetherin Agent Studio — roadmap
Milestone plan for building Aetherin Agent Studio (see `product-blueprint.md` (product-blueprint.md) for the spec and `project-overview.md` (project-overview.md) for the ecosystem inventory).
Each milestone lists deliverables, exit criteria, the surfaces it touches (registry names only), and its contract dependencies (aetherin-stack/common/openapi.yaml v0.2.0). Contract operations marked *(planned)* must exist before a milestone is considered complete.
M0 — Specification and contracts
Goal: one consistent, buildable spec and an agreed integration surface.
Deliverables:
- Canonical `product-blueprint.md` (product-blueprint.md): definition, scope,
surfaces/pages, data model, contract mapping.
- This roadmap.
- Cross-checked surface names against
registry.jsand03-status.md. - Proposal text for the Studio surface registration and the contract additions in
blueprint §6.2 (product-blueprint.md#62-studio-additions-required-propose-for-a-future-contract-revision).
Exit criteria:
- All internal markdown links resolve.
- Every surface referenced uses a registry name; the only new name (**Agent
Studio**, id studio) is explicitly marked proposed.
aetherin-agent-studiovsaetherin-agentis unambiguous everywhere.
Touches: none at runtime. Contract deps: none (read-only review of v0.2.0).
M1 — Intake and planning (read-only)
Goal: turn a brief, a repo, and assets into a reviewable plan without writing to any repository.
Deliverables:
- Studio surface registered (
studio→ Agent Studio, statusplanned) and a
matching status board row.
- Brief intake and context assembly (repo snapshot, uploaded assets).
- Plan generation: product spec, architecture, milestones, tasks.
- Account center session auth and scoped keys (read paths).
Exit criteria:
- A user can sign in via the Account center session, submit a brief with an
optional repo link, and receive a deterministic plan.
- No Git writes occur; all outputs are read-only artifacts.
- Graceful local-first fallback when backend routes are absent.
Touches: Agent Studio (new), Account center, Gateway, Portal. Contract deps: /v1/account/* *(planned)*, /v1/keys *(planned)*, /v1/models *(live)*, /v1/chat/completions *(live)*.
M2 — Design and scaffold (branch-safe)
Goal: produce design direction and a scaffolded project on a branch, behind approval.
Deliverables:
- Design direction, tokens, and screens aligned to the Design system.
- Template scaffolding and starter generation.
- GitHub branch/PR creation with protected-work safeguards and an approval gate.
Exit criteria:
- A project can be scaffolded onto a new branch and opened as a PR without touching
protected branches.
- Generated UI uses shared
ax-*tokens/components. - Every write is preceded by an Approval record.
Touches: Agent Studio, Design system, Preset studio. Contract deps: /v1/keys *(planned)*, /v1/auth/login *(planned)*, plus the proposed Studio project/plan routes.
M3 — Full operating loop
Goal: phased implementation, validation, and audited execution.
Deliverables:
- Multi-agent execution with dependency management.
- MCP-hub-backed tools (
tools/list,tools/call). - Validation pipeline: lint / build / test / audit orchestration.
- Run log, usage accounting, and audit trail.
Exit criteria:
- A project advances through build → validate with defects fed back as tasks.
- Agent runs are visible with token usage sourced from the contract usage routes.
- Failures block release rather than silently shipping.
Touches: Agent Studio, MCP hub, Gateway, Streamproof. Contract deps: /v1/usage, /v1/usage/daily, /v1/usage/providers *(planned)*, /v1/providers* *(planned)*.
M4 — Release, scale, and commercialization
Goal: release readiness, multi-tenant operation, and ecosystem hooks.
Deliverables:
- Deploy targets and CI/CD setup via Integration records.
- Release artifacts, notes, and human release gates.
- Per-user/team workspaces aligned to
plan/seats with billing/usage via **Account
center**.
- Preset-driven Studio setups and plugin entry points.
Exit criteria:
- A project can be released to a chosen target with an approval record and a
rollback/fallback story.
- Multi-tenant boundaries are enforced and visible in the Admin console.
- Usage is metered end-to-end.
Touches: Agent Studio, Account center, Admin console, Preset studio, Plugins, Gateway. Contract deps: all usage/keys/providers routes *(planned)* plus the proposed Studio route families.
Success bar
The finished product should feel like a digital studio, not a code generator: an underspecified idea becomes a launch-ready strategic foundation plus a functioning, validated implementation path — with the human in control at every gate.