Chris4K commited on
Commit
9092aaa
·
verified ·
1 Parent(s): ead5978

Update main.py

Browse files
Files changed (1) hide show
  1. main.py +1 -1
main.py CHANGED
@@ -353,7 +353,7 @@ def seed():
353
  # LEGAL
354
  {"container":"legal","folder":"gdpr","title":"Fusion Labs GDPR Deletion Architecture — Concept v3",
355
  "body":"Decentralized pull-based deletion across 14+ systems in 6 countries (DE, AT, CH, IT, FR, NL).\nCore flow: DPO triggers deletion request -> orchestrator creates deletion ticket -> each system polls /api/deletions/pending -> system processes and POSTs Proof of Deletion (PoD) certificate -> orchestrator tracks completion.\nPoD schema: {request_id, system_id, subject_id, deleted_fields[], timestamp, checksum, processor_name}.\nArchitecture Board sign-off required. DPO must countersign each PoD batch.",
356
- "summary":"Pull-based GDPR deletion design for Fusion Labs 14-system landscape","tags":["gdpr","bofrost","deletion","architecture","pod"],"importance":10,"author":"christof","version":"v3"},
357
  {"container":"legal","folder":"regulations","title":"GDPR Article 17 — Right to Erasure (Key Points)",
358
  "body":"Art. 17 GDPR: Data subject has right to erasure without undue delay when: (a) no longer necessary for original purpose, (b) consent withdrawn, (c) data subject objects under Art. 21, (d) unlawful processing, (e) legal obligation.\nExceptions: freedom of expression, legal obligation, public interest (Art. 17(3)).\nTimeline: respond within 1 month (extendable 2 months for complex cases).\nLogging: document all erasure requests and outcomes.",
359
  "summary":"GDPR Art. 17 erasure right summary","tags":["gdpr","erasure","regulation","art17"],"importance":9,"author":"christof"},
 
353
  # LEGAL
354
  {"container":"legal","folder":"gdpr","title":"Fusion Labs GDPR Deletion Architecture — Concept v3",
355
  "body":"Decentralized pull-based deletion across 14+ systems in 6 countries (DE, AT, CH, IT, FR, NL).\nCore flow: DPO triggers deletion request -> orchestrator creates deletion ticket -> each system polls /api/deletions/pending -> system processes and POSTs Proof of Deletion (PoD) certificate -> orchestrator tracks completion.\nPoD schema: {request_id, system_id, subject_id, deleted_fields[], timestamp, checksum, processor_name}.\nArchitecture Board sign-off required. DPO must countersign each PoD batch.",
356
+ "summary":"Pull-based GDPR deletion design for Fusion Labs 14-system landscape","tags":["gdpr","Fusion Labs","deletion","architecture","pod"],"importance":10,"author":"christof","version":"v3"},
357
  {"container":"legal","folder":"regulations","title":"GDPR Article 17 — Right to Erasure (Key Points)",
358
  "body":"Art. 17 GDPR: Data subject has right to erasure without undue delay when: (a) no longer necessary for original purpose, (b) consent withdrawn, (c) data subject objects under Art. 21, (d) unlawful processing, (e) legal obligation.\nExceptions: freedom of expression, legal obligation, public interest (Art. 17(3)).\nTimeline: respond within 1 month (extendable 2 months for complex cases).\nLogging: document all erasure requests and outcomes.",
359
  "summary":"GDPR Art. 17 erasure right summary","tags":["gdpr","erasure","regulation","art17"],"importance":9,"author":"christof"},