Owner-facing control record for onboarding support, access recovery, import recovery, output review, and release interruption handling.
Use the portal chooser as the recovery point for users who reach the wrong workspace or return from a stale link.
Smoke the primary workspace and the settings/connections/recovery path before marking the account ready.
Keep records staged until the user confirms destination, scope, and merge intent.
Stop sharing/exporting if an output scope label is missing or private material appears in an external packet.
Rerun public copy and route-family verification before publishing any public conversion update.
First action: Open /portal and confirm the assigned seat route appears.
Escalation: Review account seat assignment and rerun portal access verification.
First action: Return the record to staged import review and confirm destination controls.
Escalation: Rerun paid-seat connections/recovery verification before allowing additional imports.
First action: Stop export use and confirm private/client/court/family scope labels.
Escalation: Rerun privacy/security and launch proof verification before release.
First action: Patch the concrete build or route warning and rerun the build-gate verification chain.
Escalation: Use the deployment readiness failure ladder before another release attempt.
Secure access, portal chooser, active paid seats, operations center, and recovery surfaces.
Seat smoke, settings, connections, recovery, exports, and public pricing route.
Public copy scan, Justice For All route lock, public filing route family, and pricing focus.
Build warning review, source context check, auth entry check, and active paid-seat smoke.
Release-control record for build proof, source context hygiene, runtime entry, environment checks, and post-deployment smoke review.
Platform owner access remains routed through the portal chooser before opening any workspace.
The deployment package excludes generated archives, local dependency folders, prior build output, audit debris, and private environment files while preserving public assets, route mirrors, verifiers, and documentation required by release checks.
The build gate runs repository hygiene, export integrity, store contract, public language, login, auth entry, portal integrity, upload/settings/connections, public banner, Justice For All, public filing, and ChatGPT connector checks before production build.
The application package builds for the standalone runtime entry and starts through the packaged server with the assigned port.