fraqtal/agentic-dev
Template
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

chore(work): decompose compliance-docs-scaffolds epic

Browse Source 
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`.
This commit is contained in:
Danijel Martinek
2026-05-20 13:58:24 +02:00
parent ee4af9bb96
commit 96a8554871
8 changed files with 417 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

46
docs/work/epics/compliance-docs-scaffolds/04-pre-launch-compliance-checklist/_story.md Normal file
View File

@@ -0,0 +1,46 @@
---
id: 04-pre-launch-compliance-checklist
epic: compliance-docs-scaffolds
title: Write pre-launch compliance checklist
type: user-story
status: todo
feature: ~
depends-on: [03-policy-templates]
blocks: [05-compliance-overview]
created: 2026-05-20T12:00:00Z
updated: 2026-05-20T11:58:25.281Z
---
## Goal
Create `docs/guides/pre-launch-compliance-checklist.md` as a two-column Markdown table mapping every playbook obligation (drawn from playbook §19 + the 22 sections) to its coverage status: "Shipped by template" (with verification command), "Consumer responsibility", or "Infra responsibility". The table operationalizes ADR-025's three-way coverage split into a checkable launch gate.
## Why
A launching team currently has no single answer to "are we compliant enough to ship to a paying customer?" The playbook §19 is generic; nothing maps it to this template's concrete features (`pnpm compliance:emit-all --check`, `core-audit`, DSR endpoints) or explicitly flags which obligations are on the consumer vs the infra vs already handled. This checklist provides that clarity and produces verification evidence on demand for compliance officers.
## Done when
- `docs/guides/pre-launch-compliance-checklist.md` exists and contains a two-column table.
- Rows are grouped by playbook section (Infrastructure, Data, Application, Secrets, Sub-Processors, Logging, Breach, DSR, Backup, SDLC, Workforce, Legal, Documentation).
- Every "Shipped by template" row names a runnable verification command (e.g. `pnpm compliance:emit-all --check`, `pnpm conformance`, securityheaders.com scan).
- Every "Consumer responsibility" and "Infra responsibility" row is explicitly labelled as such.
- The file links to `docs/guides/compliance-overview.md` and to relevant templates in `docs/compliance/templates/`.
- All 22 playbook sections are represented.
- Every relative Markdown link resolves to an existing file.
- Commit type is `docs(compliance)`.
- `pnpm lint && pnpm typecheck && pnpm test && pnpm conformance && pnpm fallow:audit` all pass.
## In scope
- `docs/guides/pre-launch-compliance-checklist.md` — the two-column launch gate table.
- Links outward to `compliance-overview.md` and `docs/compliance/templates/*.template.md`.
## Out of scope
- Machine-enforceable CI gate for this checklist (deferred).
- Changes to any existing guide files.
## Tasks
- [ ] Write `docs/guides/pre-launch-compliance-checklist.md` as a two-column table covering all 22 playbook sections (Infrastructure, Data, Application, Secrets, Sub-Processors, Logging, Breach, DSR, Backup, SDLC, Workforce, Legal, Documentation), labelling each obligation as "Shipped by template" (with inline verification command), "Consumer responsibility", or "Infra responsibility", and linking to `compliance-overview.md` + relevant templates; commit as `docs(compliance): add pre-launch compliance checklist`.