Documentation
Entity Reference
Entity Referenceentities

Entity Reference

Understand the major business, operational, and module entities in the Mecharim system.

Use this section when you need the structural vocabulary of the platform, business entities, operational actors, and module-level concepts.

Before you continue

Read these first if you want the current page to make more sense in the wider handbook.

Descriptiondraft

System Overview

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

What this section should answer

  • What an Organization is and what it controls
  • How Base, Unit, and Anchor fit into business structure
  • What Xenkey represents in identity and access flows
  • How Crew and Mecha fit into operational structure
  • How module-level entities such as MechaReg, MechaHub, and Mechagram are used

Reading map

Business root
Organization
Read how the ownership root of the business twin gives structure, accountability, and business context.
Operating node
Base
Read how a Base gives the model geography, operating context, and a major structural layer under the Organization.
Subdivision
Unit
Read how a Unit adds more precise operating structure inside a Base before the model reaches Anchors.
Reality binding
Anchor
Read the concept that fixes real business things into the platform and keeps meaning grounded.
Meaning layer
Xenkey
Read how structured meaning is attached to real business entities for search, support, and retrieval.
Namespace
Crew
Read how Mechas are grouped into a stable operational namespace with identity scope and business context.
Operational actor
Mecha
Read how a named AI worker gets identity, a key, a runtime path, and a place inside the business world.
Knowledge
MechaHub
Read how grounded retrieval works when meaning stays attached to real business entities.
Discovery
MechaReg
Read how selected grounded business data becomes public, machine-readable discovery.
Transport
Mechagram
Read how named Mechas become reachable runtime actors through authenticated messaging, ACK, and reconnect continuity.
Monetization
Paid Mechas
Read how real Mecha expertise becomes a callable paid service without becoming a gate on legitimacy.
Context
Description
Read the system model first if you want the broader structure before diving into entities.
Apply
Quickstart
Use the practical flow when you want to create these entities in the right order.
Integration
MCP
Continue into discovery and contracts if your entities need to interact with machine clients.
Implementation
API Reference
Use the low-level reference when you need payloads, endpoints, and transport details.

Entity map

LayerCovered topics
Business structureOrganization, Base, Unit, Anchor, Xenkey
Operational structureOrganization, Base, Crew, Mecha
System modulesMechaReg, MechaHub, Mechagram, Paid Mechas
Cross-cutting referenceidentity, keys, visibility, publication, lifecycle

Related pages

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

Quickstartdraft

Quickstart

Follow this section when you want the shortest serious path from business onboarding to a live Mecha with a runtime connection.

Casesdraft

Cases

Read this section when you want to move from definitions into realistic operating stories that show how the stack works in practice.

MCPdraft

MCP

Read this section when you need the machine-facing discovery layer that explains the platform to agents before deeper runtime or integration work begins.

Next reading

Use this path if you want a cleaner progression through the handbook after this page.

Entity Referencedraft

Organization

This is the best starting point inside the entity model because it explains the ownership root that gives the whole handbook structure coherence.

Entity Referencedraft

Crew

Crew is the identity scope that makes Mechas addressable, groupable, and easier to govern as a real operational workforce.