Danijel Martinek
96a8554871
Generated 1 epic + 6 stories under docs/work/epics/ from the approved PRD docs/work/prds/compliance-docs-scaffolds.prd.md. Stories cover landing + refreshing operator-checklist.md, the seven fill-in policy templates, the pre-launch compliance checklist, the compliance-overview hub, and doc wiring (CLAUDE.md, README, glossary). Final epic of ADR-025. Ready for `pnpm work dispatch --execute`.
1.5 KiB
1.5 KiB
id, prd, title, type, status, features, created, updated
| id | prd | title | type | status | features | created | updated |
|---|---|---|---|---|---|---|---|
| compliance-docs-scaffolds | docs/work/prds/compliance-docs-scaffolds.prd.md | Compliance docs scaffolds — Epic D of ADR-025 | epic | in-progress | 2026-05-20T12:00:00Z | 2026-05-20T11:58:25.281Z |
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.