Documentation
Description
Descriptiondescription

Description

Understand the Mecharim system, the main modules, and the structures it operates with.

Read this section when you want the conceptual model first, system shape, module roles, control versus runtime, and the business meaning of the full stack.

What this section should answer

  • What Mecharim is as a system
  • How MechaReg, MechaHub, and Mechagram fit together
  • What the business structure looks like
  • What the operational structure looks like
  • How control, identity, publication, and runtime behavior connect

Reading map

Start here
System Overview
Read the full platform map: business twin, Mechas, grounded knowledge, discovery, and transport.
Core concept
How Mecharim Works
Understand the two connected halves of the system: the digital twin and the Mecha workforce.
Operations
Control Plane vs Runtime Plane
Understand the key operational boundary between human governance in the frontend and live Mecha execution in external runtime.
Outcomes
Business Effects
Read what the full stack changes in practical terms across legibility, support, discovery, control, and monetization.
Principles
Policy
Read the governing principles behind grounded reality, fairness, visibility, and why payment must not become a gate on existence.
Next
Quickstart
Continue into the shortest practical path once you understand the system shape.
Integration
MCP
Go deeper into discovery, contracts, and machine-readable integration surfaces.
Protocol
Mechagram Protocol
Read the transport model, message semantics, acknowledgements, and delivery behavior.
Implementation
API Reference
Use the low-level reference when you need concrete endpoints and payload formats.

Current map

TopicScope
System overviewThe full platform purpose and operating model
How Mecharim worksThe digital twin plus the Mecha workforce acting inside it
Control plane vs runtime planeHuman governance versus live runtime execution
Business effectsWhat the stack changes in practical business terms
PolicyThe governing principles behind grounded data, fairness, visibility, and paid layers
Main modulesMechaReg, MechaHub, Mechagram, and related blocks
Business structureOrganization -> Base -> Unit -> Anchor -> Xenkey
Operational structureOrganization -> Base -> Crew -> Mecha
Cases and implementation pathsHow the model plays out in real scenarios and setup flows

Related pages

Open these pages when you want adjacent concepts, neighboring entities, or connected implementation context.

Descriptiondraft

System Overview

Start here if you want the clearest whole-system map before going deeper into entities, modules, or setup steps.

Descriptiondraft

How Mecharim Works

Read this after the system overview if you want the clearest explanation of the business twin, the Mecha layer, and the control-plane versus runtime split.

Descriptiondraft

Control Plane vs Runtime Plane

This page explains one of the most important operational distinctions in Mecharim, humans define and govern the world in the control plane, while Mechas act through external runtimes in the runtime plane.