Skip to main content

Civil-society watch panel

Your pinned Policy Window articles, rendered with last-revision dates and a client-side "what changed" diff. No accounts, no cookies, no tracking — your reading list lives only in your browser's localStorage and never reaches PW's server. Pin an article via the ★ Save button on any /wiki/[slug] page.

How this works without an account:Save buttons across the wiki write a slug to your browser's localStorage at key pw:saved-articles. This page reads that key client-side and renders the pinned list. PW's server never sees what you saved.

Charter §7.6: no microtargeting; every visitor sees the same scaffold. §7.1.a: no advocacy framing in the watch surface itself — you (or your coalition) write the advocacy.

Loading your saved articles from localStorage…

What to pin

  • The 3-5 instruments your campaign tracks (e.g., EU AI Act, GDPR, Council of Europe AI Convention, US Federal AI memos).
  • Sector topics relevant to your community (e.g., biometric ID, training data, employment-AI, deepfakes — see /wiki/for-advocates §3 for the 7-topic harm-narrative gap list).
  • Enforcement-case-rich pages — Clearview (CNIL / Garante / ICO LFR), Mobley v. Workday, FTC v. OpenAI — for litigation-aware coalitions.
  • Charter and methodology pages for the cite-the-source workflow when drafting submissions.

Beyond watching: contribute

  • Suggest a missing instrument or topic via the GitHub-issue link in /wiki/charter §6.
  • Harm-narrative pipeline (Wave 3 of iter-316 plan): civil-society partners will be able to contribute structured affected-community accounts at /wiki/[slug]/harm-narratives (peer-reviewed, attributed to submitting organisation, never editor-authored). Status: scaffolding planned; charter §7 revision proposal is the gating step.
  • Coalition-letter evidence pack (also Wave 3): structured .docx with citations + comparative-jurisdiction crosswalk + related-debates. Evidence-only output; coalition writes the advocacy.