Crew
Understand how a Crew works as the namespace and grouping layer for Mechas, and why it gives identity scope, addressability, and business context.
Crew is the identity scope that makes Mechas addressable, groupable, and easier to govern as a real operational workforce.
Before you continue
Read these first if you want the current page to make more sense in the wider handbook.
A Crew is the namespace a Mecha belongs to. It groups Mechas under one identity scope and gives them a stable context for handles, ownership, and operational grouping.
What a Crew is
The operational structure of the platform includes:
Organization -> Base -> Crew -> Mecha
The Crew is the grouping layer that sits between the broader business context and the individual Mecha.
It provides:
- grouping
- identity scope
- addressability
- business ownership context
That is why a Crew is more than a folder. It is the namespace that makes Mecha identity coherent.
Why a Crew matters
Without a Crew layer, Mecha handles become weaker:
- naming gets harder to manage
- multiple workers blur together
- role separation becomes less clear
- routing becomes more ambiguous
With a Crew layer, the system can support:
- multiple workers under one business context
- cleaner specialization by role or region
- more stable addressing
- better operational organization
How it relates to Mecha identity
Each Mecha gets a stable handle in this form:
name^crew
Examples:
sales^acmecorp
support^acmecorp
quote^acmecorp-asia
The Crew part of the handle is what turns a local name into a meaningful and addressable business identity.
How it relates to Mecha
The Crew is the namespace. The Mecha is the individual worker inside that namespace.
That means:
- Crew groups
- Mecha acts
The Crew does not replace the Mecha. It gives the Mecha a structured home.
Why it matters for operations
One Mecha can be useful. A structured squad of Mechas is much more valuable.
Crew enables:
- role separation
- clearer delegation
- easier scaling
- better specialization
- cleaner ownership of operational actors
This is important because the platform is designed for real machine work, not only one assistant surface.
How it relates to the business twin
The Crew belongs to the acting layer, not the business twin itself.
But it still depends on the business model because it should exist inside:
- business ownership
- operational context
- meaningful structure
This is why the business twin and the acting layer should always be read together.
Business effect
| Capability | Business effect |
|---|---|
| Namespace for Mechas | More stable handles and clearer routing |
| Worker grouping | Better organization of multiple AI actors |
| Identity scope | Less ambiguity in machine-to-machine communication |
| Operational structure | Easier specialization by function or region |
What a Crew is not
- not the Mecha itself
- not the business twin
- not only a label
- not only a permissions bucket
It is the grouping and namespace layer for operational actors.
Recommended next pages
- Continue with Mecha.
- Continue with Organization.
- Continue with How Mecharim Works.
Related pages
Open these pages when you want adjacent concepts, neighboring entities, or connected implementation context.
Mecha
Mecha is the central operational actor of the platform, the point where identity, runtime, knowledge, and business context become one working unit.
Create the Operational Structure
Create the Crew and Mecha layer so the business has named operational actors inside the structured world.
Base
Base is the first major structural split under the Organization, the layer that gives the business twin real operating geography and stable context.
Next reading
Use this path if you want a cleaner progression through the handbook after this page.