---
id: compliance-docs-scaffolds
prd: docs/work/prds/compliance-docs-scaffolds.prd.md
title: Compliance docs scaffolds — Epic D of ADR-025
type: epic
status: in-progress
features: []
created: 2026-05-20T12:00:00Z
updated: 2026-05-20T12:21:53.062Z
---

## Goal

Ship the compliance documentation layer: seven copy-and-fill policy templates, a template-tailored pre-launch compliance checklist, a single `compliance-overview.md` hub mapping the 22 playbook sections, and a refreshed `operator-checklist.md`. Pure documentation — no code, no manifests, no conformance rules.

## Why

Epics A–C shipped the compliance machinery (PII manifests + retention + sub-processor generators, DSR + consent + cookie banner, security headers + rate-limit + SBOM). Epic D fills three remaining documentation gaps: no human-authored policy artifacts, no single launch gate, and no compliance map. A downstream consumer currently writes these from a blank page. ADR-025 settled the strategy; this epic is the implementation.

## Stories

- [x] [01 — Land operator-checklist.md verbatim](01-land-operator-checklist/_story.md)
- [x] [02 — Refresh operator-checklist.md for ADR-024 and ADR-025](02-refresh-operator-checklist/_story.md)
- [x] [03 — Write seven policy templates](03-policy-templates/_story.md)
- [ ] [04 — Write pre-launch compliance checklist](04-pre-launch-compliance-checklist/_story.md)
- [ ] [05 — Write compliance-overview.md hub](05-compliance-overview/_story.md)
- [ ] [06 — Wire compliance docs into CLAUDE.md, README, and glossary](06-doc-wiring/_story.md)