Danijel Martinek
2b39ae8c0a
Move the 8 shipped template epics and their 9 PRDs (incl.
coverage-architecture) to docs/work/archive/{epics,prds}/ so dispatch
context and prioritization only see live Veect work. The state builder
already walks docs/work/epics/ + docs/work/prds/ only; the one work-CLI
script that matched archive paths (bump-updated-timestamps.mjs, staged
docs/work/**/*.md) now excludes docs/work/archive/ so archived content
stays byte-identical.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016j8z4VHjedXDTjEDNg7qHK
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 | done | 2026-05-20T12:00:00Z | 2026-05-20T12:52:53.917Z |
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.