Candidate C hybrid restoration prep

OnyxIntel case work, rebuilt around the live safe line

This branch keeps the verified production shell as the base, restores the remembered platform-module structure from the April redesign, preserves firm customization and prelitigation templates, and keeps every external or final legal action gated.

Open dashboard Open command center Open workup

Safe Candidate A modules grafted onto Candidate C

The product structure is restored as source-owned copy and layout, without importing stale routes, sample data, broad marketing controls, or outdated external-action assumptions.

Document Intake

Uploads, source-email evidence, split-out documents, and routing posture are kept visible before review.

Records And Bills

Records requests, response matching, draft gaps, billing evidence, and safe external gates stay separated.

Medical Chronology

Treatment evidence, provider timelines, missing records, and chronology readiness are organized for review.

Specials And Damages

Bills, EOBs, ledgers, liens, payments, balances, and damages review remain distinct by source.

Demand Workup

Demand evidence, draft readiness, exhibit workup, and final attorney gates stay clear and local-first.

Directory Confidence

Provider, payor, insurer, records, billing, radiology, and agency contacts retain source history.

Role-aware visibility remains part of the branch

Dashboard navigation continues to use existing role guards, with platform-admin surfaces separated from firm-admin work and unresolved operational work kept in local queues.

Firm leadership

Operational readiness, risk posture, usage, audit, and gate state remain role-scoped.

Legal staff

Daily queues focus on deterministic internal work, fix-lists, and safe external gates.

Review teams

Exception lanes separate wrong-client, low-confidence, duplicate, and source-missing evidence.

Candidate B and current operations stay available

Firm settings, prelitigation templates, provider directory, external gate posture, and export readiness stay on the current authenticated route model.