What is built

Built means merged and working. Planned and Direction items come from designs the owner has approved and are not shipped. The list is regenerated from progress.json by a script.

List built on 2026-11-12.

Built

• The package layout, import rules, budgets and pipeline, enforced by ordinary Go tests.
• The append-only event log with database triggers that refuse updates and deletes, and the pure decision core.
• Webhook intake that verifies, dedupes and records each delivery.
• Four ports, each behind a small interface with a fake: Linear for the tracker, GitHub for the forge, OpenRouter for the model provider and a process runtime for the agent.
• Shadow mode: the runner records the orders the bridge would give and executes none.
• The order executor, off by default: an owner turns on one effect at a time, each with one allowed ticket.
• The ops pages, helm controls, accounts, service tokens and an MCP server for coding agents.
• The base roles embedded in the binary, with install and project layers.
• The skiff image assembler and the seat loop that claims one run, runs the agent and reports.
• Working subcommands: backfill, check, demo, helm, inspect, mcp, migrate, roles, seats, sentry, serve, skiff, users, verify and version.
• The first run guide, from the artifact to a running Muster in shadow mode.

In progress

• The bosun, plan, tally and ticket subcommands print "not implemented" and exit with status 2 today.

Planned

• A request quota for each decision class, instead of one budget for each client.
• Cleanup and seat release effects in the executor.

Direction

• Pluggable ports: one contract for every port, a conformance suite run against every adapter and fake, and a second forge adapter, Gitea, as the proof.
• Webhooks with API fallback: each port that receives vendor events set to webhook, poll or auto, switching to polling when a webhook goes quiet, settable at any time.
• A secrets port, with files as the default store and Vault as the first remote store, rotation without a restart and per consumer provider keys.
• Pluggable skiff backends: several backends live at once, local hosts and Kubernetes first, and a driver protocol that adds a cloud with no Muster code.
• The merge class and the other decision classes taken from shadow to live, one flag each, with a read-back event before a ticket closes.
• A studio for roles and rulesets, compiled into reviewed pull requests, with roles that extend the base roles.
• Health and meter based gating: CI and queue meters by slice, with thresholds that notify, open a ticket, hold or brake a slice.
• Licensing: Apache 2.0 stays, with a contributor agreement, a trademark policy and a licence check on dependencies.