Update main.py

main.py

@@ -351,9 +351,9 @@ def seed():
          "body":"CRITICAL: Use sdk: docker in README.md, NOT sdk: gradio.\nGradio SDK CSP blocks ALL <script> tags inside gr.HTML() and all iframes (frame-src: none).\nDockerfile pattern:\n  FROM python:3.11-slim\n  RUN useradd -m -u 1000 user\n  USER user\n  EXPOSE 7860\n  CMD [\"uvicorn\", \"main:app\", \"--host\", \"0.0.0.0\", \"--port\", \"7860\"]\nNo Gradio dependency. Pure FastAPI serves HTML as string. No StaticFiles.\nSurrogate chars: never use \\uD83D in Python strings — use HTML entities &#128196;",
          "summary":"How to deploy FastAPI on HF Spaces without CSP issues","tags":["hf-spaces","docker","fastapi","deployment"],"importance":10,"author":"christof"},
         # LEGAL
-        {"container":"legal","folder":"gdpr","title":"bofrost* GDPR Deletion Architecture — Concept v3",
+        {"container":"legal","folder":"gdpr","title":"Fusion Labs GDPR Deletion Architecture — Concept v3",
          "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.",
-         "summary":"Pull-based GDPR deletion design for bofrost* 14-system landscape","tags":["gdpr","bofrost","deletion","architecture","pod"],"importance":10,"author":"christof","version":"v3"},
+         "summary":"Pull-based GDPR deletion design for Fusion Labs 14-system landscape","tags":["gdpr","bofrost","deletion","architecture","pod"],"importance":10,"author":"christof","version":"v3"},
         {"container":"legal","folder":"regulations","title":"GDPR Article 17 — Right to Erasure (Key Points)",
          "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.",
          "summary":"GDPR Art. 17 erasure right summary","tags":["gdpr","erasure","regulation","art17"],"importance":9,"author":"christof"},