Atlas

Overview

Atlas is the layer that keeps a case file current. It reads records, bills, calls, and documents as they arrive, extracts the facts, and updates the case file without anyone retyping them.

Atlas sits underneath the rest of EveOS. Auditor, Analyst, agents, and research all run on the data it maintains, so it is not a tool the team opens so much as the thing the other tools read from.

It runs alongside the firm's case management system. It does not replace it, and there is no migration.

What It Reads

Documents, medical records, bills, call transcripts, notes, and connected case management fields. As each one arrives, Atlas extracts and structures the case model: incident and litigation facts, insurance, liens, expenses, providers, and contacts.

Three Things That Make It Usable

• Every value is cited. Each field and entity traces to the document or record it came from, so a number can be checked rather than trusted.

• Conflicting sources are reconciled, not overwritten. A new fact is checked against what Atlas already holds. The order of precedence is human entry first, then case management fields, then documents, so a colleague's entry is not silently replaced by a document. Higher-stakes changes route toward review.

• It does not need clean data first. Standardized case management fields are not a precondition. Atlas reads what is there, maps it to a consistent schema, and normalizes it.

What Ships Today

Atlas is available for personal injury firms and ships three pieces:

• Extraction agent, which keeps entities and fields current as new material arrives.

• Settings hub, the single place to configure what Atlas extracts and how.

• Custom fields, for data specific to a practice, configured with the Eve team.

Getting It Enabled

Atlas is opt-in rather than on by default. The Eve team enables it per firm and confirms the matter scope is personal injury.

Rollout runs in two stages. The Eve team verifies Atlas on 3 to 5 matters first, checking that it pulls the data the firm actually needs. Once the firm confirms it is working, Atlas rolls out to the rest of the matters.

Atlas needs time to work through data after it is connected, so the case file fills in as material is processed rather than all at once. After setup, nobody interacts with the extraction agent directly, only with what it puts in the case file.

What Atlas Does Not Do

• Write back to a case management or document system. Atlas reads from them and does not write to them. Medical Overview is the one place Atlas writes back into the firm's own system.

• Replace a case management system. It runs alongside one, reconciling structured fields with documents and calls.

• Support non-PI matters. Personal injury only.

Key Terms

• Case model: The structured picture Atlas maintains, covering incident and litigation facts, insurance, liens, expenses, providers, and contacts.

• Extraction agent: The component that reads new material as it arrives and keeps fields current.

• Settings hub: The single configuration surface for what Atlas extracts.

• Custom fields: Firm-specific fields beyond the standard case model, configured with the Eve team.

• Reconciliation: How conflicting sources are resolved, with human entry taking precedence over case management fields, which take precedence over documents.