Base
Understand how a Base works as a major operating node in the business twin and why it gives the platform geography, structure, and context.
Base is the first major structural split under the Organization, the layer that gives the business twin real operating geography and stable context.
Before you continue
Read these first if you want the current page to make more sense in the wider handbook.
A Base is a major operating node under an Organization. It gives the business twin a real structural and geographic layer before the model becomes more specific through Units, Anchors, and Xenkeys.
What a Base is
The Base layer sits directly under the Organization in the business twin:
Organization -> Base -> Unit -> Anchor -> Xenkey
A Base represents a major business node such as:
- headquarters
- branch
- regional hub
- warehouse
- major business location
- operating center
It is the level where the model starts gaining meaningful geography and operational structure.
Why a Base matters
Without a Base layer, the system often jumps too fast from “the whole company” to very specific entities.
That creates weak context:
- locations blur together
- regional ownership becomes vague
- routing becomes less precise
- repeated structures are harder to express cleanly
With a Base layer, the platform can say:
- this business has several major operating nodes
- this node owns a specific region or context
- downstream units and entities belong somewhere specific
How it relates to the rest of the model
Organization
Organization is the ownership root of the world.
Base
Base adds the first major operating breakdown under that owner.
Unit
Unit adds a more specific subdivision inside a Base, such as a store,
department, lab, or service slice.
Anchor
Anchor fixes a real business thing into that structured context.
Xenkey
Xenkey attaches structured meaning to that anchored thing.
This order matters because the platform stays easier to reason about when each layer does one clear job.
Practical examples
A Base may represent:
hq-londonretail-asiawarehouse-eastservice-center-munich
These are not just names. They are the context in which more specific Units, Anchors, and Mechas can make sense.
Why it matters for Mechas
Mechas become more useful when they work inside business structure instead of a flat world.
A Base helps with:
- regional ownership
- location-aware routing
- clearer operational context
- cleaner specialization of teams and Mechas
That means a Mecha is less likely to act as a generic assistant and more likely to act inside the right operating context.
Business effect
| Capability | Business effect |
|---|---|
| Major operating node | Better geography and organizational clarity |
| Structural context | Better routing and downstream ownership |
| Regional scope | Easier separation of locations, branches, and hubs |
| Foundation for Units and Anchors | More precise entity modeling and support |
What a Base is not
- not the whole company
- not the most specific entity layer
- not the meaning layer
- not a runtime actor
It is the first major operating breakdown inside the business twin.
Recommended next pages
- Continue with Organization.
- Continue with Anchor.
- Continue with Mecha.
Related pages
Open these pages when you want adjacent concepts, neighboring entities, or connected implementation context.
Unit
Unit adds the finer operating layer inside a Base, which makes routing, ownership, and later Anchors much more precise.
Anchor
Anchor is one of the most important concepts in the platform because it is the point where structure stops being abstract and starts binding to something real.
Crew
Crew is the identity scope that makes Mechas addressable, groupable, and easier to govern as a real operational workforce.