Skip to content
AskFlorence
Main Navigation ArchitectureFlorence AIAgentsMembersAgent PlatformValidationInfrastructure

Appearance

Sidebar Navigation

Overview

Home

Glossary

System Architecture

Consumer & Agent Flow

Florence AI

Overview

Principles

Runtime

Tool surface

Adding a tool

Tool registry

Knowledge: SBC scenarios & CSR

Voice

Evals & observability

Provider risk & portability

Outage playbook

Roadmap

Build plan

Agents

Overview

Workflows & pain points

Members

Overview

Medicaid coverage gap

Carriers

Overview

Marketplaces

Overview

Agency

Overview

Regulations

Overview

Agent Platform

Overview

Auth Architecture

MongoDB Permissioning

Compliance Model

Data Models

Data Sources

Overview

CMS Marketplace API

CMS dependency map

PUF Data

State Subsidies

SBE Ingestion Playbook

SBE State Watchouts + Decisions

CA Phase C/D Playbook

NY Phase C/D Playbook

Validation

Overview

Methodology

APTC Formula

California 2026

New York 2026

CAPS Formula

Scenario Results

Infrastructure

Account Inventory

AWS Setup Runbook

AWS Organizations

CloudTrail

GuardDuty

Security Hub

Config

CloudFront + WAFv2

Data sources & ingest

Phase 4 DNS

Change Log

Vulnerability Management

MongoDB Setup

Access Control

Data Classification

Documentation Hosting

Post-deploy Smoke

Development

Preflight (local CI mirror)

Testing strategy

Compliance

Overview (auditor entry point)

SOC 2 Control Mapping

HIPAA Control Mapping

CMS EDE Appendix A Mapping

Risk Assessment

Encryption Policy

Data Retention Policy

Privacy Impact Assessment

Consent Capture & Versioning

Incident Response Plan

Access Control Policy

Marketing vs. Portal Analytics

Vendor / Subprocessor Register

Dependency Vulnerability Policy

BAA / Compliance Evidence

Compliance-Automation Integration

Compliance-Automation Vendor Evaluation

Penetration Test Reports

Architecture

Portal entry handoff

Mobile app strategy

Deferred architecture decisions

Session cookie architecture

Share flows

Decisions (ADRs)

Index

0001 — Atlas project isolation

0002 — Append-only audit log

0003 — Narrow-scoped Mongo users

0004 — Cross-cluster Atlas PrivateLink

0005 — Delayed-job architecture

0006 — Mongo user simplification

0007 — Terraform owns ECS task def

0008 — E2E testing strategy

0009 — Self-hosted analytics + observability (superseded)

0010 — PostHog HIPAA Cloud (supersedes 0009)

Runbooks

Security Incident Response

Break-Glass Root Login

Onboard Team Member

Offboard Team Member

Atlas user provisioning

Deploy via Terraform (ENG-277)

Rollback via Terraform (ENG-277)

S3 data bucket migration (planned Phase 11)

Access Reviews

2026-Q2 Review

Session log

Index

2026-04-23 — Phase 10 DNS cutover

2026-04-22 — Phase 8 prod AWS mirror

2026-04-22 — Phase 7 Atlas VPC peering

2026-04-22 — Phase 6 CloudFront + WAF

2026-04-21 — Phase 5 staging go-live

2026-04-17 — Atlas staging

Briefs

Index

Member portal plan (ENG-187)

2026-04-16/17 handoff

2026-04-17 Atlas handoff

System briefing (2026-04-17)

Creative AdBundance proposal brief

Creative AdBundance analytics brief

ElevenLabs RN integration research

Policies

Overview

On this page

Tier 2 — Zip → Premium Audit ​

Last run: April 14, 2026 Duration: 38.4 minutes Total zip-county entries: 28,196 CMS calls: ~28,200

Purpose ​

For every zip in our service area, verify the cheapest Silver plan at age 35 single-adult $50K income matches CMS exactly. This catches per-zip variance within counties (partial county coverage, RA boundary issues) that the county-level validation can't see.

Method ​

Per zip:

  1. Look up our cheapest Silver plan via ageRatesByArea[regionId]['35'], filtered by countiesServed and partialCountyZips
  2. Query CMS at the same zip + county FIPS
  3. Compare cheapest Silver premium

Results — April 14, 2026 ​

MetricCount%
Exact matches28,04899.475%
Mismatches890.316%
Only in ours (CMS missing)00.0%
Only in CMS (ours missing)00.0%
CMS errors590.21%

Match rate excluding CMS errors: 99.683% (28,048 / 28,137)

Mismatch analysis ​

All 89 mismatches were caused by wrong rating area assignments in zip_county — the same pattern we fixed in the county-level validation. CMS returns a different rate for the same plan because the county is actually in a different RA than our DB has it labeled.

Affected counties (12 unique, 158 zip rows) ​

StateCountyOld RAFixed ToZips
AKAnchorage1220
AKYukon-Koyukuk1232
AKBethel2127
AKKenai Peninsula1215
AKLake and Peninsula1214
AKKusilvak1212
AKAleutians East126
AKKodiak Island126
AKDillingham127
AKAleutians West127
AKChugach124
ORColumbia159

Why these were missed in the county-level audit: The county-level validation samples one zip per county. For these AK counties, the sampled zip happened to give the same cheapest plan as CMS by coincidence (different premium from a fallback plan). The full zip-level audit catches everything.

CMS errors (59 zips) ​

All "max retries exceeded" — CMS timeouts. Distributed across runs in batches when CMS was slow. These zips will retry on the next audit run.

CMS API stats ​

total: 28201
success: 28142
retried: 295 (backoff events)
failed: 59
avgLatencyMs: 175
successRate: 99.79%

Action taken ​

Ran rating area corrections for the 12 counties via CMS verification. Updated zip_county.regionId to match what CMS expects. Expected next run: 100% match (modulo CMS-side errors).

Production impact ​

The 89 zips were showing slightly wrong cheapest Silver plans to users — typically $9-$24 off. Users would still see plans, but not necessarily the cheapest one available per CMS. Now fixed.

Pager
Next pageHome

AskFlorence Internal Documentation. Not for public distribution.

AskFlorence

Internal Documentation

Access restricted. Not for public distribution.