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

Validation Methodology ​

Status: Active. Last updated April 12, 2026. Purpose: Repeatable process for validating AskFlorence pricing accuracy per state, per plan year.


Why We Validate ​

AskFlorence calculates subsidized health insurance prices from multiple data sources and formulas. Errors in any component (premiums, SLCSP, FPL values, contribution brackets, CSR cost-sharing) produce wrong prices shown to consumers. Validation catches these errors before they reach users.

When to Validate ​

  • New state onboarded - full validation before launch
  • Annual plan year refresh - re-validate when new year's data is loaded
  • Formula change - when IRS contribution brackets, FPL values, or CSR rules change
  • After code changes to subsidy calculation, plan search, or eligibility routing

Validation Sources (ranked by authority) ​

SourceAuthorityCoverageLimitations
State marketplace (NYSOH, Covered CA)HighestState-specific, includes state programsMay be down, requires manual entry
Licensed brokerHighReal enrollment experienceManual, time-consuming
KFF Subsidy CalculatorHighAll states, independentDoesn't show plan-level detail, just APTC
CMS API (federal states)High30 federal statesDoesn't cover SBE states
Issuer SBC documentsHighPlan-specific cost-sharingPer-plan, not aggregated
Our own cross-source validationMediumCatches data pipeline errorsCircular if formula is wrong

Scenario Design ​

Every state validation must cover these categories:

Income Tiers ​

CategoryFPL RangeWhat to Verify
Medicaid thresholdBelow 138%Medicaid routing, adjustment logic for denied applicants
CSR 94%138-150%$0 or near-$0 deductible, lowest copays, highest APTC
CSR 87%150-200%Moderate deductible reduction, reduced copays
CSR 73%200-250%Slight deductible reduction
APTC only250-400%Standard cost-sharing, APTC still applies
No subsidyAbove 400%Full sticker price, no APTC (post-IRA cliff)

Household Compositions ​

TypeWhat to Verify
Single adultBase case
Married couple, no kidsCouple tier multiplier, 2-adult SLCSP
Single parent + children1-adult premium, children to CHP?, FPL household size
Married couple + children2-adult premium, children to CHP?, FPL household size
Older adults (55+)Age rating (federal states) or community rating (NY)

Geographic Coverage ​

TypeWhat to Verify
Multiple rating regionsDifferent SLCSP per region
Multiple counties in same regionSame premiums, different plan availability
Border/edge zip codesCorrect county/region assignment

State-Specific Programs ​

ProgramStatesWhat to Verify
Essential PlanNYEP routing, tier assignment, EP/QHP boundary
CAPS/CAPCCAState premium subsidy on top of federal APTC
Medicaid expansionAllThreshold calculation, auto-adjustment
State CSR enhancementsNY (diabetes, pregnancy)Additional cost-sharing reductions

What to Compare ​

For each scenario, record and compare:

FieldOur ValueKFF / State / Broker ValueAcceptable Variance
FPL %calculatedcalculated$0 (must match exactly)
APTCcalculatedfrom sourceWithin $5/month
CSR tier94/87/73/nonefrom sourceMust match exactly
SLCSP (individual)from DBfrom state dataWithin $1
Household premiumcalculatedfrom sourceWithin $2
Deductible (CSR-adjusted)from DBfrom SBC/stateMust match exactly for standard plans
MOOP (CSR-adjusted)from DBfrom SBC/stateMust match exactly for standard plans
Key copaysfrom DBfrom SBCMust match for standard plans

Running Validation ​

Automated Script ​

Each state has a validation script at scripts/validation/{state}-validation-scenarios.js.

bash
# Start dev server
npm run dev

# Run NY validation (15 scenarios)
node scripts/validation/ny-validation-scenarios.js

# Output goes to stdout — copy to validation doc

Manual KFF Comparison ​

  1. Go to kff.org/interactive/subsidy-calculator
  2. Enter: State, Zip, Income, # Adults, # Children, Ages
  3. Record: APTC amount, SLCSP
  4. Compare against our script output

Broker Validation ​

Share the scenario output with a licensed broker. Key scenarios to prioritize:

  • Medicaid-adjusted cases (KFF just says "Medicaid eligible")
  • State program boundaries (EP threshold in NY, CAPS in CA)
  • Non-standard plan cost-sharing

Documentation ​

Results are stored in docs/validation/{state}-{year}.md with:

  • Test parameters for each scenario
  • Our calculated values
  • Comparison source values
  • Variance analysis
  • Pass/fail determination
  • Date validated and by whom

Re-validation Schedule ​

TriggerScopeTimeline
New plan year data loadedFull re-run all scenariosWithin 1 week of data load
IRS bracket updateAPTC scenarios onlyWithin 1 week of publication
FPL updateAll scenarios (FPL% changes)Within 1 week of publication
Code change to subsidy calcAffected scenariosBefore merge
Quarterly spot-check3-5 scenarios per stateQuarterly
Pager
Previous pageOverview
Next pageAPTC Formula

AskFlorence Internal Documentation. Not for public distribution.

AskFlorence

Internal Documentation

Access restricted. Not for public distribution.