ProSe Legal Operations Platform
Justice For All
Operations center

Enterprise operations center

Command surface for active paid-seat onboarding, queue health, output readiness, import recovery, and owner review actions.

Operational control center ready for platform owner review
Active paid seats
3

Pro Se, Attorney, and Family Communications

Ready
Primary workspaces
18

Seat routes, settings, connections, recovery, reports, and exports

Ready
Staged import controls
7

Gmail, Google Drive, Calendar, OneDrive, Outlook, Dropbox, and Box

Review required
Output scopes
4

Private, client-safe, court-facing, and family communication

Labeled
Owner access mode
All portals

Platform owner route selection through the portal chooser

Controlled
Deferred institutional lanes
7

Preserved and separated from active paid-seat navigation

Preserved
What to review before selling seats

Operational queues

Seat onboarding

Confirms users land in the right workspace after account access.

Pro Se intake first actionAttorney matter setupFamily Communications private thread setup

Open portal chooser and smoke each active paid seat.

Import and recovery

Confirms external material remains reviewed, staged, recoverable, and destination-controlled.

Connector status cardsStaged import queueInterrupted-work recoverySettings export

Open paid-seat connections and recovery surfaces before onboarding users.

Reports and packets

Confirms paid-value outputs are available and safely scoped before download or sharing.

Pro Se court-day packetAttorney client-safe reportFamily Communications reviewed digest

Review output scope labels and missing-item signals.

Privacy posture

Confirms private, client-safe, court-facing, and family communication surfaces remain separate.

Private notesAttorney work productCourt-facing packetsParent-safe digests

Review privacy/security sweep and enterprise gates.

Institutional preservation

Confirms institutional portals remain preserved without distracting paid-seat onboarding.

Judicial EditionClerkJudgeProsecutorDefenderJusticeLaw Court

Confirm institutional portals require platform full access in the chooser.

Direct review paths

Owner action shortcuts

Release controls

Incident response checks

User lands in a single workspace after sign-in instead of the chooser.

Reset next target to /portal and rerun auth entry and portal access verifiers.

Access operations
Connector material appears merged without review posture.

Return the material to staged import status and review destination controls before promotion.

Import operations
Packet export includes private or privileged notes.

Stop export use, confirm output scope labels, and rerun privacy/security sweep before release.

Output operations
Institutional portal appears in public pricing or active paid-seat navigation.

Restore institutional separation and confirm full-access-only chooser placement.

Release operations
Deployment readiness

Production deployment readiness

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.

Deployment package ready for controlled release review
Production package checks

Release control gates

Source package hygiene
Ready

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.

Clean source contextNo committed dependency folderNo private environment filesVerifier assets preserved
Build verification chain
Ready

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.

Build gate before buildAuth verifierPublic route locksConnector guardrails
Runtime entry point
Ready

The application package builds for the standalone runtime entry and starts through the packaged server with the assigned port.

Standalone outputPort-aware startPublic assets copiedStatic assets copied
Support operations

Support operations readiness

Owner-facing control record for onboarding support, access recovery, import recovery, output review, and release interruption handling.

Support operations ready for paid-seat onboarding
Paid-seat operating controls

Support lanes

Access recovery
Owner: Account operations
Ready
Login opens secure access
Successful access opens the portal chooser
Sign-out clears the local workspace session
Owner access can open all portals

Use the portal chooser as the recovery point for users who reach the wrong workspace or return from a stale link.

Paid-seat onboarding
Owner: Seat operations
Ready
Pro Se opens to case command work
Attorney opens to professional matter operations
Family Communications opens to private threads
Settings and connections remain visible

Smoke the primary workspace and the settings/connections/recovery path before marking the account ready.

Import recovery
Owner: Connections operations
Ready
Connector status cards remain visible
Imported records stay staged
Destination can be changed before promotion
Interrupted work can be restored

Keep records staged until the user confirms destination, scope, and merge intent.

Final readiness

Final launch package readiness

Owner-facing record for the paid-seat release package, controlled configuration notes, responsive review, and final verification path.

Package ready for final local build and deployment smoke
Release contents

Package manifest

Source package
Included

Application source, public assets, route families, shared utilities, package manifest, lockfile, verifier scripts, and configuration examples remain in the release package.

Active paid seats
Included

Pro Se, Attorney, and Family Communications stay active for paid onboarding with settings, connections, recovery, reports, and export surfaces preserved.

Deferred institutional surfaces
Preserved

Judicial Edition, Justice, Clerk, Judge, Prosecutor, Defender, and Law Court surfaces remain compatible and separated from active MRR navigation.

Configuration and review posture

Controlled launch notes

Environment values
Controlled configuration required

Production service URLs, allowed accounts, session secret, OAuth redirect values, and provider keys must be supplied through the deployment environment before release.

Deployment preflight verifies required values and reports optional provider configuration separately.

OAuth provider status
Provider configuration required

Google and Microsoft entries remain safe when provider configuration is unavailable, and Google local-origin handling avoids invalid 0.0.0.0 redirects during local review.

Login and Google SSO origin verifiers protect the post-login portal chooser contract.

Connector imports
Review required

Imported material stays staged until a person confirms destination, scope, and merge intent before promotion into a matter.

Paid-seat connections and recovery verification protects staged import review and recovery controls.