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

BAA / DPA / Compliance Evidence ​

Purpose: Audit-ready inventory of every signed BAA, click-through compliance amendment, and supporting evidence file. SOC 2 CC9.2 / HIPAA §164.314 / EDE Phase 3 SA-9.

Convention: filename pattern <vendor>-<doc-type>-<YYYY-MM-DD>.{pdf,png}. Every file referenced from docs/security-compliance/vendor-register.md.

Current evidence files ​

FilenameVendorTypeDateCross-reference
aws-organizations-baa-signed-2026-04-18.pdfAWSSigned BAA PDF (org-wide; covers all 4 member accounts)2026-04-18vendor-register.md Tier 1
google-workspace-hipaa-baa-acceptance-2026-05-01.jpgGoogle WorkspaceAdmin Console click-through screenshot showing the "Google Workspace/Cloud Identity HIPAA Business Associate Amendment" accepted by [email protected] on May 01, 2026. Click-through is the legal acceptance method per Google's BAA model — no separate signed PDF exists.2026-05-01vendor-register.md Tier 1
mongodb-atlas-baa-signed-2026-05-14.pdfMongoDB AtlasSigned BAA PDF (doc LA-50572; org-level — covers MongoDB Cloud Services for the customer, so both Atlas projects askflorence-prod-01 + askflorence-staging are in scope). AskFlorence: Taha Salahuddin Abbasi (Founder), 2026-05-13. MongoDB, Inc.: Ashley Kilpatrick (Director, Global Billing), 2026-05-14. Effective Date = fully-signed date 2026-05-14.2026-05-14vendor-register.md Tier 1

Conventions ​

  • PDFs: signed contracts (DocuSign, manual signature, etc.). Filename: <vendor>-baa-signed-<YYYY-MM-DD>.pdf.
  • PNGs / screenshots: click-through acceptance evidence (Admin Console, vendor portal). Filename: <vendor>-<doc-type>-<YYYY-MM-DD>.png. Capture the date stamp + accepting user identity in the screenshot.
  • Retention: 6 years minimum (HIPAA), 10 years preferred for EDE alignment.
  • Access: read-only for non-Taha team members; Taha is the steward.
  • Updates: when a BAA expires / renews / a vendor retires, move (don't delete) the file with a -retired-<date> suffix and update vendor-register.md.

Open follow-ups ​

  • [x] MongoDB Atlas — signed BAA PDF collected + filed as mongodb-atlas-baa-signed-2026-05-14.pdf (doc LA-50572, fully executed 2026-05-14, org-level scope covers both Atlas projects)
  • [ ] At Florence Phase 1 — Anthropic BAA, file as anthropic-direct-api-baa-<date>.pdf
  • [ ] At Phase 5 (agent platform) — NIPR BAA, ID-verify vendor BAA
  • [ ] Drata / Vanta / Sprinto onboarding — DPA in addition to BAA (compliance vendor processes our metadata)

Where to find evidence not yet collected ​

VendorWhere to look
MongoDB Atlas (already collected)Atlas support ticket; BAA tied to org (askflorence@). Signed copy filed 2026-05-14.
AnthropicAnthropic console → org settings → BAA download (when on Tier 1+)
AWS (already collected)AWS Artifact → Compliance Reports → BAA
Google Workspace (already collected)Admin Console → Account → Account Settings → Legal & Compliance → Security and Privacy Additional Terms
Pager
Previous pageDependency Vulnerability Policy
Next pageCompliance-Automation Integration

AskFlorence Internal Documentation. Not for public distribution.

AskFlorence

Internal Documentation

Access restricted. Not for public distribution.