platform.tenant.provision

Provision a tenant: create its schema, run migrations, register it.

• Scope: platform.tenant.write
• System: yes
• Reachable from: no request — the CONTROL face does not mount this command. It creates a tenant — a schema, its migrations and its first credentials — which is the one operation the platform performs ON the fleet rather than on a tenant. It stays in-process by the CP-1 decision, so no request can ever be the thing that grows the fleet.
• Events: platform.tenant.provisioned

Input (JSON Schema)

{
  "properties": {
    "id": {
      "minLength": 1,
      "type": "string"
    },
    "schemaName": {
      "maxLength": 63,
      "pattern": "^[a-z_][a-z0-9_]*$",
      "type": "string"
    }
  },
  "required": [
    "id"
  ],
  "type": "object"
}

Result (200)

{
  "additionalProperties": false,
  "properties": {
    "id": {
      "type": "string"
    },
    "schema_name": {
      "type": "string"
    }
  },
  "required": [
    "id",
    "schema_name"
  ],
  "type": "object"
}

Errors

validation_failed (400) · unauthorized (401) · forbidden (403) · conflict (409) · internal (500)