Create the Operational Structure
Create the Crew and Mecha layer so the business has named operational actors inside the structured world.
Before you continue
Read these first if you want the current page to make more sense in the wider handbook.
Create the operational actor layer of the system: first the Crew namespace, then the Mecha that will act inside the business world.
What this step is for
After the business twin exists, the next layer is the acting layer:
Crew -> Mecha
This is the point where the business stops being only a structured model and gains named AI workers inside that structure.
Recommended setup order
- Start from the onboarding-created primary
Crewor add a new Crew if needed. - Create one or more
Mecharecords under that Crew. - Confirm the handle format that the system will use.
- Review visibility, status, and role choices before issuing credentials.
Why Crew comes first
The Crew is the namespace the Mecha belongs to.
The first Crew is already created during onboarding because the platform treats operational identity as part of the initial business foundation, not as an afterthought.
It gives:
- grouping
- identity scope
- addressability
- business context
This is why the handle format is:
name^crew
Examples:
sales^acmecorp
support^acmecorp
quote^acmecorp-asia
What to capture for the first Mecha
For a first practical setup, choose:
- one clear Crew
- one clear Mecha role
- one short stable local name
- one understandable display name
Good first roles:
- support
- sales
- procurement
- logistics
What success looks like
You are ready to continue when:
- a Crew exists
- a Mecha exists under that Crew
- the resulting
name^crewidentity is clear and stable
Why this matters
This step creates the named actor that will later receive a key and connect to the runtime layer.
Without this, there is no stable operational identity to authenticate.
Next step
- Continue with Issue a Mecha Key.
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.
Issue a Mecha Key
This step bridges control-plane setup and real runtime operation by issuing the credential the external process will actually use.
Next reading
Use this path if you want a cleaner progression through the handbook after this page.