This owner-facing proof path confirms that Pro Se, Attorney, and Family Communications can be entered, used, exported from, and verified while deferred institutional surfaces remain preserved and gated.
Start or resume a matter, review imported records, organize proof, track service and proof, and prepare a reviewed court packet.
Open a matter, manage professional work, review evidence and timeline records, preserve privileged notes, and prepare client-safe or court-facing output.
Create private threads, draft messages, use Before You Send review, preserve private mode, and prepare reviewed digests only when appropriate.
preserved, gated, and compile-safe
preserved and outside active paid-seat navigation
protected by route and API verification
Public e-filing routes keep upload-first intake, editable review, staging controls, status tracking, and no direct court submission from app automation.
Parser output remains staged until human promotion and the ordinary app API cannot directly treat parser candidates as canonical facts.
Filing envelopes, attempts, payment separation, export guards, audit, defect repair, relation-back support, fallback support, and plain-language posture are included in the proof chain.
Active public conversion paths focus on Pro Se, Attorney, and Family Communications without promoting deferred institutional paths as paid seats.
Private notes, privileged work product, family communication drafts, and court-facing packet records carry separate scope labels and review gates.
Paid-seat exports carry scope, review, and sensitive-content labels before records leave the workspace.
Primary paid workflows use wrapping layouts, readable action targets, keyboard posture, and no clipped controls at narrow widths.
Blocks opening paid access until corrected.
Blocks opening paid access until corrected.
Blocks opening paid access until corrected.
Blocks opening paid access until corrected.
Blocks opening paid access until corrected.
Verification record for active paid seats, access paths, privacy posture, exports, and preserved institutional workspaces.
Start or resume a matter, upload records, review suggested details, organize proof, track service and proof, and produce court-ready outputs.
Open a matter, manage clients and tasks, track deadlines, review evidence and chronology, preserve private work product, and prepare client-safe or court-facing outputs.
Create private family communication threads, draft structured messages, use Before You Send review, and produce reviewed digests only when appropriate.
Preserved institutional portals, available from the full platform chooser for approved review.
Preserved and gated outside active paid-seat navigation.
Global banner remains present with training-record and protected-information safety language.
Public visitors compare only Pro Se, Attorney, and Family Communications seats.
Each active seat page explains audience, workflow, first actions, and outputs.
The selected seat is preserved into account setup and handoff.
Returning users are directed to the correct workspace rather than a generic dashboard.
After access is confirmed, the chooser filters workspaces by seat access.
The output QA pass render-reviews Pro Se packets, Attorney reports, Family Communications digests, hearing packets, and e-filing fallback packets for page breaks, signatures, status labels, court-neutral language, manifests, packet hash posture, and safe download audit.
The launch hardening matrix covers phone, tablet, and desktop viewports; keyboard flow; screen-reader labels; table overflow; loading and error states; Core Web Vitals budgets; and route bundle-size review without exposing deferred institutional surfaces in active paid-seat navigation.
The final gate threat-models public conversion, Pro Se matters, Attorney/Firm work product, Family Communications, e-filing/ingest, exports, and ChatGPT/MCP connection paths while preserving human review for AI, parser, filing, and court-output actions.
The final release-candidate gate preserves all completed seat-launch controls, adds support/admin/customer-success operations, records go-live decision points, and keeps production configuration plus launch-owner approval as the controlling release step.
Receive paid-seat support issues with seat, account, matter, billing, connector, export, filing, and urgency classification.
No full legal text, raw messages, tokens, cookies, signed URLs, or payment data are stored in the support ticket body.
Show account, plan, route, adapter, export, packet, connector, and ingestion posture without opening private matter content as the user.
Support reads metadata and redacted support packets only; private case content requires customer-controlled export or explicit escalated authorization policy.
Recover access, rotate sessions, handle lost SSO, and resolve locked accounts without bypassing entitlement or private-data boundaries.
Recovery never grants cross-seat access and never exposes protected data before identity and entitlement are confirmed.
Handle plan cancellation, failed payment, refund request, invoice issue, downgrade, and trial conversion with entitlement reconciliation.
Payment events are separated from legal records; refund or cancellation does not delete legal data without a separate retention and export workflow.
Public paid-seat launch remains limited to Pro Se, Attorney/Firm, and Family Communications.
Disposition: deferred institutional surfaces preserved and hidden from active paid-seat navigation
Critical and high-risk blockers must be closed or explicitly accepted by the launch owner with a mitigation and support procedure.
Disposition: no unresolved critical/high risks in the launch risk register
Production launch requires approved auth, billing, persistence, audit, storage, queue, ingest, email, connector, and provider configuration.
Disposition: provider-pending surfaces are labeled and cannot imply live production integration
Operational control record for secure access, paid-seat continuity, reviewed imports, output safeguards, incident recovery, and full platform owner access.
Platform owner access opens all portals through the post-login chooser.
Login lands on the portal chooser, workspace access issues a platform-scoped session for approved owner accounts, and direct login loops are rejected.
Active MRR seats remain Pro Se, Attorney, and Family Communications while institutional portals remain separated from paid-seat navigation.
Connector material stays staged until a person reviews destination, scope, and merge intent before promotion.
Paid-value outputs carry review posture, scope labels, and neutral wording before use outside the workspace.
Family Communications stays private by default; protective posture requires sustained harmful patterns and reviewed output controls.
The account workspace now exposes launch proof, enterprise readiness, connections, recovery, and route inventory from the portal chooser.
Owner-facing record for the paid-seat release package, controlled configuration notes, responsive review, and final verification path.
Application source, public assets, route families, shared utilities, package manifest, lockfile, verifier scripts, and configuration examples remain in the release package.
Pro Se, Attorney, and Family Communications stay active for paid onboarding with settings, connections, recovery, reports, and export surfaces preserved.
Judicial Edition, Justice, Clerk, Judge, Prosecutor, Defender, and Law Court surfaces remain compatible and separated from active MRR navigation.
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.
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.
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.