Current capabilities
See what Atlas Lyme supports in the current public release and how each capability contributes to evidence-aware investigation.
This page describes the current public Atlas experience. Use it to choose a supported workflow and to avoid treating a planned or experimental idea as a released capability.
Capability status
Atlas uses four status labels:
- Available now — verified in the current public release and appropriate to document as user behavior.
- Planned — part of the product direction, but not available to rely on today.
- Experimental/demo — available only in a constrained, feature-gated, or validation context; do not treat it as a production commitment.
- Not supported — outside the current product promise or deliberately excluded from the public experience.
What you can do today
| Capability | Status | How it supports investigation | Important boundary |
|---|---|---|---|
| Front Porch | Available now | Read the public introduction at / without a sign-in. | It does not show county scores, a map of results, or a comparison. |
| Atlas Explorer | Available now | Sign in and start from the United States or one state. Read the map and county list together, then open county evidence and suggested follow-up on the same address. | A review-priority signal is not a diagnosis, disease-burden estimate, or individual risk estimate. National scope is a bounded picture, not a ranking of every U.S. county. |
| Compare two counties | Available now | Open Compare for two counties from the same release and read each measure's unit, period, and availability. | The page does not rank a winner. It does not compare five counties. |
| Inspect evidence and provenance | Available now | Open county evidence and Inspect provenance before deciding what to review next. | Check source, geography, time or vintage, release, method version, freshness, completeness, uncertainty, and limitations. |
| Share a workspace address | Available now | Share an Atlas Explorer or Compare URL that keeps scope, county, compare, release, period, and Explorer mode. | Record the release and method with the URL. A URL does not guarantee that a future release will contain identical data. |
| County PDF | Available now | From county evidence, export a county PDF when Atlas can verify that the file matches the displayed county, observations, sources, period, and caveats. | If that check fails, the PDF is unavailable. That is not a claim that the report contains none of a period. |
Authenticated professional workspace
These routes require sign-in. The professional workspace guide describes each destination. Older public bookmarks open Atlas Explorer after sign-in. They do not keep a separate public map.
| Capability | Status | How it supports investigation | Important boundary |
|---|---|---|---|
| Atlas Explorer at /explore | Available now | Start from the United States or one state, and read the map and county list. Open county evidence or suggested follow-up on that address. | National scope is a bounded picture. It is not a ranking of every U.S. county. A saved default applies only when the address has no scope and no county. On a state picture with no county, Atlas Explorer selects the first published review candidate and writes it into the address. A county that is present but does not validate opens with selection=required and is not replaced. |
| Compare at /compare | Available now | Compare two counties on aligned measures, with unit, period, and availability on each value. | This page does not rank a winner. |
| Settings at /app/settings | Available now | Save United States or a state as the next Atlas Explorer start, plus optional role, organization, and job title. Sign out, export, and removal use the account controls on the same page. | Optional fields can stay empty. The default does not change evidence values or block other geographies. |
| Docs from the workspace | Available now | Open this reference in a new tab from the workspace navigation. | The original workspace tab keeps its URL. Docs is not in-page help. |
| Ask Atlas at /askatlas | Experimental/demo | Atlas Explorer and Compare open this dedicated page. It requests reviewed literature when that service is enabled. Explorer and Compare can pass a validated page reference and a return link. | Feature-gated. The reference is not sent as a county or comparison request. With the service off, the page says Ask Atlas is unavailable and the other pages stay usable. There is no side panel, no Structured mode, and no Both mode. History stays in this browser. |
| Feed at /app/feed | Planned | The destination is in the navigation. | It does not yet provide feed items or alerts. |
| Evidence brief | Experimental/demo | A direct plan=evidence-brief address still opens that brief and returns to county evidence. | It is not a workspace destination. Surveillance planning is not released. |
| API keys in Settings | Not supported | Public API reads do not use a key. | Settings does not generate or revoke a key. See API, MCP, and access and the developer quickstart. |
Capabilities that are not current promises
| Capability | Status | What this means for you |
|---|---|---|
| Historical release trends | Not supported | The public explorer currently exposes one active release. A generated date is release metadata, not the date of disease observations. |
| Guaranteed outbreak prediction or automated public-health action | Not supported | Atlas surfaces signals and investigation candidates. It does not predict with certainty or act on behalf of an authority. |
| Clinical diagnosis or person-level exposure risk | Not supported | Atlas is a population-level public-health decision-support experience, not a clinical or individual-risk tool. |
| Additional clinical, laboratory, jurisdictional, or other governed sources | Planned | Atlas is designed to adapt future sources into the same evidence model. The current release stays open-data-first. See Sources and canonical evidence. |
| Live EHR, TEFCA, patient-level, PHI, or production clinical-laboratory ingestion | Not supported | Naming a future standard is not a connection. No live EHR or production clinical-laboratory feed is part of this release. |
| AI-generated findings treated as authoritative | Experimental/demo | AI-enabled experiences must remain grounded in approved evidence, show limitations, and retain human review. Do not use an AI suggestion as a finding by itself. |
| Alerts, private feeds, or account-based evidence access | Not supported | The Front Porch remains usable without sign-in. A workspace account does not unlock different governed evidence, change a score, or authorize an interpretation. Feed does not list items, and alerts are not released. |
| Separate public map, five-county comparison, or Investigation Workspace | Not supported | Older /overview, /geographic_explorer, and /investigate bookmarks open Atlas Explorer after sign-in. They do not restore a separate public analytical page. |
Where to start
- Sign in and open Atlas Explorer for the map, county list, county evidence, and suggested follow-up.
- Open Compare for two counties.
- Read the professional workspace guide for Atlas Explorer, Compare, Ask Atlas, Feed, Settings, and Docs.
- Follow the investigation workflows for question-to-next-step guidance.
- Read evidence, provenance, and uncertainty and the methodology context beside the result before relying on a signal. Keep the AI Ethics commitments nearby for AI-enabled or experimental experiences.
- Read sources and canonical evidence before treating a future source, file format, or clinical standard as available.
- Read AI-enabled decision intelligence for the status of AI-assisted and future capabilities, or use the FAQ and troubleshooting guide for common questions.
The current release is a situational-awareness foundation. When a question depends on a feed, model, alert, historical comparison, or export that is not listed as available now, treat it as an open product or data dependency and do not infer the answer from the interface.