Civil society workflow surface
Saved articles — your watch panel
A no-account watch list for civil-society coalitions and affected-community networks tracking specific instruments and topics. Pinning happens via the ★ Save button on any catalog row. The list lives only in your browser's localStorage — PW's server never sees what you saved and there is no cross-device sync.
Data flow: (1) Save buttons across the wiki write a slug to your browser at key pw:saved-articles. (2) This page resolves each saved slug to a canonical article title server-side (so you see real editor-curated names, not auto-capitalised slug fragments). (3) A 30-day changelog window is queried server-side; any saved slug with recent revisions is decorated with a chip. (4) All of that renders alongside the localStorage list — nothing about your watch set leaves your browser.
Privacy posture:no accounts, no cookies, no IPs logged for the watch list, no cross-device sync, no third-party analytics. Your list never leaves your browser. The 30-day changelog set is the SAME for every visitor; what's personalised is which of those slugs you have pinned, and that lookup happens client-side.
Charter §7.6: no microtargeting; every visitor sees the same scaffold + manifest + recently-updated set. §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.
How updates surface
The "Recently updated" chip on a saved row means we have a revision captured for that slug in the last 30 days — derived from the public /wiki/changelog feed, not from any personal browsing history. Click through and the article header shows the per-version diff banner if you have a pw:last-visited-iso stamp from a previous visit. The diff is calendar-day resolution, calculated entirely against the public ArticleRevision table — no per-user state on our side.
See /wiki/changelog/feed for the RSS / Atom version if you prefer to track changes in a feed reader rather than via the watch panel.
Alternative: email alerts
Email-based watching is intentionally a separate workflow — it requires an account (so we can email you back) and uses the existing AlertButton flow inside the article body rather than this anonymous panel. See /wiki/persistent-id for the persistent-identifier and citation backbone the alert system threads through, and /wiki/influence-tracker for the parallel CSET-style citation log that documents how PW evidence surfaces in external regulatory + research outputs.
The watch panel + email alerts coexist by design: the panel is the anonymous workflow for advocates who don't want to leave any server-side trace; the email channel is the opted-in workflow for coalitions that want active push notifications + can accept the account + email-list implications.
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.