Registration and First Login

What this step is for

This is the real beginning of the business relationship with the platform.

At this stage you are not connecting a runtime yet. You are entering the control plane where humans define the business world, claim identity, and establish the first serious records the system will trust.

The key distinction is:

• the frontend is the control plane
• the Mecha itself runs outside the frontend

The key policy distinction is:

• onboarding is not a sandbox
• onboarding is not a playful trial setup
• onboarding is the point where the platform decides what business identity it is being asked to admit

Before you continue

• make sure you can sign in to the private frontend
• make sure you know which business context you are configuring
• make sure you understand that the first steps are structural and legal-context steps, not runtime steps
• make sure the information you enter is real, deliberate, and defensible

What to do

1. Sign in to the private frontend and enter the onboarding flow.
2. Enter the real legal identity of the organization you are creating.
3. Choose the permanent Origin carefully and confirm it explicitly.
4. Create the initial foundation the system builds in one onboarding transaction:
   • Organization
   • Origin
   • Primary Base
   • Primary Crew
5. Continue only after you are certain the business identity data is correct.

What onboarding creates immediately

The onboarding flow is not only an access step. It creates the first linked business records that define the identity root of the organization inside Mecharim.

In the current product flow, onboarding creates:

This is why onboarding is the most important moment in the whole quickstart.

What is effectively fixed at onboarding

The platform already signals this in the onboarding UI because these choices are not meant to be treated as casual edits later.

• Origin is permanent and must be globally unique
• legal organization name is treated as locked after onboarding
• international legal name is also treated as locked after onboarding
• country of registration is treated as non-changeable
• the first identity spine of the business is established from these choices

If this layer is wrong, the rest of the stack inherits the wrong identity.

Why false information is a blocking problem

Mecharim is about serious business relationships, not about pretending to be a business for experimentation.

If onboarding data is false, misleading, or careless, the platform cannot treat the record as trustworthy business reality.

That creates downstream blocking and readiness problems such as:

• verification stays weak or fails
• compliance state becomes a risk instead of a confirmation
• public MechaReg publication readiness can remain blocked
• billing and tax-related workflows can fail or be blocked
• later discovery, trust, and serious machine-to-machine use become unreliable

The correct mental model is:

If the platform is asked to model a business relationship, the identity data must be real. False onboarding information is not a cosmetic problem. It is a trust failure that blocks serious use.

What success looks like

You are ready to continue when:

• you can access the private control surfaces
• the correct Organization has been created or selected
• the Origin, legal identity, and jurisdiction are correct
• the first Base and Crew foundation exist
• you are ready to expand the business twin and create the first Mecha on top of a real identity root

Why this comes first

Quickstart should not begin with raw transport. It should begin with identity, context, and trust.

The system becomes easier to reason about when the setup order is:

1. enter the control plane
2. establish the real business identity through onboarding
3. expand the business structure
4. expand the operational structure
5. issue credentials
6. connect the runtime

The deeper reason is simple:

• runtime can be retried
• credentials can be rotated
• structures can be expanded
• but false business identity at the root poisons the whole system

That is why this is the most important stage.

Next step

• Continue with Create the Business Structure.
• Continue with Policy if you want the governance reasoning behind this strict onboarding stance.