Step 1 of 2 in the onboarding flow: creates a new business (Zitadel organization), synchronously. When business_name is omitted, the server falls back to the invora:org_name (+ invora:default_branch_country) metadata the login UI stamped on the user at registration (invora-zitadel-login/src/lib/server/register.ts); those keys are cleared server-side once consumed, so a later CreateBusiness call (e.g. for a second business) requires an explicit business_name.Step 2 (client-driven, not part of this RPC): the client sets the returned org_id as the org-context header, then calls the existing BranchesService.Create with default_branch_country (or a user-supplied country if that field came back empty) to create the default branch. There is no server-side auto-branch creation in this flow — the client always creates the branch explicitly.