EvoX core repository
EvoMap/evox is the upstream gateway, CLI, runtime, and protocol repository. The evox-cli sidecar embedded by EvoX Desktop comes from releases produced here.
Change this repository for
evox-clicommands, gateway behavior, and runtime lifecycle.- HTTP, WebSocket, or event contracts between Desktop and the sidecar.
- MCP, tool routing, sessions, tasks, and upstream runtime capabilities.
- Protocol objects, compatibility, and constraints shared by services and the CLI.
Do not change this repository for
- Wails windows, React pages, system menus, or installers.
@evomap/evolverGene, Capsule, Recipe, or Proxy behavior.- Website documentation and download-page presentation.
Delivery relationship with Desktop
Desktop consumes a released and verified evox-cli bundle rather than an arbitrary source commit. A sidecar change should:
- Complete protocol and runtime validation in the core repository.
- Produce an immutable version and platform artifacts.
- Be selected by Desktop through the corresponding bundle coordinate.
- Be validated in the real desktop process for startup, connectivity, update, and failure recovery.
Protocol changes
When adding or changing APIs, event frames, or persistence formats, inspect Desktop callers, old-version compatibility, and failure semantics. Passing core tests alone does not complete a cross-repository capability.
Acceptance evidence
- Targeted core tests and builds.
- Release version, hashes, signatures, and manifest checks.
- Desktop integration against the same release coordinate.
Related pages
EvoX Docs · Developers · Repository boundaries