fraqtal/agentic-dev
Template
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
Files
3a1b0886c51ea4e610cdc54654f3b9469a322031
agentic-dev/docs/work/archive/epics/dsr-consent-and-cookie-banner/_epic.md
Danijel Martinek 2b39ae8c0a docs(work): archive shipped template epics and PRDs 
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
2026-07-12 17:32:20 +02:00

2.1 KiB
Raw Blame History

id, prd, title, type, status, features, created, updated
id prd title type status features created updated
dsr-consent-and-cookie-banner docs/work/prds/dsr-consent-and-cookie-banner.prd.md DSR + consent abstraction + cookie consent banner — Epic B of ADR-025 epic done
core-shared
core-consent
core-dsr
core-ui
core-eslint
core-testing
core-api
auth
2026-05-19T12:00:00Z 2026-05-19T22:09:30.310Z

Goal

Ship the user-rights surface end-to-end: DSR endpoints that walk Epic A's PII tags to export/delete/rectify/restrict any subject's data, per-use-case consent gates with audit-logged proof, and a compliant cookie consent banner with EU-prominence defaults.

Why

Epic A delivered declarative PII inventory + retention + sub-processors. Epic B closes the remaining gaps: GDPR Arts. 15–18 + 20 DSR endpoints, Art. 7 demonstrable consent with structural lint enforcement, and a CNIL-compliant cookie consent banner that downstream consumers can drop in without forking legal-compliance logic.

Stories