Editorial Board
The Policy Window AI Governance Wiki is catalog-curated, not crowd-edited. Articles render from typed catalog constants (no single author wrote them) but the catalog itself is reviewed by named editors. This page lists who.
1 · What editors do (and don't)
- Review catalog scope — which topics should be added, merged, or deprecated under the topic-determination framework (methodology §4).
- Review source selection — that every
sourceUrlcites a primary source of appropriate authority for its claim. - Review methodology — that the anti-hallucination grounding mechanisms still bind in practice, and that any change to the editorial workflow is documented.
- Do NOTwrite article prose. Article bodies render deterministically from catalog rows — editors edit those rows, they don't compose narratives. This is the structural commitment that makes the wiki citable.
2 · Conflicts of interest disclosure
Every editor lists their affiliations and any direct funding or contractual relationship with AI labs, regulators, or advocacy organisations that could plausibly shape catalog decisions. Disclosure is per-editor and updated as relationships change. Editors recuse themselves from catalog rows where their disclosed relationships create a conflict.
3 · Current board
The board is being constituted. Placeholder slots below document the structure (one subject editor per topic kind + a methodology lead). Real editors will replace each placeholder as recruited. This is an honest disclosure of the current state, not a fictional roster. Following the methodology page's §6 version-history honesty pattern.
| Editor | Role | Topic cluster | Conflicts of interest |
|---|---|---|---|
| Ryan WongPolicy Window (project lead) | Founding editor + maintainer | All — interim until subject editors are recruited | Project founder; no current funding from any AI lab or regulator. |
| Subject editor — Capability classes | Subject editor | foundation_models, biometric_id, deepfakes, agentic_systems_governance, catastrophic_risk | To be disclosed on recruitment |
| Subject editor — Sectoral applications | Subject editor | employment, healthcare, criminal_justice, education | To be disclosed on recruitment |
| Subject editor — Procedural obligations | Subject editor | transparency, redress, compute_reporting, training_data, synthetic_content_provenance, open_weight_release | To be disclosed on recruitment |
| Subject editor — Political frames | Subject editor | sovereign_ai, tech_sovereignty, development_rights_framing | To be disclosed on recruitment |
| Methodology + meta-domain reviewer | Methodology lead | international_coordination + methodology framework + anti-hallucination grounding | To be disclosed on recruitment |
4 · Become an editor
We're actively recruiting subject editors with primary- source expertise in each topic cluster. Editors commit to quarterly catalog reviews + COI disclosure + recusal where appropriate. Time commitment: ~2–4 hours per quarter. Affiliation with academia, civil society, regulators, or industry is welcome; the COI disclosure is what manages the risk, not the affiliation itself.
Interested? Open a GitHub issue with your expertise + topic clusters + any COI to disclose.