# Specs

What nixos-router should become, beyond what exists. `PLAN.md` records decisions and what is done; this file
lists wanted features. Nothing here is started.

## Later

### Programmatic access

- **REST API** for everything the web UI does (settings, apply/confirm, status, metrics, updates), versioned and
  authenticated with tokens rather than the browser session. The web UI would use the same handlers.
- **GraphQL** on top of it, possibly: one query for the overview and for related settings.
- **MCP server**, so an assistant can read the router's state and propose or make changes (the same checks as the
  web UI: settings are validated, applied with commit-confirm rollback, secrets are never returned).
- To settle first: token scopes (read-only vs. change), audit log, and that changes still go through
  `settings.json` and `router-apply` rather than touching the live system.