RootMC Context
Operational context for the RootMC surface as it connects to Ava Ivy, governance, player services, Discord, and the Root Record runtime.
Surface split
RootMC is a distinct public/game ecosystem. Discord is used for player help and data/cloud-facing interaction. Deep runtime and code work belongs in the actual integration tree rather than being inferred from a public chat surface.
Governance boundary
RootMC governance uses weighted Council mechanics rather than a simple one-player-equals-one-vote model. Linked-account state, proposals, polls, and weighted results are runtime concerns and should not be replaced with hard-coded UI assumptions.
Discovered integration paths
The currently discovered runtime candidates are:
/home/ava-core/ava/all-connections/rootmc/discord-slack-poller/src/gateway.mjs/home/ava-core/ava/all-connections/rootmc/discord-slack-poller/src/governanceClient.mjs
Additional copies exist in mirrors and workstation trees. Their presence alone does not make them canonical; active runtime ownership should be verified before editing.
Ava connection
Ava Ivy provides the infrastructure/runtime side of the broader system. RootMC keeps its own player-facing and governance concerns while connecting through explicit integration surfaces.
Ava context · Developer context · Compute and energy roadmap