Quickstart
Create the Business Structure
Quickstartquickstart / create-the-business-structure

Create the Business Structure

Build the digital twin first by defining the business structure that Mechas will later work inside.

Build the world first, the platform becomes much more useful once Organization, Base, Unit, Anchor, and Xenkey exist before runtime work begins.

Before you continue

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

Quickstartdraft

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.

What this step is for

This step expands the identity foundation created during onboarding.

Before a Mecha can work well, the platform needs a business world for it to work inside.

That world is the digital twin:

text
Organization -> Base -> Unit -> Anchor -> Xenkey

This structure gives the platform:

  • ownership
  • geography and operating context
  • real business entities
  • meaning attached to those entities

Recommended setup order

  1. Confirm the onboarding-created Organization.
  2. Confirm the onboarding-created primary Base.
  3. Create more Base records if the business already has multiple major operating nodes.
  4. Add Unit records where you need more specific subdivisions.
  5. Add Anchor records for real business entities.
  6. Add Xenkey records where you need structured meaning around those entities.

What each layer does

LayerPurpose
OrganizationOwnership root of the business world
BaseMajor operating node such as a branch or regional hub
UnitMore specific subdivision inside a base
AnchorReal business thing fixed into the model
XenkeyStructured meaning attached to that real thing

Practical guidance

  • do not treat the onboarding-created identity root as disposable test data
  • start with the smallest structure that still reflects reality
  • do not try to model every edge case on day one
  • use Anchors for real things that matter for search, support, and operations
  • use Xenkeys where meaning, conditions, or evidence need to stay explicit

What success looks like

You are ready to continue when:

  • the business has an ownership root
  • at least one meaningful Base exists
  • the first real entities are anchored into the model
  • the first grounded meaning layer exists where it is needed

Why this step matters

The point is not to create paperwork. The point is to create a world that is machine-legible, grounded, and useful for later Mechas.

Next step

Related pages

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

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

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.

Entity Referencedraft

Xenkey

Xenkey matters because it does not float on its own, it stays attached to an Anchor and therefore keeps meaning tied to real business reality.

Next reading

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

Quickstartdraft

Create the Operational Structure

Create the Crew and Mecha layer so the business has named operational actors inside the structured world.

Quickstartdraft

Issue a Mecha Key

This step bridges control-plane setup and real runtime operation by issuing the credential the external process will actually use.