Repository boundaries

EvoX is not a single-repository product. Core runtime, desktop client, Evolver, and the website publish different deliverables. Documentation, code changes, and releases must return to the repository that owns the artifact.

Repository map

Repository	Primary responsibility	Does not own
`EvoMap/evox`	Upstream gateway, CLI, runtime, and protocol; produces `evox-cli`.	Desktop UI, installers, and npm Evolver.
`EvoMap/evox-desktop`	Wails desktop client, platform integration, installers, updates, and signing.	Upstream protocol definitions or Evolver asset semantics.
`EvoMap/evolver`	npm Evolver engine, CLI, Proxy, MCP, and GEP asset behavior.	Desktop shell and platform installers.
`EvoMap/evomap-website`	Public product pages, documentation, download-manifest consumption, and frontend acceptance.	Building or signing Desktop, `evox-cli`, or Evolver packages.

Choose where to change code

UI, system menus, browser panes, desktop updates, or installation experience: Desktop.
Gateway, sidecar API, runtime protocol, or evox-cli behavior: EvoX core.
Genes, Capsules, Recipes, Evolver CLI, Proxy, or MCP: Evolver.
Public copy, documentation routes, download pages, and manifest presentation: Website.

Cross-repository delivery

Split cross-repository work into independently accepted deliverables. For example, an upstream evox-cli change first produces a verifiable release in EvoMap/evox; Desktop then updates its sidecar coordinate and completes desktop acceptance; the website finally consumes the published manifest and updates documentation. A website mock does not prove that upstream or Desktop has shipped a capability.

Versions and evidence

Use release tags, manifests, package metadata, and repository tests as factual sources.
Do not infer “supported” from another repository's mock, screenshot, or planning document.
Documentation may describe a cross-repository dependency but must not present an unreleased dependency as currently available.

EvoX Docs · Developers · Repository boundaries

Repository map

Repository	Primary responsibility	Does not own
`EvoMap/evox`	Upstream gateway, CLI, runtime, and protocol; produces `evox-cli`.	Desktop UI, installers, and npm Evolver.
`EvoMap/evox-desktop`	Wails desktop client, platform integration, installers, updates, and signing.	Upstream protocol definitions or Evolver asset semantics.
`EvoMap/evolver`	npm Evolver engine, CLI, Proxy, MCP, and GEP asset behavior.	Desktop shell and platform installers.
`EvoMap/evomap-website`	Public product pages, documentation, download-manifest consumption, and frontend acceptance.	Building or signing Desktop, `evox-cli`, or Evolver packages.

Choose where to change code

UI, system menus, browser panes, desktop updates, or installation experience: Desktop.

Gateway, sidecar API, runtime protocol, or evox-cli behavior: EvoX core.

Genes, Capsules, Recipes, Evolver CLI, Proxy, or MCP: Evolver.

Public copy, documentation routes, download pages, and manifest presentation: Website.

Cross-repository delivery

Versions and evidence

Use release tags, manifests, package metadata, and repository tests as factual sources.

Do not infer “supported” from another repository's mock, screenshot, or planning document.

Documentation may describe a cross-repository dependency but must not present an unreleased dependency as currently available.

EvoX Docs · Developers · Repository boundaries