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

docs(work): archive shipped template epics and PRDs

Browse Source 
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
This commit is contained in:
Danijel Martinek
2026-07-12 17:28:21 +02:00
parent 2126fda6f8
commit 2b39ae8c0a
86 changed files with 5 additions and 757 deletions
Download Patch File Download Diff File Expand all files Collapse all files

46
docs/work/archive/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: done
feature: ~
depends-on: [03-policy-templates]
blocks: [05-compliance-overview]
created: 2026-05-20T12:00:00Z
updated: 2026-05-20T12:37:24.995Z
---
## 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
- [x] 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`.