Skip to content

Phase 20: GDPR right-to-erasure analysis & design (design-only) #24

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
cemililik wants to merge 2 commits into from
Closed

Phase 20: GDPR right-to-erasure analysis & design (design-only) #24

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
774d029
docs(phase-20): GDPR right-to-erasure analysis & design
cemililik May 2, 2026
074e533
docs(phase-20): address review-bot + reviewer findings
cemililik May 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,21 @@ All notable changes to ForgeLM are documented here.
> Per-PR CHANGELOG entries below collapse into the v0.5.5 release
> notes at tag time.

### Added — Wave 2a / Phase 20 — GDPR right-to-erasure design

- **GDPR Article 17 erasure analysis & design document** —
`docs/analysis/code_reviews/gdpr-erasure-design-202605021414.md` is the
Phase 20 deliverable: 12 sections + 11-test plan + file map that pin the
scope of Phase 21's `forgelm purge` implementation. Maps every Article
17(1) trigger to a ForgeLM action; enumerates the seven artefact kinds
that may carry personal data; specifies the `RetentionConfig` Pydantic
block (Article 5(1)(e) storage limitation); specifies the three new
audit events (`data.erasure_requested` / `data.erasure_completed` /
`data.erasure_failed`); resolves three Wave 1 carry-overs (GH-023, GH-013,
Round-5 concurrent-approve lock), six open questions; supplies the
marketing-claim replacement copy for `safety_compliance.md`. No code
changes in this PR — design only; Phase 21 implements.

### Added — Wave 1 closure (Faz 9, 11, 12, 13, 25, 31, 32 — see PR description)

- **Article 14 staging directory + `forgelm approve` / `forgelm reject` (Faz 9)** —
Expand Down
Loading