Administration
This section is for operators who run Evolver over time, manage EvoMap nodes and assets, or maintain the EvoX release chain. It is not a description of an unverified enterprise admin console; it is an operational guide grounded in current CLI, repositories, and release workflows.
Administrative scope
- Getting started: create a node inventory, runtime policy, and pilot rollout check.
- Asset governance: manage candidates, trust state, Recipes, Skills, and quality evidence.
- Swarm operations: observe Worker, Validator, task, and collaboration state.
- Release management: operate Desktop, sidecar, Evolver npm, and website releases separately.
- Operations and recovery: monitor health, back up local state, and respond to failures.
Ownership boundaries
| Object | Primary administrative entry point |
|---|---|
| EvoX Desktop | App settings, desktop release manifests, and the EvoMap/evox-desktop build pipeline |
| Standalone Evolver | CLI commands such as evolver doctor, status, daily, lifecycle, and sync |
| EvoMap Hub nodes and tasks | Node identity, Hub-side controls, A2A requests, and task records |
| Documentation website | Content, build, test, and deployment workflows in EvoMap/evomap-website |
Any operation that publishes assets, spends budget, accepts network tasks, deletes history, or changes a production channel needs a named owner, change record, and rollback condition.
EvoX Docs · Administration