Platform onboarding

This receipt binds an existing local account, property and member to a reviewed pilot intake. It does not activate a tenant, create access, invite a user or authorize deployment.

BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/pilot_handoff.py:36

23 further boundary constants in this module

• Platform onboarding is reviewed, workspace-scoped, and manual-first. Plan selection prepares entitlement intent, onboarding tasks, and safe drafts; it does not create users, grant vendor or property access, send email, start billing, monitor alarms, or dispatch emergencies.

  ONBOARDING_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:114

• Live activation command records are disabled by default. Creating one does not execute any runtime operation; it documents the locked command plan and required future enablement.

  LIVE_ACTIVATION_COMMAND_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:218

• Pilot kickoff agendas are manual meeting/checklist packets. Completing an agenda does not invite users, grant access, start billing, import production data, send email, monitor alarms, or dispatch work.

  KICKOFF_AGENDA_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:159

• Activation approval packets are post-kickoff human approval receipts. They do not activate the workspace, invite users, grant access, start billing, import production data, send email, monitor alarms, or dispatch work.

  ACTIVATION_APPROVAL_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:166

• Activation execution plans are dry-run operator plans only. Marking a plan ready does not execute identity, access, billing, import, monitoring, or dispatch operations.

  ACTIVATION_EXECUTION_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:172

• Activation closeout packets record outcome and followups for the controlled pilot runway. They do not perform runtime activation, grant access, start billing, send notifications, import production data, monitor alarms, or dispatch work.

  ACTIVATION_CLOSEOUT_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:177

• Activation window packets schedule a future human-controlled activation window only. They do not activate workspaces, invite users, grant access, start billing, import production data, enable monitoring, send notifications, or dispatch work.

  ACTIVATION_WINDOW_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:183

• Activation preflight signoffs record final human/operator readiness evidence for a scheduled window. They do not execute identity, access, billing, import, monitoring, notification, or dispatch operations.

  ACTIVATION_PREFLIGHT_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:189

• Activation abort/rollback packets are contingency planning receipts only. They do not perform activation, rollback runtime data, revoke access, send notifications, start billing, import production data, monitor alarms, or dispatch work.

  ACTIVATION_ABORT_ROLLBACK_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:195

• Runtime activation request packets bind the reviewed runway into a request for a future live activation workflow. They do not activate workspaces, invite users, grant access, start billing, import production data, send notifications, monitor alarms, or dispatch work.

  RUNTIME_ACTIVATION_REQUEST_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:201

• Activation operator assignment logs name operators and witnesses for a future activation attempt. They do not grant privileges, send invitations, start billing, import data, enable monitoring, or dispatch work.

  ACTIVATION_OPERATOR_ASSIGNMENT_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:207

• Activation dry-run verification reports record checks and evidence only. They do not execute identity, access, billing, import, monitoring, notification, or dispatch operations.

  ACTIVATION_DRY_RUN_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:213

• Activation execution audit ledgers seal evidence for a disabled command plan. They do not execute activation steps, invite users, grant access, start billing, or mutate runtime data.

  ACTIVATION_AUDIT_LEDGER_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:223

• Identity invitation adapter packets are dry-run provider intents only. They do not call an identity provider, create subjects, send invitations, or email users.

  IDENTITY_INVITATION_ADAPTER_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:228

• Access grant adapter packets are dry-run grant intents only. They do not create account, workspace, property, vendor, field, or owner-decision access rows.

  ACCESS_GRANT_ADAPTER_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:233

• Activation tasks are reviewed handoff items for a controlled pilot. They do not invite users, grant account, property, vendor, or field access, import production data, send email, start billing, monitor alarms, or dispatch work.

  ACTIVATION_TASK_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:127

• Commercial readiness is an operator-reviewed authorization preview. It records plan, terms, billing-contact, and blocker posture for a controlled pilot; it does not create invoices, subscriptions, payment methods, charges, billing-provider records, emails, access grants, production imports, monitoring, or dispatch.

  COMMERCIAL_READINESS_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:133

• Activation readiness is an operator-reviewed gate on an empty workspace shell. Marking a pilot activation_ready records evidence only; it still does not invite users, grant identity, property, vendor, or field access, import production data, send email, start billing, monitor alarms, or dispatch work.

  ACTIVATION_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:120

• Access request previews are planning bundles only. Drafting or reviewing a preview does not create identity, account, property, vendor, or field access rows, send invitations, start billing, import production data, enable monitoring, or dispatch work.

  ACCESS_PREVIEW_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:140

• Access request packets are auditable handoff receipts generated from reviewed access previews. They do not create users, identity rows, account memberships, property assignments, vendor or field access, invitations, email, billing, imports, monitoring, or dispatch.

  ACCESS_PACKET_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:146

• Commercial authorization packets are start-of-service evidence only. They do not create billing-provider customers, invoices, subscriptions, payment methods, financial charges, email, access grants, imports, monitoring, or dispatch.

  COMMERCIAL_PACKET_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:153

• Activation release manifests are read-only evidence projections. A ready manifest means the packet stack is complete enough for a separate explicit enablement release; it does not enable runtime commands, call identity providers, invite users, grant access, start billing, import production data, monitor alarms, send notifications, or dispatch work.

  ACTIVATION_RELEASE_MANIFEST_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:238

• Pilot launch packets are read-only kickoff projections for human review. They summarize plan proof, empty-shell preparation, activation readiness, handoff tasks, access previews, and commercial boundaries; they do not send email, invite users, grant access, import production data, start billing, monitor alarms, or dispatch work.

  LAUNCH_PACKET_BOUNDARY · apps/api/src/ironbound_api/modules/platform_onboarding/router.py:245

Copied verbatim from apps/api/src/ironbound_api/modules/platform_onboarding/router.py and regenerated from apps/api/src/ironbound_api/modules. The API returns these same strings in its boundary fields, and a drift check fails the build if this page and the source stop agreeing.