First Organization and Mecha
Follow the first realistic path from control-plane entry to a structured business twin, a Crew, and a first working Mecha.
This is the best case to read after Quickstart if you want to see how the first complete setup path comes together as one operational story.
Before you continue
Read these first if you want the current page to make more sense in the wider handbook.
By the end of this case, a business has entered the control plane, created its first structure, created a Crew, defined a Mecha, and is ready to issue a key and connect runtime.
Why this case matters
Many readers understand the platform conceptually, then still need one simple story that answers:
- what gets created first
- what depends on what
- when the runtime actually appears
This case gives that story in one pass.
Starting state
At the beginning:
- the team can access the private frontend
- the business is not yet modeled inside the platform
- there is no Crew
- there is no Mecha
- no runtime is connected
The flow
1. Enter the control plane
The operator signs in and completes onboarding with real business identity data.
This matters because the frontend is the place where humans define the business world and govern the operational actors.
In the current onboarding flow, the system creates the initial identity spine in one transaction:
OrganizationOriginPrimary BasePrimary Crew
This is the most important stage in the whole path because these records are not
framed as casual throwaway setup.
The Origin is permanent, and core legal identity fields are treated as locked
after onboarding.
If the information entered here is false, the problem is not cosmetic. It undermines verification, compliance, public trust, and downstream readiness.
2. Build the business twin
The team creates:
- the
Organization - at least one
Base - one or more
Unitsif the operating shape needs them - the first
Anchors - the first
Xenkeys
This step gives the system a world that can later support routing, retrieval, support, and public representation.
3. Create the operational layer
The team creates:
- a
Crew - a first
Mecha
At this point the Mecha exists as an owned operational identity, but it is not yet live in runtime.
4. Prepare runtime
The operator issues a Mecha key and stores it securely.
That key becomes the credential the external runtime will use later.
The key lesson
The sequence matters:
- establish the real business identity
- expand the world
- define the actor
- issue the credential
- connect the runtime
If the order is reversed, the platform loses clarity and the Mecha becomes much less grounded.
If the identity root is false, the platform also loses trust and serious use can be blocked.
What modules are involved
| Layer | Role in this case |
|---|---|
| Business twin | Gives the first structured world |
| Crew and Mecha | Create the first operational actor |
| MechaHub | Becomes useful once the world has grounded meaning |
| MechaReg | Can later expose the public face of selected grounded data |
| Mechagram | Carries runtime traffic once the Mecha connects |
Business effect
- the business becomes structured instead of vague
- the first Mecha becomes accountable instead of generic
- later runtime work becomes easier to reason about
- the team gets a repeatable onboarding path
- the business starts from a trustable identity root instead of a disposable test record
Recommended next pages
- Continue with Issue a Mecha Key.
- Continue with Connect a Mecha Runtime.
- Continue with Grounded Support.
Related pages
Open these pages when you want adjacent concepts, neighboring entities, or connected implementation context.
Registration and First Login
This is the most important stage of the whole onboarding path, because it establishes the business identity, creates the first foundational entities, and locks choices the rest of the platform will depend on.
Create the Business Structure
Build the world first, the platform becomes much more useful once Organization, Base, Unit, Anchor, and Xenkey exist before runtime work begins.
Create the Operational Structure
Create the Crew and Mecha layer so the business has named operational actors inside the structured world.
Next reading
Use this path if you want a cleaner progression through the handbook after this page.
Issue a Mecha Key
This step bridges control-plane setup and real runtime operation by issuing the credential the external process will actually use.
Grounded Support
This case shows the practical value of MechaHub, the support flow becomes more precise when answers are grounded in real entities and structured meaning.