Last modified: August 24, 2025

For versions: 1.0.0.1

Wiki
Governance
Monthly Public Discussion — Universal Operating Model

Estimated reading time: 75 min

About This Guide

1.1 Purpose and scope

This guide is the Universal Operating Model for all Global Risks Forum (GRF) tracks—Research, Innovation, Policy, Capital & Investment, and New Media & Civic Foresight. It provides a single, plain-language playbook for how monthly public discussions run, who does what, what must be produced, and how results move through Planetary Nexus Governance (PNG) from the Central Bureau (CB) to Regional Stewardship Boards (RSBs) to National Working Groups (NWGs).

What this handbook covers (scope)

Core principles: neutrality, evidence standards, clause compliance, privacy & confidentiality.
Roles & responsibilities (Chair, Committee Leads, Facilitator, Rapporteur, Governance Secretary).
Monthly cadence: intake → pre-reads → 90-min public discussion → outputs → hand-offs → follow-through.
Standard agenda and required artifacts (AAR, Clause Pack delta, Policy/Investment/Comms notes).
Handoffs and acceptance criteria to GCRI/NSF/GRA/RSBs/NWGs/New Media.
Measurement (KPIs), calendaring, inclusion & accessibility, security & digital hygiene.
Dispute resolution and escalation consistent with PNG.

What is out of scope

Entity charters, financial approvals, or HR policies of any Nexus institution.
Tool/product development (owned by technical units such as TMDs/NE Inc.).
Long-form research/methods manuals (maintained by GCRI) and standards registries (maintained by NSF).

How to use it

Treat Sections 2–14 as normative (“MUST/SHOULD/MAY” language is intentional).
Apply Section 20 Track Overlays to add domain-specific inputs/outputs without changing the universal core.
Use the templates in Section 22 exactly as provided, unless your overlay has an approved variant.

Non-negotiables

Membership ≠ governance; leadership is honorary and non-fiduciary.
GRF does not own or develop tools; all outputs are clause-licensed and routed to the appropriate Nexus entity for implementation.
Confidentiality, conflict-of-interest (COI), and document-labeling rules apply to all contributors.

1.2 Who should use this

This handbook is written for everyone who participates in GRF track operations. Each role below includes how to read this document:

Track Chairs (Leaders Council):
- Read Sections 3–5, 8–12, 13, and 22.
- Use the Chair Checklist (Sec. 22.9) before, during, and after each discussion; own KPIs and follow-through.
Committee Leads (five lanes: Science/Methods; Standards/Clause; Policy/Regulatory; Capital/Investment; Media/Civic):
- Read Sections 4, 8–11, 16, 22.
- Own your lane’s pre-reads, in-session inputs, and monthly artifacts; ensure hand-off readiness.
Facilitators & Rapporteurs:
- Read Sections 4, 8–10, 16, 18, 22.10.
- Keep sessions on time/neutral; deliver an accurate, ≤3-page AAR within 5 business days.
Governance Secretaries:
- Read Sections 4, 6–7, 8, 10–11, 13, 17, 18, 22.11.
- Run COI and document-labeling, maintain official records, and update the CB master calendar.
Advisors, Fellows, Observers, and General Members:
- Read Sections 3, 6, 8–10, 15, 22 (templates as reference).
- Contribute evidence, review drafts when requested, and uphold neutrality and confidentiality.
RSB/NWG Focal Points, Central Bureau Schedulers, and Trustees:
- Read Sections 2–3, 8, 11, 12–14, 17, 21–22.
- Ensure calendars align, hand-offs are acknowledged, and governance records stay current.

1.3 How this universal model relates to track-specific overlays

The universal model defines how every track runs. Track overlays (Section 20) define what is specific to each domain (inputs, tests, extra artifacts). Use these rules of engagement:

Precedence & consistency
- The universal model is authoritative for roles, cadence, agenda, required outputs, hand-offs, QA, KPIs, and compliance.
- Overlays extend the universal model with domain-specific details; they do not weaken neutrality, evidence standards, or licensing.
Allowed variations
- Overlays MAY add data sheets, checklists, or annexes; they SHOULD keep the 90-minute agenda intact.
- Time-boxing may shift by ±5 minutes with Chair approval if all required segments are preserved.
Change control
- Any overlay change that affects roles, required outputs, licensing, or compliance must be approved per Section 1.4 (owner/approver flow) before use.
- Once approved, update the overlay’s version and note the change in this handbook’s Change Log.
Examples
- Research overlay adds Replication Appendix; Innovation overlay adds Readiness Gate; Policy overlay adds Jurisdiction Collision Map; Capital overlay adds Covenant Redlines; New Media overlay adds Narrative Risk Table. All inherit the same cadence and outputs.

1.4 Document control (version, owner, review cadence, change log)

1.4.1 Control table

Field	Value / Instruction
Title	GRF All Tracks Universal Operating Model (Handbook)
Short name	GRF-UTOM
Classification	Internal (shareable with invited participants); label specific artifacts Public/Internal/Restricted as per Sec. 6
Version	v1.0.0 (Initial release)
Status	Approved
Effective date	[YYYY-MM-DD]
Next review	Quarterly (end of Q1/Q2/Q3/Q4) or upon material governance change
Owning body	GRF Governance Secretariat (on behalf of the Board of Trustees)
Document owner	Track Operations Lead, Global Risks Forum
Approver	Chair, Board of Trustees (or delegated PNG Trustee)
Editors	Central Bureau Scheduler; Chairs’ Council Representative; Governance Secretary (docs)
Distribution	Track Chairs, Committee Leads, Facilitators, Rapporteurs, Governance Secretaries, RSB/NWG focal points, CB schedulers, Trustees
Supersedes	N/A (first consolidated edition)
Related documents	PNG Charter; GRF Code of Conduct & Privacy Notice; Clause Licensing & Attribution Guide; NSF Registry Guide; GCRI Methods Notes; GRA Corridor Handbook

1.4.2 Review cadence

Quarterly review led by the Document Owner with Chairs’ Council input.
Interim updates allowed for urgent compliance, security, or legal changes (fast-track approval by Approver).
All updates must include a redline and an updated Change Log entry.

1.4.3 Amendment protocol (summary)

Draft change (Document Owner) → 2) Internal review (Editors + affected Leads) → 3) Legal/compliance check if required → 4) Approval (Approver) → 5) Publish new version (replace prior; archive superseded) → 6) Notify distribution list and update CB calendar note.

1.4.4 Change log (template)

Date	Version	Editor	Summary of change	Sections affected	Approval ref
[YYYY-MM-DD]	v1.0.1	[Name]	Clarified COI recusal steps and tightened AAR acceptance criteria	Sec. 6, Sec. 10	BOT-[ID]
[YYYY-MM-DD]	v1.1.0	[Name]	Added Capital overlay “Covenant Redlines” annex; updated acceptance criteria	Sec. 20.4, Sec. 11.2	BOT-[ID]

Licensing & compliance note: This handbook and its artifacts are clause-licensed. GRF leadership is honorary/non-fiduciary. GRF does not own or develop tools; commercial implementation routes to the appropriate Nexus entity. All contributors must follow COI, confidentiality, and document-labeling rules.

PNG Alignment & Governance Map

2.1 Planetary Nexus Governance (PNG) at a glance

What PNG is: a simple, layered way to move from global strategy to local action—and back again—without losing scientific rigor, legal integrity, or public trust. It synchronizes people, processes, and evidence across the Nexus Ecosystem.

The layers (who does what):

General Assembly (GA) — the top democratic forum. Ratifies policies and budgets; elects the Global Stewardship Board.
Board of Trustees (BoT) — legal and fiduciary oversight. Approves governance rules; ensures compliance and continuity.
Global Stewardship Board (GSB) — strategy brain. Sets yearly priorities and success metrics across themes (climate, health, finance, tech, etc.).
Central Bureau (CB) — the nerve center led by the Group CEO. Turns strategy into a unified plan and calendar; assigns resources; tracks delivery.
Regional Stewardship Boards (RSBs) — regional adapters (Africa, Asia, MENA, Europe, North America, South America). Translate global plans into regional realities and oversee execution.
Specialized Leadership Boards (SLBs) — topic experts (e.g., data governance, health, infrastructure, finance). Keep science, methods, and regulatory thinking sharp.
National Working Groups (NWGs) — country teams. Implement pilots, gather evidence, and report ground truth.
Bioregional Assemblies — community voice. Bring local knowledge, culture, and equity into decision-making.
Technical Management Divisions (TMDs) — build and maintain the technology (simulation, EO/AI, dashboards, digital twins).
Nexus Interfaces — where entities cooperate:
- GCRI (science & foresight)
- GRF (public convening & diplomacy)
- GRA (capital & corridor structuring)
- NSF (standards, clauses, audits)
- NE Inc. (enterprise deployment)

In one sentence: PNG makes sure decisions are well-evidenced, legal, inclusive, and executable—from Geneva to the grassroots and back.

2.2 GRF’s role within PNG (what GRF does / does not do)

GRF does:

Convene monthly public discussions for each track (Research, Innovation, Policy, Capital & Investment, New Media & Civic Foresight).
Translate complex risks into clear options using structured agendas, stress-testing, and neutral facilitation.
Publish concise, actionable artifacts (AARs, clause-pack deltas, policy/ investment/ comms notes).
Hand off decisions and evidence to the right bodies (GCRI/NSF/GRA/RSBs/NWGs) with clear owners and deadlines.
Safeguard neutrality: enforce conduct rules, COI declarations, document labels, and accessibility standards.
Amplify bottom-up inputs: integrate Bioregional Assembly and NWG evidence into regional and global conversations.

GRF does not:

Own or develop tools (platforms, models, dashboards, code). Those live with TMDs/NE Inc./other technical units.
Raise or broker capital inside GRF sessions (no “deal room” behavior). Capital discussions produce signals and requirements, not transactions.
Sell governance or influence (membership never buys decision rights).
Replace the legal authority of BoT/GA or the strategic mandates of GSB/RSBs.

GRF outputs are: short, neutral, verifiable, clause-licensed documents that other bodies can use immediately to legislate, standardize, pilot, or finance.

2.3 Decision flow: CB → RSB → NWG and where monthly public discussions fit

The core loop:

[GSB sets priorities]
        │
        ▼
[Central Bureau (CB)]  — annual plan, master calendar, resources
        │
        ▼
[RSBs]  — regional adaptation: goals, pilots, partners
        │
        ▼
[GRF Monthly Public Discussions]  — options under stress, neutral artifacts
        │            │           │            │
        ├────────────┼───────────┼────────────┤
        │            │           │            │
     → GCRI       → NSF       → GRA        → RSBs/NWGs
   (methods)    (clauses)   (capital)      (local pilots)
        │            │           │            │
        └────────────┴───────────┴────────────┘
                         ▲
                         │
                   [CB status & KPI tracking]

How it runs month to month (plain steps):

CB sets the frame (themes, goals, calendar).
RSBs localize the plan (regional needs, partners, timelines).
GRF hosts the monthly track discussions (public, time-boxed, neutral).
Outputs and hand-offs go to:
- GCRI/TMDs for methods and data work,
- NSF for clause/standard updates,
- GRA for corridor and capital structuring,
- RSBs/NWGs for policy/pilot localization,
- New Media for public explainers.
NWGs implement and report back; RSBs review; CB tracks progress and risks.
Feedback returns to GRF/RSBs/GSB to refine priorities and cycle again.

Where the monthly public discussions fit:

They are the decision-shaping waypoint. GRF does not “decide law or budget”; it tests options, clarifies trade-offs, and assigns owners for next actions.

Acceptance criteria for a “good” cycle:

Pre-reads issued on time; COI cleared; labels applied.
AAR ≤3 pages, neutral, referenced; all hand-offs have named owners and due dates.
Receiving bodies acknowledge within 5 business days; progress checked at T+14.
KPI updates logged to the CB calendar.

2.4 Guardrails: neutrality, clause compliance, “membership ≠ governance,” “no tool ownership”

Neutrality (always on):

Use the standard agenda; keep debate on evidence and options, not advocacy.
Declare conflicts; recuse when needed.
Label all docs: Public / Internal / Restricted; follow the label.

Clause compliance:

Convert decisions into clause text (definitions, triggers, covenants) for NSF; track redlines and collisions.
All GRF outputs are clause-licensed; cite sources; keep audit trails.

Membership ≠ governance:

Joining GRF does not grant voting power or fiduciary control.
Leadership roles are honorary, invitation-based, performance-reviewed, and non-fiduciary.

No tool ownership:

GRF sessions do not build, host, or sell technology.
Any implementation or commercialization flows to the appropriate Nexus entity (e.g., TMDs/NE Inc.) outside GRF meetings.

Capital integrity:

No fundraising, brokered deals, or fee discussions in GRF rooms.
Capital outputs are signals and requirements only; the GRA corridor handles any structuring elsewhere.

Security & privacy basics:

Use approved channels and MFA; minimize sensitive data in open sessions.
Recordings only with notice and consent; store in approved repositories.

Enforcement & escalation:

First response: Facilitator/Chair correction in-session.
If unresolved: PNG simulation-based review (documented).
Persistent breach: escalate to BoT; legal disputes fall under agreed arbitration.

Bottom line: Guardrails keep GRF trusted, neutral, and useful—so others can act on its outputs with confidence.

Universal Operating Model Overview

3.1 The monthly cycle (intake → pre-reads → discussion → outputs → hand-offs → follow-through)

Goal: run every track the same way—predictable, neutral, fast—from first submission to verified hand-offs.

A) Intake (T-14 → T-7)

What enters: cases, datasets, draft clauses/policies, pilots, corridor concepts, comms risks.
How: standardized web form or template; submitter declares purpose, owner, desired outcome.
Governance checks (Governance Secretary):
- COI declarations requested/updated.
- Document labels applied: Public / Internal / Restricted.
- Eligibility filter: relevant, decisionable, fits agenda timebox.
Definition of Ready (DoR): item has (i) 1-page summary, (ii) sources listed, (iii) proposed question(s) for decision.

B) Pre-reads & setup (T-6 → T-2)

Science/Methods Lead: Evidence & Assumptions pack (methods used, uncertainty bands, EVPI/gaps).
Standards/Clause Lead: Draft Clause Pack (baseline + proposed deltas; collision notes).
Policy/Regulatory Lead: Jurisdiction map; oversight/remedy pathways.
Capital/Investment Lead: Valuation prompts; covenant hypotheses; data-room asks.
Media/Civic Lead: Narrative risk notes; on/off-record recommendation.
Chair: confirms agenda, desired decisions, and timeboxes; circulates pre-reads.

C) Discussion (T-0; 90 minutes, standard agenda)

Neutral facilitation; evidence-first debate; options under stress; owners + dates captured in-room.

D) Outputs (T+1 → T+5)

Rapporteur: AAR (≤3 pages) drafted from notes and pre-reads; references verified.
Leads: finalize their monthly artifacts (Clause Pack delta; Policy/Investment/Comms notes).
Chair: signs off; Governance Secretary archives and distributes.

E) Hand-offs (by T+5)

Routed to GCRI/TMDs (methods/data), NSF (clauses/registry), GRA (capital corridors), RSBs/NWGs (localization/pilots), New Media (public explainers).
Acknowledgment SLA: recipients confirm receipt & owner within 5 business days.

F) Follow-through (T+14)

15-min checkpoint (Chair + Governance Secretary): status (Done / On-track / At-risk), blockers, next gate.
CB calendar updated; issues escalated per PNG if needed.

Always on guardrails: neutrality; clause licensing; membership ≠ governance; GRF does not own/develop tools; no fundraising or deal-making in GRF sessions.

3.2 Meeting types and openness levels (public discussion, working session, closed technical)

Type	Purpose	Who attends	Inputs	Outputs	When to choose
Public Discussion (default; 90’)	Shape decisions; test options under stress; assign owners/dates	Chair, 5 Leads, Facilitator, Rapporteur, members/guests	Full pre-reads; scenario cards	AAR; Clause/Policy/Investment/Comms notes	Monthly track forum; broad transparency fits
Working Session (60–90’)	Draft artifacts; resolve collisions; prepare hand-offs	Chair + relevant Leads + invited SMEs	Specific sections needing edits	Revised draft(s); decision log	When a public session reveals drafting work remaining
Closed Technical (45–75’)	Handle restricted data, security, or legal sensitivities	Limited SMEs; Governance Secretary present	Restricted materials	Redacted summary; restricted annex; risk log	When labels = Restricted or legal counsel requires privacy

Openness rules

Public Discussion agendas & AARs are publishable unless marked Internal/Restricted sections exist (those are redacted).
Recording only with notice/consent; store recordings in approved repositories; apply labels.
Closed Technical meetings must log a minimal public note (“topic, owner, next gate”) without sensitive details.

3.3 Evidence standards (verifiability, recency, provenance)

A) Verifiability

Every factual claim ties to a source the rapporteur can retrieve (URL/DOI/report ID or dataset hash).
Methods are named (e.g., Bayesian model, SIR, Monte Carlo) with parameter ranges or a link to a methods note.
Where evidence is thin, explicitly mark “Data gap:” and the decision rule used (e.g., precautionary floor).

B) Recency

Default preference: ≤12 months for dynamic topics (markets, policy, climate signals, platforms).
Stable references (laws, standards, foundational science) may be older but must still be the latest controlling text.
If using older data, state why it still governs the decision.

C) Provenance & chain-of-custody

For datasets: note origin, license, version/date, transformations (ETL), and QA/QC status.
For models: version, training window, validation metrics, and known limitations.
For EO/AI outputs: sensor/model ID, timestamp, spatial/temporal resolution, confidence intervals.

D) Uncertainty & decision quality

Show uncertainty bands (e.g., P10/P50/P90) and the main drivers of variance.
Use EVPI (expected value of perfect information) to highlight which data would most reduce uncertainty.
Record assumptions separately from observations.

E) Disallowed / flagged

No anonymous “leaks” as sole evidence; no unverifiable screenshots; no single-source claims for consequential decisions.
Synthetic media requires disclosure and verification steps; deepfake-prone items are treated as Restricted until cleared.

3.4 Output artifacts and minimum quality requirements

All artifacts share:

Neutral tone; plain language; actionable next steps.
Header block: title, track, date, owners, labels (Public/Internal/Restricted), version.
References list (live links/IDs); appendix only when essential.
Clause licensing statement; GRF no-tool-ownership notice.

1) After-Action Report (AAR) — Required every month

Length: ≤3 pages.
Structure: Context → Facts → Uncertainties → Options tested → Decisions → Owners & deadlines.
Minimum quality: references verified; labels applied; decisions phrased as verbs + dates; blockers named with mitigation.

2) Clause Pack Delta (NSF) — If clauses touched

Content: baseline clauses; proposed redlines (definitions, triggers, covenants); collisions & resolutions.
Minimum quality: redline table + clean copy; registry-ready text; responsible editor named; effective/transition dates if applicable.

3) Policy Option Note (RSBs/NWGs) — If policy pathway is in scope

Content: jurisdiction map; oversight/remedy paths; compatibility with existing mandates; pilot candidate(s).
Minimum quality: feasibility rating (Low/Med/High); dependencies; draft timeline; owner in RSB/NWG.

4) Investment Note (GRA) — If capital implications exist

Content: thesis; exposures & metrics; triggers/covenants; diligence hooks; data-room checklist.
Minimum quality: states what evidence would flip the decision (up/down); indicates expected impact/return bands; names corridor lead.

5) Comms Note (New Media/RSBs/NWGs)

Content: on/off-record stance; key messages; early-warning prompts; localization/translation needs; narrative risk table.
Minimum quality: approves quotes/sources; preps public explainer outline; assigns comms owner for each region.

File naming & metadata (all artifacts)

Name: [Track]_[Artifact]_[YYYYMMDD]_vX.Y_Label (e.g., Policy_AAR_20251105_v1.0_Public).
Metadata fields: Track • Region • Owners • Due dates • Related items (intake IDs) • Labels • Version.

Definitions of Done (DoD)

AAR: published to repository; Chair sign-off; recipients notified.
Clause Pack Delta: redline + clean copy uploaded; NSF acknowledgment received.
Policy/Investment/Comms notes: owner assigned in receiving body; acceptance logged (≤5 business days).
Follow-through: T+14 status posted to CB calendar; unresolved risks escalated per PNG.

Reminder: GRF artifacts are clause-licensed; GRF does not own/develop tools; commercial implementation (if any) is routed to the appropriate Nexus entity outside GRF sessions.

Roles & Responsibilities (RACI)

This section defines who does what, who decides, and what “good” looks like for every GRF track. It uses plain RACI: Responsible (does the work), Accountable (final decision/sign-off), Consulted (two-way input), Informed (kept in the loop).

4.1 Track Chair (Leaders Council) — mandate, decision rights, success criteria

Mandate
Steward the track end-to-end—set priorities, keep sessions neutral and evidence-based, and ensure outputs are delivered, handed off, and followed through.

Core duties

Set quarterly priorities and monthly agendas with the Steering Committee.
Approve pre-reads (or send back for fixes).
Preside over sessions; enforce ground rules, timeboxes, and neutrality.
Sign off AAR and track artifacts (Clause Pack delta; Policy/Investment/Comms notes).
Assign owners/dates for actions; escalate blockers; update CB status with Governance Secretary.

Decision rights (A)

Approve/hold: agenda, pre-reads, AAR, and hand-offs.
Order of business; extend/curtail segments (±5 min) without losing required content.
Request recusal in COI situations; adjourn or move items to a Working/Closed Technical session.
Trigger escalation to RSB/GSB/BoT per PNG if risk/compliance issues persist.

Success criteria (KPIs)

Pre-reads issued ≥2 days before T-0; AAR ≤3 pages by T+5.
Receiving bodies acknowledge hand-offs ≤5 business days; T+14 follow-through posted.
≥2 options stress-tested per session; evidence verifiable with sources.
Participation mix targets met; zero unresolved COI/confidentiality incidents.

Delegation & tenure

May appoint an Acting Chair for a specific session.
Honorary, non-fiduciary; 2-year term; annual performance & ethics review.

4.2 Committee Leads (five lanes)

Each Lead owns quality and continuity for their lane—before, during, after the monthly discussion. All Leads are R for their artifacts; the Chair is A for final sign-off.

1) Science/Methods Lead (GCRI liaison)

Purpose: Ensure methods and evidence are sound, transparent, and decision-ready.
Before: Compile Evidence & Assumptions pack (methods, uncertainty bands, EVPI/gaps; sources with provenance).
During: Present the evidence brief; separate observations vs assumptions; flag limits.
After: Log data/method tasks to GCRI/TMDs; confirm owners/dates.
Outputs: Evidence pack; annexed parameter ranges/validation notes.
Quality bar: All claims sourced; uncertainty bands stated (e.g., P10/P50/P90); “Data gaps” explicitly listed.

2) Standards/Clause Lead (NSF liaison)

Purpose: Convert decisions into clause-ready text; maintain standards integrity.
Before: Draft Clause Pack (baseline + proposed deltas; collision notes).
During: Walk through redlines; highlight definitional impacts/triggers/covenants.
After: Produce Clause Pack delta (redline + clean); submit to NSF registry; capture feedback.
Outputs: Clause Pack delta; collision log.
Quality bar: Registry-ready language; collisions resolved or flagged with options.

3) Policy/Regulatory Lead (RSB/NWG liaison)

Purpose: Map options to jurisdictions; define oversight/remedy paths and pilotability.
Before: Build Jurisdiction Map; identify legal dependencies/conflicts.
During: Present policy pathways; propose oversight/remedy mechanisms.
After: Draft Policy Option Note; route to RSBs/NWGs with pilot prompts; collect localization feedback.
Outputs: Policy Option Note; pilot checklist.
Quality bar: Feasibility rating; dependencies; owner named in recipient body.

4) Capital/Investment Lead (GRA liaison)

Purpose: Translate risk insights into investable signals and accountable covenants (no deal-making in GRF).
Before: Prepare valuation prompts; hypothesize triggers/covenants; data-room checklist.
During: Present exposure/probability/impact; covenant ideas; diligence hooks.
After: Draft Investment Note; hand off to GRA corridors; log acceptance.
Outputs: Investment Note; ESG/legal checklist.
Quality bar: Clear thesis; metrics; triggers; “what evidence flips the decision” statement.

5) Media/Civic Foresight Lead (New Media liaison)

Purpose: Protect narrative integrity and public trust; prepare early-warning messaging.
Before: Draft narrative-risk notes; recommend on/off-record posture.
During: Present comms risks; propose EWI messages; identify localization needs.
After: Deliver Comms Note; coordinate explainers with New Media/RSBs/NWGs.
Outputs: Comms Note; Narrative Risk Table; public explainer outline.
Quality bar: Source-checked statements; approvals captured; redactions honored.

4.3 Facilitator & Rapporteur — session delivery and records

Facilitator

Mandate: Run the room—neutral, on time, on scope.
Duties:

Enforce agenda/timeboxes; rotate speaking; stop grandstanding.
Keep focus on evidence → options → decisions; park tangents.
Call COI/label reminders; propose Working/Closed sessions if needed.
Authority: May pause a segment for process or safety; escalate to Chair on breaches.

Rapporteur

Mandate: Create the authoritative record.
Duties:

Capture facts, uncertainties, options, decisions, owners, deadlines.
Verify references; apply labels; draft AAR ≤3 pages by T+5.
Append acceptance criteria; list blockers; distribute per label.
Authority: May request clarifications from speakers; may flag unverifiable claims.

4.4 Governance Secretary — COI, confidentiality labels, archival, CB calendar updates

Mandate: Compliance backbone for the track.
Duties:

Run COI declarations/recusals; maintain COI log.
Apply document labels (Public/Internal/Restricted); ensure storage in approved repositories.
Maintain the official record: attendance, agenda, pre-reads, AAR, artifacts, sign-offs.
File and track hand-off acknowledgments (≤5 business days SLA).
Update the CB master calendar (T-0 schedule, T+5 deliveries, T+14 status).
Manage access permissions; redaction workflow; incident logging & notifications.
Authority: May halt distribution that violates labeling/COI rules; elevates unresolved incidents to Chair → RSB/GSB/BoT per PNG.

4.5 Advisors, Fellows, Observers — how they contribute

Advisors (SMEs invited by Chair/Leads)

Consulted on evidence, clauses, policy, capital, or comms.
Provide memos/data; attend portions of sessions as needed.
No sign-off authority; disclose COI; follow labels.

Fellows (recognized contributors)

Responsible for discrete tasks (e.g., annex drafting, replication checks).
Eligible for rotating seats on the Steering Committee; potential path to Lead roles.
Must meet artifact quality bars and timelines.

Observers (learners/partners)

Informed; may comment in Q&A segments at Chair’s discretion.
Must follow ground rules, labels, and COI norms.

4.6 RACI matrix (who is Responsible, Accountable, Consulted, Informed)

Roles (columns):

Chair (CH)
Science/Methods Lead (SCI)
Standards/Clause Lead (STD)
Policy/Regulatory Lead (POL)
Capital/Investment Lead (CAP)
Media/Civic Lead (MED)
Facilitator (FAC)
Rapporteur (RAP)
Governance Secretary (SEC)
Advisors/Fellows (ADV/FEL)
RSB/NWG Focal Points (RSB/NWG)
Central Bureau Scheduler (CB)

Activity / Deliverable	CH	SCI	STD	POL	CAP	MED	FAC	RAP	SEC	ADV/FEL	RSB/NWG	CB
1. Set quarterly priorities	A	C	C	C	C	C	I	I	I	C	C	R
2. Approve monthly agenda	A	C	C	C	C	C	C	I	I	I	I	R
3. Intake triage & eligibility	A	C	C	C	C	C	I	I	R	I	I	I
4. COI checks & labels	I	I	I	I	I	I	I	I	R/A	I	I	I
5. Pre-reads: Evidence & Assumptions	A	R	C	C	C	C	I	I	I	C	I	I
6. Pre-reads: Clause Pack (draft)	A	C	R	C	C	C	I	I	I	C	I	I
7. Pre-reads: Policy map	A	C	C	R	C	C	I	I	I	C	C	I
8. Pre-reads: Capital prompts	A	C	C	C	R	C	I	I	I	C	I	I
9. Pre-reads: Comms risks	A	C	C	C	C	R	I	I	I	C	C	I
10. Run session (T-0)	A	C	C	C	C	C	R	I	I	I	I	I
11. Draft AAR (≤3 pp)	A	C	C	C	C	C	I	R	I	C	C	I
12. Sign-off AAR	A	C	C	C	C	C	I	R	I	I	I	I
13. Clause Pack delta	A	C	R	C	C	C	I	I	I	C	I	I
14. Policy Option Note	A	C	C	R	C	C	I	I	I	C	C/R	I
15. Investment Note	A	C	C	C	R	C	I	I	I	C	C	I
16. Comms Note & explainer	A	C	C	C	C	R	I	I	I	C	C/R	I
17. Archive & access control	I	I	I	I	I	I	I	I	R/A	I	I	I
18. Handoffs to recipients	A	C	C	C	C	C	I	I	R	I	C/A	I
19. Acknowledgment tracking (≤5 days)	I	I	I	I	I	I	I	I	R/A	I	C	I
20. T+14 follow-through update	A	C	C	C	C	C	I	I	R	I	C	C
21. Escalation (PNG)	A	C	C	C	C	C	I	I	C	I	C	C

Legend: A = Accountable; R = Responsible; C = Consulted; I = Informed.
Notes:

The Chair is A for agenda, artifacts, and escalations; Leads are R for their lane’s content.
Governance Secretary is R/A for COI, labels, archival, acknowledgments, and CB updates.
RSB/NWG become C/A for localization deliverables they own; CB is R/C for calendaring and cross-track balance.

Standing guardrails for all roles

Neutrality & clause compliance at all times.
Membership ≠ governance; leadership is honorary, non-fiduciary.
GRF does not own/develop tools; commercial implementation routes outside GRF.
Respect labels (Public/Internal/Restricted); disclose COI; use approved channels and MFA.

Leadership & Access

This section defines who can lead, how leaders are appointed and renewed, how performance and ethics are reviewed, how removal works, and how members progress toward leadership. It is written to be clear, fair, and consistent across all GRF tracks.

5.1 Eligibility & appointment (invitation/merit)

Principles

Leadership at GRF is honorary and non-fiduciary.
Appointments are based on merit, documented contribution, and neutrality—never on payment, sponsorship, or status.
All candidates must pass COI (conflict-of-interest) and confidentiality checks.

Baseline eligibility (all leadership roles)

Track record: Documented, high-quality contributions across ≥2 monthly cycles in the past 9 months (e.g., evidence notes, facilitation support, artifact drafting).
Quality & reliability: On-time delivery; acceptance of hand-offs by recipients; zero unresolved COI or labeling incidents.
Standards literacy: Demonstrated understanding of clause licensing, document labels, and evidence standards.
Neutrality & conduct: Consistent adherence to ground rules and non-advocacy posture.

Additional role-specific signals

Committee Lead: Proven authorship of the relevant artifact type (e.g., Clause Pack deltas, Policy Option Notes).
Track Chair: Successful steering of a working session or acting-chair stint; strong KPI results and cross-track collaboration.

Nomination & appointment process

Nomination: Any two current leaders (Chair/Lead/Trustee delegate) submit a short nomination citing evidence of eligibility.
Screening: Governance Secretary runs COI & label compliance checks; confirms contribution record.
Review panel: Chair + two Committee Leads (or Chairs’ Council for Chair appointments) interview the nominee on neutrality, evidence standards, and guardrails.
Recommendation: Panel issues a written recommendation (approve/hold/decline) with conditions if any.
Approval: Board of Trustees (or delegated Trustee) approves appointment; Governance Secretariat issues appointment letter with term dates.
Onboarding: Role handover, access rights, and entry in the CB master calendar.

Probation (optional)

For first-time leaders, a one-cycle probation may be used; full appointment follows satisfactory performance.

5.2 Terms (2-year), renewals, succession, temporary delegation

Term length

Standard term is 2 years from effective date (shown in appointment letter).

Renewals

Triggered 90 days before term end.
Inputs: KPI history, artifact quality, compliance record, peer feedback, and recipient (GCRI/NSF/GRA/RSB/NWG) satisfaction.
Decision: Chair (for Leads) or Chairs’ Council (for Chair) recommends renew / rotate / extend short-term; Trustee approves.

Succession planning

Every leadership seat maintains a named successor (shadow/vice) documented in the CB calendar.
Successors should have completed the leadership bootcamp and delivered at least one artifact of the lane they would inherit.

Temporary delegation

Allowed when a leader is unavailable for a specific cycle (travel, conflict, illness).
Chair may appoint an Acting Lead; Chairs’ Council may appoint an Acting Chair for one cycle.
Governance Secretary records the delegation and restores original permissions after the cycle.

Early rotation

Leaders may request rotation after 12 months with 30-day notice; a successor is seated to avoid service gaps.

5.3 Annual performance & ethics reviews

Purpose

Reinforce quality, neutrality, inclusion, and predictable delivery; not punitive—development first.

Inputs

KPI dashboard (participation mix, evidence quality, options tested, hand-off acceptance, T+14 follow-through, incidents).
Artifact audits (sample of AARs, Clause Pack deltas, Policy/Investment/Comms notes).
360 feedback (peers, recipients, Governance Secretary).
Compliance log (COI, labeling, incident resolutions).

Scoring bands

Exceeds (consistently high KPIs; artifacts exemplary; mentorship provided).
Meets (stable KPIs; artifacts meet bars; no unresolved issues).
Watch (inconsistent delivery or minor incidents—development plan required).
At Risk (material issues—probation or rotation considered).

Outcomes

Renew as-is; Renew with development goals; Rotate with mentoring role; Probation for 1 cycle; Recommend removal (see 5.4).

Documentation

Governance Secretary files the review summary and updates the CB calendar (status note and any actions).

5.4 Removal for cause (misconduct, inactivity, COI breach)

Grounds for removal

Misconduct: harassment, discrimination, intimidation, retaliation, misuse of confidential information.
Inactivity: missed deliverables across ≥2 cycles without delegation; recurring tardiness that blocks hand-offs.
COI breach: undisclosed conflicts, failure to recuse, or attempts to influence outcomes for private gain.
Guardrail violations: advocacy in place of neutrality; deal-making/fundraising inside GRF sessions; tool-ownership claims.

Due-process steps

Notice: Written summary of alleged issues; evidence attached; opportunity to respond (7 calendar days).
Panel review: Chair + two uninvolved leaders + Governance Secretary evaluate facts; may consult legal/ethics advisor.
Decision: Written outcome—no action / corrective plan / probation (1 cycle) / removal.
Appeal: One appeal to the Trustee delegate; if unresolved, PNG simulation review; legal disputes default to the agreed arbitration venue.

Effects of removal

Access revoked; calendar updated; successor seated.
Record preserved with minimal facts (reason category, effective date).

5.5 Membership vs governance (paths to elevation)

Bright line

Membership ≠ governance. Membership grants participation rights in public discussions (subject to COI and labels). It does not grant fiduciary power or leadership seats.

Participation rights (members)

Attend monthly public discussions; submit items to intake; contribute evidence; comment during Q&A; review public drafts.

Paths to elevation (merit-based)

Contributor → Fellow
- Deliver ≥2 high-quality contributions (evidence notes, drafting support, facilitation assists) in 9 months.
- Complete COI/confidentiality training; pass compliance check.
- Fellowship is recognition; still non-governance, but unlocks rotating seats on Steering Committees.
Fellow → Committee Lead
- Demonstrate authorship of lane artifacts across ≥2 cycles with on-time hand-off acceptance.
- Two nominations; panel interview; Trustee approval.
- Serve 2-year term; maintain KPIs; mentor at least one Fellow.
Committee Lead → Track Chair
- Prior acting-chair experience or orchestration of cross-lane delivery with strong KPIs.
- Chairs’ Council recommendation; Trustee approval.
- Steward the track; uphold neutrality and guardrails; manage escalations.

Institutional delegates

Institutions may designate delegates to contribute; designation does not create governance rights. Delegates follow the same merit path.

What never qualifies for elevation

Sponsorships, donations, fees, titles, or external rank.
Attempts to broker deals, lobby in-room, or claim tool ownership within GRF proceedings.

Simple checklist for candidates (self-assessment)

Two cycles of documented, on-time contributions.
Zero unresolved COI/labeling incidents.
Familiar with clause licensing and evidence standards.
Endorsements from two leaders based on observed work.
Comfortable enforcing neutrality and session guardrails.

Standing guardrails (apply to all of Section 5)

Leadership is honorary, non-fiduciary, time-bound, and performance-reviewed.
GRF sessions are neutral spaces; no fundraising/deal-making; no tool ownership.
All leaders and aspirants must follow COI, confidentiality, document-labeling, and approved-channels/MFA requirements.

Ethics, COI & Conduct

This section sets the ground rules that keep GRF spaces neutral, safe, lawful, and useful. It tells you what to do, what not to do, how to declare conflicts, how to label and handle information, and how to raise concerns without fear of retaliation.

6.1 Code of conduct (do’s/don’ts with examples)

Principles (memorize these 5):

Neutrality — ideas compete, people don’t.
Truthfulness — cite sources; separate facts from assumptions.
Respect — no harassment, intimidation, or personal attacks.
Safety & Privacy — protect people and data; follow labels.
Integrity — no lobbying, deal-making, or tool-ownership claims in GRF rooms.

Do (examples):

Prepare: read pre-reads; bring sources you can share.
Disclose: state any conflict before speaking on an item.
Stick to time: respect the agenda/timeboxes; let others speak.
Use approved channels: meeting platforms, shared drives, and email groups designated by the Governance Secretary.
Label & cite: mark docs Public/Internal/Restricted; include references and dates.
Challenge ideas, not people: “The assumption on exposure seems optimistic given [source].”

Don’t (examples):

No lobbying/deals: “We can finance this if you choose our vendor” (not allowed).
No private influence: DMing participants to sway outcomes during a session.
No unverified claims: screenshots with no provenance; rumors; “a friend at X said…”
No data spills: forwarding Restricted files outside the distribution.
No harassment or bias: slurs, stereotyping, unwanted contact, belittling.
No undisclosed AI output: pasting model-generated text or figures without checking and citing sources (and noting “AI-assisted” if material).

Meeting etiquette (remote & in-person):

Cameras optional; mic off when not speaking; use the raised-hand queue.
No recording unless announced before the session and approved by the Chair & Governance Secretary.
Wear “no-photo” badges where provided; ask consent before photos/quotes.

If in doubt: ask the Governance Secretary before you act.

6.2 Conflicts of interest — declaration, recusal, record-keeping

What counts as a conflict (examples):

Financial: equity/options, paid advisory, grants, royalties, performance bonuses linked to the topic.
Professional/Institutional: board roles, employment, procurement involvement, supervision relationships.
Intellectual: patents/IP claims, authorship disputes, strong prior public advocacy on the specific item.
Personal: close family/partner with a stake; recent (<24 months) employment or funding from a party in scope.

When to declare:

Annually: complete/update the COI form (Section 22 templates).
At intake: declare conflicts on each submitted item.
In-room: verbally declare before speaking to a conflicted item or when a new conflict becomes apparent.
Within 7 days: update the written record if circumstances change.

Recusal options (Chair decides with the Secretary):

Full recusal: no participation on that item (you may leave or be muted).
Partial recusal: you may provide factual clarifications but do not argue for outcomes or vote/decide.
Mitigated participation: disclose conflict; operate under extra scrutiny (used for scarce expertise only).

Record-keeping:

Governance Secretary keeps a COI log (who, what, nature, decision, date).
Retention: 6 years (or longer if legal hold).
Public materials are redacted; internal records remain accessible to Trustees and relevant reviewers.

Gifts & hospitality:

Decline gifts; if unavoidable, declare anything over a nominal value (rule of thumb: >USD 100) within 7 days.
Travel/funding to attend GRF must be neutral and pre-cleared; no vendor-sponsored junkets.

Breaches (examples & responses):

Undeclared equity in a discussed vendor → removal from item; written warning; potential role review.
Recusal ignored → session pause; escalation to ethics review; possible suspension.

6.3 Confidentiality & document labeling (Public / Internal / Restricted)

Why labeling matters: It signals who can see a document and how it must be handled. Labels apply to files, slides, notes, recordings, and chat transcripts.

Labels (choose one):

Public — safe to publish/share broadly. Examples: public AAR, press lines, public explainer.
Internal — share within the GRF distribution list; not for public release. Examples: working drafts, unfinalized data.
Restricted — need-to-know only; may include sensitive data, security topics, personal data, or legal exposure. Examples: sanctions/PEP checks, unpublished IP details, confidential contract terms.

How to label (must do all three):

File name: [Track]_[Artifact]_[YYYYMMDD]_vX.Y_[Label]
Header/Footer: label + date + owner (e.g., “Restricted — 2025-08-24 — Owner: Policy Lead”).
Repo metadata: set the label field and access controls in the approved repository.

Handling rules by label:

Action	Public	Internal	Restricted
Share outside GRF	Allowed	Chair/Secretary approval	Not allowed
Email forwarding	Allowed with context	Allowed inside distro	No (link with access controls only)
Storage location	Approved repo	Approved repo	Restricted folder with access list
Recording	Allowed with notice	Allowed with notice	By exception; encrypted; retention limits
Redaction	Not needed	Remove sensitive lines before external use	Required; create public summary

Data minimization & security:

Share the minimum data needed; anonymize when feasible.
Use MFA on all accounts; no personal cloud drives for GRF work.
Encrypt Restricted files at rest and in transit (platform defaults or password-protected archives if needed).

Breach response (timeline):

Immediate: stop sharing; notify the Governance Secretary.
<24 hours: Secretary assesses scope; informs Chair and, if needed, legal/compliance.
<5 business days: remediation plan (revoke access, rotate links, notify affected parties, update artifacts).
Record: log the incident and outcome; include in quarterly review.

6.4 Anti-harassment, safeguarding, whistleblowing

Zero tolerance: GRF prohibits harassment, discrimination, bullying, retaliation, doxxing, and threats—online or in person.

Harassment includes (non-exhaustive):

Offensive comments, slurs, or stereotypes about identity or beliefs.
Unwanted sexual attention or contact; stalking.
Deliberate intimidation; shouting down; targeted humiliation.
Repeated interruptions after warnings; refusal to follow facilitation.

Safeguarding (people & venues):

Respect no-photo/recording preferences.
Physical events: identify emergency exits, first-aid, venue security; display an on-site Duty of Care contact.
Remote events: moderators may mute or remove participants for safety/compliance breaches.
Sensitive cohorts (e.g., minors or vulnerable groups): obtain guardian/org consent and apply Restricted handling.

Whistleblowing (protected disclosures):

What you can report: harassment; safety issues; COI breaches; data misuse; fraud; serious policy violations.
How to report:
- In-session: tell the Facilitator/Chair (they pause and call the Secretary).
- Outside session: email the Governance Secretary or use the anonymous form (Sec. 22 templates).
Timelines:
- Acknowledgment within 2 business days.
- Triage within 5 business days (assign investigator; define scope).
- Resolution target ≤30 days (complex cases may need more; reporter kept informed).
Protections:
- No retaliation—discipline up to removal for those who retaliate.
- Identities kept confidential to the maximum extent practicable.
- You may request an independent reviewer (Trustee delegate) for sensitive cases.

Investigation outcomes (examples):

No breach: close with reasons and guidance.
Corrective action: apology, training, monitored participation.
Restrictions: topic bans, temporary suspension, removal from role.
Serious breach: termination of access/role; referral to arbitration or authorities as required.

Bystander guidance (what to do if you witness an issue):

Signal the Facilitator in chat or raise hand; keep notes of what you saw/heard.
Support the affected person (private message or after the session).
Do not escalate publicly with accusations—route through the Secretary or Chair.

Quick reference (paste on the last slide of every deck)

Declare COI before speaking on an item; recuse if asked.
Label everything (Public/Internal/Restricted) and share accordingly.
Cite sources; mark AI-assisted content.
No lobbying/deals/tools in GRF rooms.
Zero harassment/retaliation; report issues safely.
Ask the Governance Secretary when unsure.

Security, Privacy & Digital Hygiene

This section keeps GRF work safe, private, and compliant without slowing you down. Follow these rules every time you communicate, share files, or handle data for GRF tracks.

7.1 Approved communication channels and accounts

Principles

Use only GRF-approved channels and work accounts for GRF work.
No forwarding to personal inboxes, drives, or messengers. Ever.

Approved channels (categories & examples)

Email & Calendar — GRF/GCRI organizational email and the CB master calendar (managed by the Governance Secretariat).
Meetings — GRF-approved video platform with waiting room/lobby, meeting passcodes, and host controls enabled by default.
Chat — GRF-approved team chat (track workspaces; governance channels for Chairs/Secretariat).
Documents — GRF-approved document repository (versioned, permissioned, with labels: Public / Internal / Restricted).
Registries & Standards — NSF/Clause registries (read/write only for authorized editors).
Data & Code — Approved research/analytics repositories (GCRI/TMDs), never personal Git or public buckets.
Issue & Task Tracking — GRF-approved tracker (for artifact tasks, not for Restricted content unless the space is approved for Restricted).

Account rules

Access GRF systems only with your provisioned identity (no shared accounts).
Sponsoring institutions may federate SSO; if they cannot, use GRF-issued accounts.
Deactivate access within 24 hours of role change/exit (Governance Secretary + IT).

7.2 MFA, device standards, link-sharing rules

Multi-Factor Authentication (MFA) — mandatory

Require MFA on email, chat, repos, meetings, and registries.
Allowed factors: app-based TOTP/push or hardware keys; no SMS where avoidable.

Device standards (bring-your-own or GRF-issued)

OS support: latest stable OS; security patches applied within 7 days (critical within 48h).
Disk encryption: enabled (BitLocker/FileVault/Linux LUKS or mobile equivalents).
Screen lock: auto-lock ≤ 5 minutes; strong passcode/biometric.
Endpoint protection: active (AV/EDR); firewall on.
Backups: encrypted; no syncing Restricted data to personal cloud.
Separation: keep GRF work in a dedicated profile/account; disable clipboard sync between personal and work if possible.

Link-sharing & permissions

Share links, not attachments, except for Public artifacts.
Default permission = view-only; add download/print disabled, watermark if available.
Require sign-in; no “anyone with the link” for Internal/Restricted.
Expiry for links to Internal (≤90 days) and Restricted (≤30 days).
Meeting links: always with passcode + waiting room; host-only screen share for Restricted sessions.

AI/automation tools

Do not paste Restricted content into external AI tools.
Declare AI-assisted content when material; verify facts/sources before use.
Use only approved internal assistants for document drafting/summarization.

Passwords

Unique per system; length ≥ 12; password manager recommended.
Never share credentials; use delegated access if someone needs temporary control.

7.3 Data minimization & privacy notice

(what we collect, why, how we protect)

What we collect (minimum necessary)

Identity & role: name, affiliation, email, track role (Chair/Lead/etc.).
Participation metadata: attendance, agenda items touched, speaking role.
Governance: COI declarations, document labels, approvals/sign-offs.
Artifacts: AARs, Clause Pack deltas, Policy/Investment/Comms notes (and version history).
Recordings/transcripts: only with notice and label; not default for Restricted.
Operational telemetry: access logs (who viewed/edited what and when).

Why we collect

To run neutral, auditable processes; manage hand-offs; satisfy governance and standards requirements (PNG, NSF registry); protect participants and data.

How we protect

Access control: least-privilege, role-based; periodic access reviews.
Encryption: in transit (TLS) and at rest (platform native); extra encryption for Restricted exports.
Segregation: separate storage spaces for Public/Internal/Restricted.
Logging & audit: immutable logs for key repositories; quarterly review.
Vendor due diligence: DPAs/SCCs as applicable; security reviews for all processors.

Retention (default)

Public/Internal artifacts: 6 years.
Restricted artifacts: 2 years (or project term + 1 year), unless legal hold or registry rule requires longer.
COI records: 6 years from last activity.
Recordings: Public/Internal ≤ 12 months; Restricted by exception (define retention at creation).

Your rights (where applicable)

Access/correct your personal data; request deletion of non-record artifacts where it does not conflict with governance/legal retention.
Direct questions or requests to the Governance Secretary (who coordinates with privacy/compliance).

7.4 Incident reporting & response timelines

What is an incident?
Any loss, alteration, or unauthorized disclosure of GRF data; account compromise; malware/ransomware; mis-sharing of Internal/Restricted materials; meeting intrusion; or suspected espionage/social engineering.

Severity levels & SLAs

Severity	Examples	Report within	Initial response	Containment target	Full report
SEV-1 (Critical)	Lost/stolen device with Restricted data; active account compromise; leaked Restricted artifact; meeting hijack with sensitive content	1 hour	1 hour (ack & triage)	4 hours	72 hours
SEV-2 (High)	Mis-shared Internal content; suspicious login attempts; malware blocked by EDR	4 hours	8 hours	24 hours	5 business days
SEV-3 (Moderate/Low)	Policy deviation without data exposure; mislabeled doc caught pre-share	1 business day	2 business days	5 business days	10 business days

How to report (choose one, then follow up by email)

In session: notify Facilitator/Chair → they pause and ping the Governance Secretary immediately.
Out of session: email Governance Secretary (subject: “Security Incident [SEV?]”) or use the incident form (Sec. 22 templates).

Response playbook (summary)

Acknowledge & classify (Secretary + Security/IT) → set severity & comms channel.
Contain — revoke access, kill sessions, rotate credentials/keys, quarantine files/devices, disable links.
Investigate — scope affected accounts/data, timeline, root cause; preserve logs.
Notify — Chairs/CB, affected recipients; if required, Trustees, regulators, or partners (per DPA/contract).
Remediate — fix configs, patch systems, redaction/recall, retrain as needed.
Recover — restore from backups; verify integrity; re-enable access.
Report & learn — deliver incident report/post-mortem by SLA; file actions into the CB calendar; track to closure.

Golden rules

Do not delete evidence (emails/logs/files); isolation > deletion.
Do not contact attackers; route all comms through Governance Secretary/Security.
Do change your passwords and revoke tokens if you suspect compromise.
Do assume forwarders and synced devices received anything mis-shared—contain broadly, then narrow.

Quick checklist (pin to your desktop)

MFA on; device encrypted; screen locks in 5 minutes.
Share links with least privilege; label everything.
Never paste Restricted into external AI.
Report incidents fast; don’t clean up quietly.
When unsure, ask the Governance Secretary.

Monthly Cadence (Repeatable Playbook)

This playbook runs every track, every month, the same way—predictable, neutral, fast. “T-0” is the public discussion. All times are relative to T-0.

8.1 T-14 → T-7: Intake window

(cases / datasets / policy drafts / pilots), COI screening, doc labels

What opens

Standard Intake Form (Sec. 22 templates) collects: title, 1-page summary, owner, desired decision/question, sources, proposed label (Public / Internal / Restricted), declared COI, and target hand-off(s).

Triage (Governance Secretary + Chair)

Eligibility: on-topic, decisionable in 90 minutes, sources listed, owner identified.
Labeling: confirm Public / Internal / Restricted; apply to all files and the intake record.
COI: request/update declarations; pre-flag recusals.
Prioritization: score (impact, urgency, readiness, cross-track dependencies).

Definition of Ready (DoR) — must pass to enter the agenda

1-page summary with clear question(s) for the room.
Cited sources (links/IDs) + dataset/model provenance if applicable.
Named presenter and recipient(s) for hand-off.
Proposed label + COI declarations on file.

Outputs

Draft agenda (items + timeboxes)
Intake log updated (status: Accepted / Hold / Redirect)

Comms

Confirm to submitters (Accepted/Hold/Redirect).
Share intake status with Committee Leads.

8.2 T-6 → T-2: Pre-reads & setup

(pre-reads, scenario cards, clause pack draft, collision checks, valuation prompts, comms risks)

Lane deliverables

Science/Methods Lead: Evidence & Assumptions Pack (methods; uncertainty bands; EVPI/gaps; provenance).
Standards/Clause Lead: Clause Pack (draft) (baseline + proposed redlines; collision notes).
Policy/Regulatory Lead: Jurisdiction Map (overlaps, dependencies; oversight/remedy paths).
Capital/Investment Lead: Valuation Prompts (exposure, metrics; covenant hypotheses; data-room asks).
Media/Civic Lead: Narrative Risk Note (EWI messages; mis/disinformation risks; on/off-record recommendation).

Chair & Secretary

Finalize run-of-show (agenda, timeboxes, presenters).
Apply/verify labels on all files; ensure COI notes are attached.
Distribute pre-reads to the track list (D-2 minimum) with access controls; log acknowledgments.
Accessibility: confirm captions/interpretation if requested; prepare redacted packs if needed.

Freeze

At T-2, agenda and pre-reads freeze. New material → Working Session or next month.

8.3 T-0: 90-minute public discussion

(standard agenda)

Segment	Time	Owner	Outcome
1) Opening & purpose	5’	Chair	Decision questions; ground rules; label reminder; COI recap
2) Evidence & assumptions	15’	Science Lead	Facts vs assumptions; uncertainty bands; EVPI/gaps
3) Options under stress	20’	Facilitator	2–4 options tested; trade-offs; “no-regrets” actions
4) Policy & clauses	15’	Policy + Standards	Jurisdiction map; oversight/remedies; candidate clauses/conflicts
5) Capital implications	15’	Capital Lead	Exposure, triggers/covenants, diligence hooks
6) Narrative & comms	10’	Media Lead	EWI messaging; narrative risks; on/off-record posture
7) Decisions & owners	10’	Chair + Rapporteur	Who does what by when; hand-off recipients; blockers & next gates

Facilitation rules

Neutral moderation; rotate speakers; keep to timeboxes.
Park tangents; move sensitive details to Closed Technical if label demands.
No fundraising, brokering, or “tool-ownership” claims.
Rapporteur captures decisions as verbs + dates + named owners.

Record

Attendance, labels, recusals, incidents (if any). Recording only if noticed and aligned with the label.

8.4 T+1 → T+5: AAR issuance & artifact packaging

Rapporteur (R)

Draft AAR (≤3 pages) by T+3: Context → Facts → Uncertainties → Options → Decisions → Owners/Dates → Blockers.
Verify references; apply label; route to Chair for sign-off.

Committee Leads (R)

Standards/Clause: Clause Pack Delta (redline + clean; collision log).
Policy/Regulatory: Policy Option Note (readiness, dependencies, pilot prompts).
Capital/Investment: Investment Note (thesis, metrics, triggers, diligence asks, data-room list).
Media/Civic: Comms Note (on/off-record; key messages; localization plan; narrative risk table).

Chair (A)

Sign off AAR + artifacts or return with fixes (24h).
Confirm recipient owners and due dates.

Governance Secretary (R/A)

Archive (versioned; labeled) in approved repo.
Distribute to recipients; request acknowledgment within 5 business days.
Update intake record and artifact links.
If any artifact is Restricted, create a Public/Internal summary.

Definition of Done (per artifact)

Neutral tone; complete headers; labels; live references.
Clear owners & deadlines; acceptance criteria noted.
Stored in the correct repository with metadata; links shared (no open attachments for Internal/Restricted).

8.5 T+14: Follow-through checkpoint & CB status

10–15 minute checkpoint (Chair + Governance Secretary; Leads as needed)

Review hand-off acknowledgments (met/missed).
Check owner progress vs deadlines; update risks/blockers.
Decide escalations (Working Session, RSB/GSB attention, Closed Technical).
Refresh CB master calendar: status per item (Done / On-track / At-risk / Blocked).

Status definitions

Done: Acknowledged + first milestone met or closed.
On-track: Acknowledged; milestones on schedule; no critical risks.
At-risk: Acknowledged; slippage or unresolved dependency—mitigation planned.
Blocked: No acknowledgment or critical dependency unmet—escalate.

KPI tick-up (for Chair’s monthly report)

Pre-reads timeliness, options tested, evidence quality, hand-off acceptance rate, T+14 status mix, incidents (COI/labeling/comms).

Comms

Send a brief track update to the distribution list (1 paragraph + links); provide a public snippet if any artifacts are labeled Public.

Automation hints

Calendar holds for T-6, T-2, T+1, T+5, T+14.
Auto-reminders to Leads for lane deliverables; auto-SLA pings to recipients for acknowledgments.
Pre-filled AAR and note templates (Sec. 22) with track/date/label metadata baked in.

Always-on guardrails: neutrality; clause licensing; membership ≠ governance; GRF does not own/develop tools; no fundraising/deal-making in GRF sessions; respect labels & COI at every step.

Standard 90-Minute Agenda (With Objectives)

Purpose: a single, time-boxed format for all tracks that keeps debate neutral, evidence-first, and action-oriented.
Guardrails (always on): neutrality; COI declarations/recusals; document labels (Public / Internal / Restricted); no fundraising or tool-ownership claims; membership ≠ governance.

Run-of-show (90 minutes total)

Opening & purpose — 5’
Evidence brief & scenario assumptions — 15’
Options under stress — 20’
Policy pathways & clause implications — 15’
Capital implications & risk pricing — 15’
Narrative & comms risks — 10’
Decisions, owners, deadlines — 10’

9.1 Opening & purpose (Chair) — 5 minutes

Objective: align everyone on the decision questions, rules, and scope.
Inputs: final agenda; COI log; labels on all pre-reads.
Script (concise):

“Today’s decision questions are: Q1, Q2.”
“Labels in force: [Public/Internal/Restricted]. COIs to declare?” (pause)
“We will keep to timeboxes; we test options, not people.”

Outputs to capture: revised decision questions (if any); COI declarations/recusals; confirmation of label.

Success signals: crisp problem framing; any recusals documented before content begins.

9.2 Evidence brief & scenario assumptions (Science) — 15 minutes

Objective: establish a shared factual baseline and explicit assumptions.
Inputs: Evidence & Assumptions Pack (methods, uncertainty bands, EVPI/gaps).
Flow:

Facts (5’): what we observed; sources & provenance.
Assumptions (5’): what we are treating as true; parameter ranges; model limits.
Uncertainty (5’): P10/P50/P90 or similar; top drivers; EVPI—what new data would most help.

Prompts:

“Which claim lacks a verifiable source?”
“What single assumption, if wrong, flips our preferred option?”

Outputs: list of assumptions; uncertainty bands; EVPI items for follow-up.

Success signals: zero orphan claims; uncertainties explicit, not implied.

9.3 Options under stress (Facilitator) — 20 minutes

Objective: compare 2–4 credible options against the same stressors to surface trade-offs and “no-regrets” moves.
Inputs: pre-read scenario cards; stressors/thresholds.
Flow:

Set stressors (3’): e.g., time, budget, legal constraint, failure mode, equity impact.
Option walk-through (12’): 3–4 minutes per option: intended effect → stress response → risks.
Compare & cluster (5’): what’s dominated, what’s robust; identify no-regrets steps.

Prompts:

“Under X shock, which option fails first and why?”
“What could we remove to reduce complexity without losing effect?”

Outputs: ranked/clustered options; noted no-regrets items; parked items (for Working Session).

Success signals: at least two options genuinely tested; one no-regrets action identified.

9.4 Policy pathways & clause implications (Policy + Standards) — 15 minutes

Objective: map favored options into enforceable policy paths and clause text; flag collisions.
Inputs: Jurisdiction Map; Clause Pack (draft).
Flow:

Policy path (7’): where this can legally live; oversight/remedy; dependencies.
Clause impacts (6’): definitions/triggers/covenants; redlines vs baseline; known collisions.
Next gate (2’): who drafts what by when.

Prompts:

“Which clause is most likely to collide across jurisdictions?”
“What oversight mechanism prevents misuse of this power?”

Outputs: list of clause deltas; policy path options; owners for drafting.

Success signals: at least one viable policy route with a named drafting owner and date.

9.5 Capital implications & risk pricing (Capital) — 15 minutes

Objective: turn risk insights into investable signals and accountable covenants (no deals in GRF).
Inputs: valuation prompts; exposure/impact metrics; covenant hypotheses.
Flow:

Exposure picture (5’): probability × impact; key metrics; scenario range.
Covenants/triggers (7’): what to monitor; when to act; verification hooks.
Diligence asks (3’): data-room checklist; who provides what by when.

Prompts:

“What single metric best predicts failure here?”
“What evidence would flip our investment stance?”

Outputs: draft trigger/covenant set; diligence checklist; corridor lead for hand-off.

Success signals: clear, measurable triggers; named capital recipient (GRA) and next step.

9.6 Narrative & comms risks (Media/Civic) — 10 minutes

Objective: protect public trust; set early-warning messages; decide on/off-record posture.
Inputs: Narrative Risk Note; proposed key messages; EWI prompts.
Flow:

Narrative risks (4’): likely misreads; dis/misinformation vectors; equity sensitivities.
Messaging (4’): 2–3 key messages; audience and channels; localization cues.
Posture (2’): on/off-record decision; approvals needed.

Prompts:

“What will the public reasonably misunderstand first?”
“Which message must be localized to avoid harm?”

Outputs: Comms Note outline; posture decision; named comms owner(s).

Success signals: messages tied to evidence; clear posture logged; localization owners named.

9.7 Decisions, owners, deadlines (Chair + Rapporteur) — 10 minutes

Objective: convert conclusions into accountable actions with dates and recipients.
Inputs: notes from segments 2–6; hand-off checklist.
Flow (live capture on screen):

Decisions (3’): bullet verbs (“Adopt scenario B for pilot”; “Draft clause X redline”).
Owners & dates (4’): one human per action + deadline.
Hand-offs (2’): recipients (GCRI/NSF/GRA/RSB/NWG/New Media) + acknowledgment SLA (≤5 business days).
Blockers (1’): named risk + mitigation or Working Session follow-up.

Definition of Done (DoD) for the session:

Decisions phrased as verb + object + date.
Every action has one owner and one recipient.
Label and any recusals noted; AAR due T+3; artifacts due T+5.

Close (Chair): restate top 3 actions; thank contributors; remind label & COI carry forward.

Facilitation tips (all segments)

Ruthless timekeeping: ±30 seconds on transitions; park digressions.
Equitable turns: prioritize unheard voices; rotate regions/sectors.
Clarity checks: “In one sentence, what did we just decide?”
Safety: intervene on harassment, lobbying, or confidentiality breaches; move sensitive content to Closed Technical if needed.

Artifacts created/updated during the meeting

Decision log (live) • COI updates • Parking lot list • Incidents (if any) • AAR skeleton (Rapporteur).

Reminder: All outputs are clause-licensed; GRF does not own/develop tools; any commercialization or deal structuring occurs outside GRF via the appropriate Nexus entity.

Required Outputs (Every Month)

All tracks must produce the same core set of artifacts. Keep them short, neutral, sourced, and ready for immediate hand-off. Every file must carry a label (Public / Internal / Restricted) and the licensing footer in 10.6.

Shared header for every artifact

Title · Track · Date (YYYY-MM-DD) · Version (vX.Y) · Owner(s) · Recipients · Label · Related Intake ID(s)
File name format: [Track]_[Artifact]_[YYYYMMDD]_vX.Y_[Label] (e.g., Research_AAR_20250824_v1.0_Internal)

Shared quality bar (applies to all)

Plain language, neutral tone; decisions stated as verb + object + date.
References are verifiable (URL/DOI/dataset ID/registry ID) and placed at the end.
COI notes and document label applied in header/footer and repository metadata.
Stored in the approved repository with correct permissions; links shared (no attachments for Internal/Restricted).

10.1 After-Action Report (AAR, ≤3 pages)

Purpose: single source of truth for what was decided, by whom, by when—based on evidence discussed at T-0.

Contents (in order)

Context (≤5 lines): item(s), scope, label, date.
Facts (bullets): sourced statements only.
Uncertainties: key assumptions + P10/P50/P90 (or comparable) + EVPI (what data would help).
Options Tested (2–4): one-line summary + notable trade-offs.
Decisions: verb + object + date (e.g., “Draft redline for Clause X by 2025-09-05”).
Owners & Recipients: one named person per action; receiving body (GCRI/NSF/GRA/RSB/NWG/New Media).
Blockers & Mitigations: named risks + next gate.
References: links/IDs; methods note pointer if used.

Tone: neutral, non-advocacy, no sales language.

Acceptance criteria

Delivered by T+3; ≤3 pages; all decisions time-bound and owner-assigned.
Every factual claim has a retrievable source; confidential items redacted per label.
AAR approved by Chair; archived and distributed by Secretary by T+5.

10.2 Clause Pack Delta (Standards/NSF)

Purpose: capture the exact legal/standards changes implied by the session.

Contents

Baseline citation (registry link/ID) + version.
Redline table (add/modify/remove):
- Field: Definition / Trigger / Covenant / Oversight / Remedy
- Old text → Proposed text
- Rationale & evidence reference
- Collision notes (jurisdiction/standard)
Clean copy of proposed clauses (registry-ready).
Implementation notes: effective date, transition/grace, deprecation if any.

Acceptance criteria

Language is registry-ready (no placeholders); collisions resolved or explicitly flagged with options.
Submitted to NSF registry with owner named; receipt/acknowledgment logged within 5 business days.
Labeling consistent (Restricted if any sensitive legal language pending clearance).

10.3 Policy Option Note (Policy/Regulatory → RSBs/NWGs)

Purpose: turn favored options into enforceable, localized policy pathways and pilots.

Contents

Policy routes (2–3): statute/regulation/mandate pathway; oversight & remedy; compatibility with existing frameworks.
Jurisdiction map: which authorities; cross-border collisions; harmonization approach.
Readiness rating: Low / Medium / High with rationale.
Dependencies: data, standards, capacity, budget.
Pilot prompts: objective, site/agency candidate(s), timeline (Qx-YYYY), success metrics.
Risks & mitigations: legal, operational, equity.

Acceptance criteria

One named recipient owner in RSB/NWG; specific next gate and date.
Conflicts and dependencies explicitly listed; label applied; redactions prepared for Public summary if needed.
Delivered by T+5; acknowledgment within 5 business days.

10.4 Investment Note (Capital → GRA)

Purpose: translate insights into investable signals and accountable covenants (no deals inside GRF).

Contents

Hypothesis / Thesis: what to finance and why (1–2 paragraphs).
Exposure & KPIs: probability × impact ranges; the one metric that best predicts failure/success.
Triggers & Covenants: monitorable conditions; verification hooks; clause references.
Diligence asks: data-room checklist; counterparties to contact; missing evidence that would flip the decision.
Corridor fit: which corridor(s) and stage; indicative timeline to structure outside GRF.

Acceptance criteria

No pricing terms/negotiation language; signals only.
Clear hand-off to GRA with a named corridor lead and target date.
Delivered by T+5; acknowledgment within 5 business days.

10.5 Comms Note (Media/Civic → New Media/RSBs/NWGs)

Purpose: protect public trust, align early-warning messaging, and set the on/off-record posture.

Contents

Posture: On-record / Off-record + approvals required.
Key messages (2–3): short, evidence-linked, non-alarmist.
EWI alignment: what to say if indicators cross thresholds; who says it; where.
Narrative risk table: likely misreads; misinformation vectors; vulnerable groups; mitigations.
Localization cues: terms to avoid/translate; regional examples; accessibility needs (captions, formats).
Assets needed: explainer outline, visuals/data, spokespersons.

Acceptance criteria

Statements source-checked; quotes approved; redactions honored per label.
Named comms owner(s) per region; delivery plan and timeline recorded.
Delivered by T+5; Public version provided if label permits.

10.6 Licensing statement (paste into every artifact footer)

Licensing & Guardrails
This artifact is clause-licensed for public-benefit governance and standards alignment. The Global Risks Forum (GRF) provides neutral convening and documentation only; it does not own or develop tools and does not conduct fundraising or deal-making within GRF sessions. Any implementation, commercialization, or capital structuring occurs outside GRF via the appropriate Nexus entity (e.g., GCRI/TMDs for methods & tooling, NSF for standards/registry, GRA for capital corridors, RSBs/NWGs for localization and pilots). Document label: [Public / Internal / Restricted]. COI and confidentiality rules apply.

Definition of Done (DoD) checklist — apply before publishing

Header complete (title/track/date/version/owner/recipients/label/intake ID).
Neutral tone; no advocacy or sales language.
Decisions/actions are verb + object + date, with one owner and one recipient each.
References present and retrievable; sensitive data redacted per label.
Stored in approved repo with correct permissions; link shared (no raw attachments for Internal/Restricted).
Licensing footer pasted (10.6); COI notes recorded; Acknowledgment requested from recipients.

Handoffs & Acceptance Criteria

This section defines what leaves GRF, where it goes, what “ready” means, and how acceptance is confirmed. Use the same structure every month to keep recipients fast and confident.

11.0 Universal handoff package (all recipients)

Handoff cover sheet (1 page, required)

Header: Track • Item title • Label (Public/Internal/Restricted) • Date • Version • From (Owner) • To (Recipient/Named Owner)
Links: AAR, lane artifact(s) (Clause/Policy/Investment/Comms), supporting pre-reads
Ask: What decision/action you’re requesting, with due date and acceptance criteria
Context: 3–5 bullets (facts, uncertainties, risks)
COI note & distribution list
Contact(s) for follow-up

Attachments (as applicable)

AAR (≤3 pp) • Clause Pack Delta • Policy Option Note • Investment Note • Comms Note • Annexes (redacted per label)

Repository & permissions

Stored in the approved repo; link shared (no attachments for Internal/Restricted)
Access scope matches the label; watermarks/download controls on where supported

11.1 To GCRI/TMDs (methods, data, testing)

Purpose: turn insights into methods work, data tasks, and prototype tests.

What to send

AAR + Evidence & Assumptions pack
Methods tasks list (owner, due date, success measure)
Data spec: sources, transformations, quality flags, license
Test plan outline: scenario, metrics, run conditions, compute/EO needs

Acceptance criteria (by recipient)

Named GCRI/TMD owner assigned
Task IDs opened in their tracker, with dates & resources
Data access confirmed (or request sent)
Test schedule agreed (window/infra)

Definition of Done (GRF)

Handoff cover sheet + links filed
Acknowledgment (≤5 business days) logged
T+14 status updated in CB calendar

11.2 To NSF (standards/clauses, audits, registry)

Purpose: convert decisions into registry-ready clauses and standards updates.

What to send

AAR + Clause Pack Delta (redline + clean)
Collision log (jurisdiction/standard) + options for resolution
Effective/transition dates, oversight/remedy notes

Acceptance criteria (by recipient)

NSF registry ticket/ID issued
Editor of record assigned; target publication date set
Collisions accepted (resolved or queued with plan)
Audit implications (if any) recorded

Definition of Done (GRF)

Registry ID captured in the artifact metadata
Acknowledgment (≤5 business days) logged
T+14 status posted (Published / In queue / Needs revision)

11.3 To RSBs/NWGs (localization, pilots)

Purpose: move options into regional/national policy paths and pilots.

What to send

AAR + Policy Option Note
Jurisdiction map; dependencies; pilot prompts (site/agency/timeframe/metrics)
Any redactions/localization cues

Acceptance criteria (by recipient)

RSB/NWG owner named (ministry/agency focal + person)
Pilot decision: Proceed / Scope / Hold, with target Q and first milestone
Localization plan logged (language, legal review, stakeholders)
Feedback window scheduled (date for first check-back)

Definition of Done (GRF)

Owner + first milestone captured
Acknowledgment (≤5 business days) logged
T+14 status posted (Pilot planned / Awaiting prerequisites / Redirected)

11.4 To GRA (corridor pipelines, co-structuring)

Purpose: translate signals into corridor pipeline work (outside GRF).

What to send

AAR + Investment Note
Triggers/covenants (verification hooks, clause refs)
Diligence checklist; data-room needs; counterparties

Acceptance criteria (by recipient)

Corridor lead assigned; stage & indicative timeline created
Diligence room opened/requested; missing evidence list acknowledged
Compliance checks (sanctions/PEP where needed) initiated
Next gate agreed (scope or structure workshop, outside GRF)

Definition of Done (GRF)

Corridor lead + next gate recorded
Acknowledgment (≤5 business days) logged
T+14 status posted (In corridor / Awaiting evidence / Not a fit)

Guardrail reminder: no deal-making or pricing inside GRF. GRA handles structuring outside GRF spaces.

11.5 To New Media (public explainers, messaging kits)

Purpose: deliver trusted public communication and EWI-aligned messages.

What to send

AAR + Comms Note (posture, key messages, EWI prompts)
Narrative risk table; localization plan; approvals needed
Visual/data assets (or requests) and spokespeople list

Acceptance criteria (by recipient)

Comms owner(s) per region named
Posture confirmed (On/Off record) with approvals
Explainer brief accepted with delivery date and channels
Translation/accessibility plan set (languages, captions, formats)

Definition of Done (GRF)

Owners + delivery dates logged
Acknowledgment (≤5 business days) recorded
T+14 status posted (Live / In production / Requires revision)

11.6 Acknowledgment SLA & “Definition of Done” per recipient

Acknowledgment SLA (all recipients)

Recipients confirm receipt and name an internal owner within ≤5 business days.
If unmet: Governance Secretary pings day 6; Chair escalates day 7 to RSB/CB as appropriate.

Definition of Done (per recipient class)

Recipient	DoD (accepted when…)
GCRI/TMDs	Task IDs created; owner named; data access confirmed; test window scheduled.
NSF	Registry ticket/ID issued; editor assigned; collision status set; target publication date noted.
RSBs/NWGs	Owner/focal named; pilot decision & first milestone set; localization plan logged; check-back date scheduled.
GRA	Corridor lead assigned; stage & next gate defined; diligence room or evidence request opened; compliance checks initiated as needed.
New Media	Regional comms owners named; posture confirmed; explainer brief & delivery plan accepted; translation/accessibility plan defined.

Tracking & escalation

Governance Secretary maintains the handoff log (owner, due dates, label, links, SLA status).
Chair reviews at T+14; unresolved items marked At-risk/Blocked; escalate to RSB/GSB/BoT per PNG if needed.
When an artifact is revised post-feedback, version bump and change note are required; notify the distribution list.

Security & privacy

Labels control distribution (Public/Internal/Restricted); redactions prepared where needed.
No Restricted content in unapproved tools or channels; MFA enforced on all repos.

Licensing & guardrails (apply to every handoff)

All artifacts are clause-licensed; GRF does not own/develop tools; no fundraising or deal-making occurs in GRF sessions.
Implementation/commercialization happens outside GRF via the appropriate Nexus entity.

Measurement & Reporting

This section defines what we measure, how we score it, what “good” looks like, and what to do when we fall short. It applies to every track, every month.

12.1 KPIs (definitions & how to compute)

Data sources: attendance log, pre-read timestamps, AAR/artifact metadata, handoff log, CB calendar (T+14 / 30 / 60), incident log.

KPI	Definition	How to compute (monthly)
Participation mix	Breadth and balance of who is in the room.	Count unique participants by sector (Gov/IGO, Academia/Research, Private/Finance/Industry, Civil Society/NGO, Community/Bioregional) and region (AF, AS, EU, MENA, NA, SA). Score = sectors represented (0–5) + regions represented (0–6). Track % underrepresented groups if collected.
Evidence quality	Rigor of inputs and transparency of limits.	0–5 score: (1) All factual claims sourced (1pt); (2) Methods named + parameters (1pt); (3) Uncertainty bands stated (1pt); (4) EVPI/gaps listed (1pt); (5) Pre-reads delivered by T-2 (1pt).
Options tested	Depth of decision analysis.	Number of distinct options stress-tested at T-0 (target 2–4).
Handoff acceptance	Responsiveness of recipients.	% of handoffs acknowledged (owner named) ≤5 business days.
30/60-day follow-through	Delivery discipline on actions.	% of actions marked Done by D+30 and D+60 (from the decision date captured in AAR).
Compliance incidents	Safety, COI & confidentiality performance.	Count of material incidents per month and rate per 100 participants. Categories: COI, labeling/privacy, conduct/safeguarding.
Timeliness (AAR & artifacts)	On-time outputs.	% AAR issued by T+3; % lane artifacts issued by T+5.

Optional overlays (track-specific): Research replication rate; Innovation readiness gates cleared; Policy collision resolution time; Capital diligence cycle time; Media EWI coverage time.

12.2 KPI targets, thresholds, and remediation steps

Status colors: 🟢 Green = on target · 🟡 Yellow = watch/remediate · 🔴 Red = escalate

KPI	Target (Green)	Yellow	Red	First remediation steps (owner)
Participation mix	≥ 3 sectors and ≥ 3 regions represented per month	2 sectors or 2 regions	≤1 sector or ≤1 region	Chair + Secretary: adjust invite lists; rotate time zones; enable interpretation; tap Fellows/RSB rosters; carry target to next 2 agendas.
Evidence quality (0–5)	≥4	3	≤2	Science Lead: pre-read QA checklist; add methods appendix; schedule Working Session to fix gaps; coaching for repeat offenders.
Options tested	2–4 options	1 option	0 options	Facilitator: enforce agenda; require option card for intake; Chair holds items that arrive without ≥2 options.
Handoff acceptance	≥95% acknowledged ≤5 biz days	80–94%	<80%	Secretary: day-6 ping; day-7 Chair escalation to recipient lead/RSB/CB; review handoff clarity template.
30-day follow-through	≥75% actions done by D+30	60–74%	<60%	Chair: T+14 risk review; assign Working Session; remove/replace non-performing owners; escalate blockers to RSB/CB.
60-day follow-through	≥90% actions done by D+60	75–89%	<75%	Chairs’ Council: corrective plan; rotate owners; consider pausing new intake until backlog clears.
Compliance incidents (rate)	0 (≤0.1 per 100 participants)	0.1–0.3	>0.3	Secretary: incident post-mortem; refresher on COI/labels/safety; targeted restrictions; repeat → removal review.
Timeliness: AAR	≥95% by T+3	80–94%	<80%	Rapporteur + Chair: pre-built AAR skeleton; backup rapporteur; automate reference pulls.
Timeliness: artifacts	≥95% by T+5	80–94%	<80%	Leads: lane work-back plans; template enforcement; escalate blockers day-4.

Escalation ladder (if any KPI is 🔴 for 2 consecutive months): Chair → RSB/CB → Chairs’ Council/Trustee review. Outcomes may include role rotation, additional resources, or temporary intake freeze.

12.3 Monthly KPI summary template; quarterly track review

A) Monthly KPI Summary (one-page)

Header: Track · Month · Chair · Secretary · Label (Public/Internal) · Version

KPI	Value (this month)	Target	Status	Note (root cause / context)	Action	Owner	Due
Participation mix (sectors, regions)	3 sectors / 4 regions	≥3 / ≥3	🟢		Add Africa speaker next month	Chair	Next T-0
Evidence quality (0–5)	3	≥4	🟡	Late pre-reads	Pre-read freeze at T-2; QA pass	Science Lead	D-2
Options tested (#)	2	2–4	🟢
Handoff acceptance (%)	88%	≥95%	🟡	NSF ack late	Day-7 escalation	Secretary	Day 7
30-day follow-through (%)	70%	≥75%	🟡	Owner change	Replace owner; Working Session	Chair	D+35
60-day follow-through (%)	85%	≥90%	🟡	Dependency	Escalate to RSB	Chair	D+45
Compliance incidents (count / rate)	1 / 0.14	0 / ≤0.1	🟡	Mislabel	Refresher; label bot	Secretary	+7d
Timeliness AAR (%)	100%	≥95%	🟢
Timeliness artifacts (%)	90%	≥95%	🟡	Capital note late	Template; backup author	Capital Lead	T+5

Footer: Links: AARs · Artifacts · Handoff log · Incident report · CB calendar status

B) Per-Session Mini-Scorecard (attach to AAR)

Item	Score / Result
COI declared before item?	Yes/No
Evidence quality sub-score (0–5)
Options tested (#)
Decisions written as verb+object+date	Yes/No
Owners named (1 per action)	Yes/No
Label applied & respected	Public / Internal / Restricted
Incidents (Y/N)

C) Quarterly Track Review (2–3 pages)

1) Highlights & outcomes

Top 3 wins; notable cross-track collaborations; policy/standards published; pilots launched.

2) KPI trends (3 months)

Table of monthly KPI values with color status.
Commentary: what improved, what regressed, why.

3) Risks & blockers

Recurrent issues (e.g., late pre-reads, slow acks, incident hotspots).
Root causes and system fixes (calendar cadence, template gaps, resourcing).

4) Corrective actions

Specific, measurable steps (owner + date).
Training/bootcamps scheduled (evidence QA, facilitation, labeling).

5) Resource requests

People (backup rapporteurs, deputy leads), tooling (label automation, translation), budget (access services).

6) Governance notes

Any role rotations, acting appointments, or term renewals recommended.

7) Next-quarter goals

Participation targets (regions/sectors), evidence-quality goal, backlog burn-down, publication milestones.

Appendix

Incident summaries (redacted), handoff acceptance logs, AAR/artifact timeliness chart.

D) Roles for measurement & reporting (who does what)

Rapporteur: per-session mini-scorecard; AAR KPI fields.
Governance Secretary: monthly KPI table; handoff & incident logs; CB updates.
Chair: approves monthly summary; owns remediation plan; presents quarterly review.
Committee Leads: deliver lane metrics (e.g., artifact timeliness); execute corrective actions.
CB/RSB focal points: confirm acknowledgments; unblock cross-entity issues.

E) Ready-to-paste notes (headers/footers)

Header on KPI docs: “This report is Internal; COI & confidentiality rules apply.”
Footer: “All outputs are clause-licensed; GRF remains a neutral convening body and does not own/develop tools. Commercial or implementation activity occurs outside GRF via the appropriate Nexus entity.”

Calendaring & Coordination

This section makes every track easy to find, join, and run—without collisions. It defines the quarterly rhythm, how the Central Bureau (CB) master calendar works, and how Chairs’ Council resolves conflicts and balances load.

13.1 Quarterly sample calendar (Week 1–4 rotation)

Goal: a predictable month where every track has its window, plus time for fixes and cross-track alignment.

Standard month (repeat each month in the quarter)

Rotate the meeting time zone window monthly:

Slot A (AMER/EMEA) and Slot B (APAC/EMEA) alternate to share convenience.

Keep each track on its weekday to build habit.

Week	Tue	Wed	Thu	Fri
Week 1	Research (Public Discussion)	—	Innovation (Public Discussion)	—
Week 2	Policy (Public Discussion)	—	New Media & Civic (Public Discussion)	—
Week 3	—	Capital & Investment (Public Discussion)	—	—
Week 4	Working Sessions (as needed)	Closed Technical (as needed)	Working Sessions (as needed)	Chairs’ Council (cross-track alignment)

Default durations & buffers

Public Discussion: 90 minutes (Section 9 agenda).
Working/Closed Technical: 60–90 minutes.
Buffers: 15-minute setup + 15-minute decompression after every meeting slot.
Blackouts: avoid major regional holidays; the CB publishes a holiday list at the start of each quarter.

Time zone rotation (example)

Month 1: Slot A (AMER/EMEA) for all Public Discussions.
Month 2: Slot B (APAC/EMEA).
Month 3: back to Slot A.

Chairs may schedule additional mirror sessions (shorter, recap-only) for regions that missed the main slot.

13.2 Central Bureau master calendar: submissions, updates, visibility

What the CB calendar is
The single source of truth for all track events, artifacts, and deadlines. Managed by the Governance Secretary on behalf of CB.

Event types (color key)

Public Discussion (green)
Working Session (blue)
Closed Technical (red)
Chairs’ Council (purple)
Deadlines—AAR (orange), Artifacts (yellow), Handoff acks (pink), T+14 check (gray)

Required metadata on every calendar entry

Track • Region focus (if any) • Label (Public / Internal / Restricted)
Owner(s) (human) and Distribution list
Attachments/Links: agenda, pre-reads, run-of-show, meeting link (passcode), repo folder
Deadlines auto-linked: AAR (T+3), Artifacts (T+5), Handoff Ack (≤5 business days), T+14 follow-through

Submission & update flow

Add events: Chairs propose changes to the Secretary; Secretary edits the CB calendar.
Intake windows: CB calendar shows T-14→T-7 open window for submissions per track.
Freeze: T-2 agenda & pre-reads freeze posts on the calendar event.
Deadlines: AAR/T+3, Artifacts/T+5, Handoff Ack/Day 5, T+14 check—auto-created as separate calendar reminders.
Rescheduling rule: ≥ 5 business days’ notice unless safety/compliance demands immediate change.

Visibility & access

Read-only ICS feeds for all members (sanitized titles if labeled Internal/Restricted).
Full details visible to distribution list members with access rights.
No personal calendars for Restricted topics—only CB calendar links with SSO/MFA.

Records & retention

Calendar entries keep versioned attachments; changes captured in the calendar’s change log.
Past quarter events archived with labels intact.

13.3 Cross-track alignment (Chairs’ Council), conflict resolution, load balancing

A) Chairs’ Council (weekly micro-sync + monthly deep-dive)

Weekly (15 min, Week 1–3, Fri): quick scan—collisions, late pre-reads, handoff acks, incident flags.
Monthly (60 min, Week 4, Fri): review KPIs (Sec. 12), prioritize cross-track needs, set next-month goals, confirm time-zone rotation.

Inputs: monthly KPI summary, handoff log, incident log, CB calendar diffs.
Outputs: alignment notes, conflict decisions, any temporary intake caps, and resourcing moves (backup rapporteurs, interpreter bookings, etc.).

B) Conflict resolution (prioritization matrix)

When two or more tracks compete for the same SMEs, recipient capacity, or calendar slot, the Chair + Secretary apply this order:

Safety/Legal/Regulatory deadlines and incident response.
External dependency windows (e.g., scheduled RSB/NWG pilot launch, NSF registry window).
Cross-track leverage (items unlocking multiple tracks or corridors rank higher).
Age & readiness (older, DoR-ready items beat newer or under-baked items).
Equity & region rotation (ensure rotating regional convenience; avoid repeated APAC-unfriendly scheduling).

Resolution tools

Move one item to Closed Technical (if label/sensitivity drives priority).
Split content: Public Discussion holds decision framing; Working Session finishes redlines/tests.
Assign acting SMEs or request written memos if the top SME is booked.
If unresolved: elevate to CB for final slotting.

C) Load balancing (caps & triggers)

To protect quality and people:

Per-session caps

Agenda items: max 3 decision items + 1 short update.
Restricted items: max 1 per Public Discussion (others → Closed Technical).
Speaking roles: avoid assigning the same person to >2 major roles in one month.

Per-month triggers (automatic guardrails)

If AAR timeliness < 95% or artifact timeliness < 90% → cap the next month at 2 decision items until back in green.
If handoff acceptance < 90% → Secretary runs recipient outreach; Chair may pause new intake for 1 cycle.
If compliance incidents > 0.3/100 participants → mandatory refresher + label bot/automation enabled.

Resourcing moves

Appoint backup rapporteurs; schedule template bootcamps; pre-book interpreters/captions and technical moderators.
Use mirror sessions (recap format) to reduce single-slot congestion.

D) Communication & change control

Publish Monthly Track Snapshot (one-pager) to the track list: upcoming slots, deadlines, and key dependencies.
All changes summarized in a CB weekly bulletin (bulleted diffs with links).
Emergency changes (security/compliance): Secretary posts a red-banner notice and reissues invites immediately.

Quick checklists

Chair (end of Week 4)

Next month’s agenda sketched (≤3 decision items).
Time zone slot selected (alternate A/B).
Known SME collisions flagged to Secretary.
Resource holds (interpreters/captions/moderators) confirmed.

Governance Secretary (every Friday)

Intake windows posted for next 2 weeks.
All T-2 freezes visible; access permissions verified.
Deadlines auto-generated (AAR/T+3, Artifacts/T+5, Ack/D+5, T+14).
Handoff log reconciled; acks pending pinged.

Chairs’ Council (monthly)

KPI heatmap reviewed; caps applied if needed.
Conflicts ruled; escalations (if any) sent to CB.
Holiday/blackout impacts handled; mirror sessions scheduled if appropriate.

Standing guardrails: keep neutrality, labels, and COI rules at the center; GRF does not own/develop tools; no fundraising/deal-making in GRF sessions; use CB calendar as the single source of truth.

Dispute Resolution & Escalation

Purpose. Give every track a fast, fair, and documented way to resolve disagreements—starting in-room, then via a PNG simulation, and only then (if needed) via arbitration.
Principles. Speed • Proportionality • Neutrality • Due process • Confidentiality • Non-retaliation.
Scope. Substantive/content disputes, process disagreements, cross-track collisions, recipient rejections, and governance conflicts. (Misconduct/harassment follows §6.)

14.1 Session-level disagreements (Facilitator protocol; Chair decision)

When it applies. Live disputes at T-0: scope/time, evidence verifiability, COI/recusal, label changes, option framing.

“Stop–Clarify–Decide” micro-protocol (≤3 minutes total):

Stop (≤30s): Facilitator halts discussion, names the disagreement type, cites the rule (agenda, COI, label, evidence).
Clarify (≤90s):
- If evidence claim → ask for source now. No source? Mark “unverified” and park it.
- If COI → confirm/record; Chair may impose recusal.
- If label → check pre-reads; move to Closed Technical if required.
Decide (≤60s): Chair rules: continue as is | timebox extend (±5 min) | table to Working/Closed | reframe question | recusal.
Record: Rapporteur logs the ruling; Governance Secretary updates the COI/incident note if relevant.

Quick remedies (examples).

Time/sequence: Move a late item to the end; grant a 5-minute extension once.
Scope: Reframe decision to what can be decided today.
Evidence: Create a Working Session to resolve data/method gaps.
COI: Full or partial recusal.
Sensitivity: Switch to Closed Technical (new invite + label).

Documentation & SLAs.

Dispute note in AAR; Secretary adds entry to Dispute Register within 24h.
If the same dispute reappears next month, auto-triggers §14.2 (PNG simulation).

14.2 Cross-track or governance disputes (PNG simulation first)

When it applies.

Affects multiple tracks/regions/recipients.
Recipient rejects hand-off on principle (not just formatting).
Recurrent session-level dispute (twice in 60 days).
Standards/policy collision across jurisdictions.

Goal. Test contested assumptions and options under a neutral, clause-aware simulation to generate a resolution matrix.

Process & timeline (business days from dispute log entry).

T+0–2 | Acknowledge & scope. Secretary logs case; Chair (or Chairs’ Council) appoints Neutral Simulation Lead. Define the decision question, parties, evidence set, label, and required recusals.
T+3–5 | Pack & invites. Simulation Lead compiles Evidence & Assumptions pack, scenario cards, collision map (if any), and sends agenda.
T+6–10 | Simulation session (90–120 min).
- Re-state question; verify COIs/labels.
- Stress-test 2–4 options with the same stressors (legal, operational, equity, cost, time).
- Produce Resolution Matrix: option → impacts, clause deltas, policy route, risks, “no-regrets” steps.
T+12 | Draft finding. Circulate Simulation Findings Note + Proposed Resolution (owners, dates).
T+15 | Final decision. Decision body confirms (below). Secretary files and updates CB calendar.

Decision bodies (by scope).

Track-internal → Chair + Leads endorse; if contested, → Chairs’ Council.
Regional impact → RSB confirms.
Global/standards impact → GSB/NSF (and Trustees if constitutional).

Outcomes.

Adopt option X with clause deltas; assign owners/dates.
Conditional adoption with data/guardrails.
Defer to pilot in named RSB/NWG with success criteria.
No-go with rationale; alternative path.

Confidentiality. Label the entire process; use Closed Technical if any Restricted content. Public summaries are redacted.

14.3 Formal escalation to arbitration (jurisdiction, venue, timelines)

When it applies. Only after §14.2 is completed without resolution, or when a party alleges a material breach of PNG/GRF rules that cannot be remedied administratively.

Pre-conditions.

Evidence that PNG simulation ran (Findings Note attached).
Statement of unresolved points and remedies sought.
Confirmation that internal appeals (Chair → Chairs’ Council → RSB/GSB/Trustee as applicable) are exhausted.

Notice of arbitration (what to file).

Parties, contact info, dispute summary, relief sought, relevant documents (AARs, Clause Pack deltas, Simulation Findings).
Send to the Governance Secretary and the other party; copy Trustees.

Seat, law, language.

Seat/Venue: Zug, Switzerland.
Governing law: applicable Swiss law, read together with the PNG/GRF governing instruments.
Language: English.

Rules & tribunal.

Proceedings under recognized Swiss arbitration rules administered by a competent Swiss arbitration centre.
Tribunal of one or three arbitrators (per rules); emergency measures available if needed.
Parties may agree in writing to an alternative reputable institution.

Timelines (targets).

Tribunal constituted: ~30–45 days from Notice (subject to rules).
Hearing/briefing schedule set within 15 days of constitution.
Final award targeted within 120 days of constitution (extendable by tribunal).

Confidentiality & conduct.

Proceedings are confidential; redacted summaries may be published only if required by policy or law.
No retaliation against any participant; access and roles remain unaffected unless a protective order is issued.

Remedies.

Declaratory relief; direction to perform procedural obligations (e.g., run pilot, register clause); corrective publication; cost allocation.
Monetary damages are generally out of scope for honorary/non-fiduciary roles, but the tribunal may allocate fees/costs.

Enforcement & closure.

Award is final and binding.
Governance Secretary logs outcome; CB calendar updated with any mandated actions; Dispute Register closed with references.

Quick reference (paste in decks)

In room: Stop–Clarify–Decide → Chair ruling (logged).
If it spans tracks/regions/standards: run a PNG simulation (T+10) → Findings → Resolution Matrix.
If still unresolved: Arbitration (Zug; Swiss law; English).
At every step: label correctly; record COIs; zero retaliation.

Inclusion, Accessibility & Translation

Purpose. Make every GRF interaction usable and welcoming for all participants—across languages, abilities, bandwidths, and time zones—while protecting confidentiality and accuracy.

Roles

Governance Secretary (SEC): books services, sets permissions, applies labels, tracks SLAs.
Media/Civic Lead (MED): owns inclusive content & public-facing materials.
Track Chair (CH): enforces inclusive practice in-room.
RSB/NWG Localization Focals (LOC): advise languages/dialects; validate localized outputs.

15.1 Accessibility services (interpretation, captions, formats)

A) Booking & setup (virtual or in-person)

Request window: participants can request services on the intake form or by emailing the SEC ≥7 calendar days before T-0 (earlier is better).
Default options (choose as needed):
- Live captions (human CART preferred; ASR allowed for Public/Internal with disclosure; ASR not for “Restricted” unless SEC approves).
- Sign-language interpretation (specify language: e.g., ASL, BSL, LSF).
- Spoken-language interpretation (simultaneous or consecutive).
- Real-time text chat backchannel for questions.
Platform setup:
- Enable multi-language audio, caption feed, host controls, and recording toggle (off by default for Restricted).
- Provide interpreters panelist/host privileges and a sound check T-0 minus 20 minutes.

B) Accessible content standards (apply to all pre-reads/artifacts)

Plain language: short sentences, defined terms; avoid idioms.
Structure: H1/H2/H3 headings; lists instead of walls of text.
Fonts & contrast: min 12pt (prefer 14pt); contrast ratio ≥4.5:1.
Color use: never encode meaning by color alone; add labels/patterns.
Links: descriptive text (“Policy Option Note”), not raw URLs; indicate if external.
Images/charts: include alt text; ensure data labels; provide underlying data where possible.
Tables: simple headers; avoid merged cells; add summaries.
Documents: provide tagged PDF (PDF/UA) and accessible HTML or DOCX; right-to-left (RTL) languages respected.
Numbers/dates: use ISO 8601 dates (YYYY-MM-DD); show units; for currency show code (e.g., USD).

C) Room conduct to support access

Speak clearly and one at a time; pause for interpretation every few minutes.
Name yourself before speaking when audio-only.
Avoid acronyms; if used, expand on first use.
Facilitator manages a hand-raise queue; chat questions read aloud for attendees using screen readers.

D) Venue (in-person) minimums

Step-free access, ramps/elevators; seating for mobility devices.
Quiet space; clearly marked restrooms; hydration.
Assistive listening (loop/IR) where available; caption screen if feasible.
Safety briefing at start; Duty-of-Care contact displayed.

E) Procurement & confidentiality

Use vetted vendors under NDA for interpretation/captions.
Interpreters/captioners receive document labels (Public/Internal/Restricted) and COI reminders.
Do not send Restricted materials to vendor platforms lacking encryption/MFA.

SLA (target)

Services confirmed ≥ 5 business days before T-0; dry-run performed; backup caption method ready.

15.2 Inclusive participation practices & regional time-zone rotation

A) Meeting practices

Progressive speaking order: prioritize unheard voices/regions; rotate first speakers each month.
Timeboxing & pacing: moderator enforces limits; provides 30-second warnings.
Multi-modal participation: accept inputs via voice, chat, and pre-submitted notes.
Bandwidth equity: provide audio-only dial-in, low-bandwidth slides (PDF), and recordings/transcripts where label permits.
COI & safety: remind at start; make recusal simple and stigma-free.

B) Regional time-zone rotation

Alternate monthly between Slot A (AMER/EMEA) and Slot B (APAC/EMEA) (see §13.1).
Offer mirror recap (30–45 min) if a region is systematically disadvantaged.
Publish quarterly time-zone map; avoid major regional holidays; coordinate with RSBs.

C) Inclusion signals & checks

Attendance mix reviewed monthly (sectors/regions/gender where provided).
Provide interpretation/captions availability in invites.
Share pre-reads at T-2 so non-native speakers and interpreted attendees can prepare.

15.3 Translation & localization workflow for outputs

Definitions

Translation: language conversion of content.
Localization: adapting for legal, cultural, and operational context (jurisdiction names, agencies, units, examples).

A) What we translate (priorities)

Always: AAR executive summary (≤200 words), Comms Note intended for public use, and public explainers.
As needed: full AAR, Policy Option Note sections for target jurisdictions, Investment Note one-pager for corridor partners, Clause Pack cover note (not the legal redline unless requested by NSF/RSB).
Restricted: translate only via secure, approved channels; no external MT.

B) Language selection (decided with RSB/NWG LOC)

Base on audience and deployment path: e.g., EN/FR/ES/AR/ZH/RU/HI/PT as core; add regional languages (e.g., Swahili, Bahasa Indonesia) per item.

C) Workflow (who does what)

Request (Owner → SEC): specify document, label, languages, deadline, audience.
Prep (MED + Owner): finalize English source; add glossary and style guide; mark untranslatable tokens (clause IDs, dataset codes).
Translate (Vendor or RSB/NWG LOC):
- Public/Internal: MT-assist allowed + human review.
- Restricted: human-only translators under NDA; secure transfer.
Review (Two-pass):
- Language QA: accuracy, tone, terminology.
- Localization QA: jurisdiction names, units, agency titles, compliance terms.
Sign-off (Owner + MED): confirm label carried over; headers/footers updated.
Publish & store: save with locale tag and metadata; distribute links (no attachments for Internal/Restricted).

D) Quality bar & formatting

Maintain structure (headings, tables, alt text, lists).
Keep numbers/units consistent; show local unit and original on first mention where helpful.
Use UTF-8; support RTL layout where needed.
Apply locale tags in filenames:
- Policy_AAR_20251015_v1.0_Public_en, …_fr-CA, …_ar, …_sw.

E) Turnaround targets (per 1,000 words; working days)

Public/Internal: MT-assist + human review → 1–2 days.
Restricted: human-only + confidentiality checks → 2–4 days.
Comms snippets (≤200 words): same day where possible.

F) Terminology & consistency

Maintain a central glossary (PNG/GRF terms, agencies, clause labels); update quarterly.
Avoid ambiguous terms; prefer plain language equivalents.
For legal/standards terms, include the original language in parentheses on first use.

G) Verification & sign-off checklist

Label and COI carried through headers/footers/metadata.
Names, agencies, titles verified with RSB/NWG LOC.
Numbers/units/dates verified; currencies include code (USD, EUR).
Links function; documents are accessible (tagged PDF/HTML, alt text).
Licensing footer preserved (clause-licensed; no tool ownership).

H) Storage & access

Store originals and translations together in the approved repo; link them bidirectionally.
Track version & locale in metadata; use read-only links with MFA for Internal/Restricted.

I) Metrics (reported in §12)

% of artifacts with accessibility compliance (spot-checks).
Translation turnaround vs target; errata rate (<2% target).
Coverage by region/language vs plan.
Participant satisfaction pulse after sessions (caption quality, interpretation, clarity).

Standing guardrails: honor labels (Public/Internal/Restricted), keep neutrality, avoid idioms and advocacy language, and never paste Restricted content into external tools. All outputs remain clause-licensed; GRF does not own or develop tools; any implementation or commercialization occurs outside GRF via the appropriate Nexus entity.

Quality Assurance

Purpose. Make every input and output trustworthy, readable, and ready for hand-off. This section defines what must be checked before T-0 (pre-reads), after T-0 (AAR & lane artifacts), and how to manage redlines/versioning for clauses and policy drafts.

Roles (RACI summary)

Chair (A): final sign-off; may pause items that fail QA.
Science/Methods Lead (R): technical QA on evidence/methods.
Standards/Clause Lead (R): legal/standards QA; redlines & registry readiness.
Policy Lead (R): jurisdictional QA; oversight/remedy completeness.
Capital Lead (R): triggers/covenants clarity; diligence asks.
Media/Civic Lead (R): posture, plain language, accessibility, narrative risk checks.
Rapporteur (R): AAR structure, neutrality, references.
Governance Secretary (R/A): labels, COI, repository, link/access hygiene.
Advisors/Fellows (C): targeted peer review when requested.

16.1 Pre-read QA checklist (methods, assumptions, provenance)

When: T-6 → T-2. All pre-reads must pass QA by the T-2 freeze or move to a Working/Closed session.

A) Methods & evidence (Science/Methods Lead)

Methods named & versioned (e.g., model name, algorithm class, rev/date).
Parameters & ranges listed; validation metrics (e.g., RMSE/AUC) or replication note.
Uncertainty bands shown (P10/P50/P90) or equivalent; sensitivity drivers identified.
EVPI/gaps stated (what new data would most reduce uncertainty).
Provenance for each dataset (source, license, timestamp, transformations/QA).
Recency appropriate (≤12 months for dynamic topics, or rationale for older).
Observations vs assumptions clearly separated.
AI-assisted outputs marked; sources verified; no Restricted data fed to external AI.

B) Standards & policy readiness (Standards/Clause + Policy Leads)

Clause Pack (draft) includes baseline references and proposed redlines.
Collision notes: known standard/jurisdiction conflicts flagged.
Jurisdiction map present; oversight/remedy mechanisms sketched.

C) Capital & comms readiness (Capital + Media/Civic Leads)

Valuation prompts include exposure metrics and hypothetical triggers/covenants.
Narrative risk note (misreadings, misinformation vectors, EWI messages, on/off-record recommendation).

D) Compliance & accessibility (Governance Secretary + Media/Civic)

Labels applied (Public / Internal / Restricted) in header/footer/metadata.
COI declarations collected; required recusals pre-flagged.
Accessibility: tagged PDF/HTML or DOCX, alt text for images, ≥12pt font, contrast ≥4.5:1, descriptive links.
Links & permissions working; no “anyone with link” for Internal/Restricted.

Red flags (auto-HOLD)

Missing sources or unverifiable core claims.
Restricted material placed in Public pre-reads.
No uncertainty treatment or undisclosed conflicts.
Pre-reads delivered after T-2.

QA outcome stamp (add to cover page)

QA-PASS / QA-FIX (notes) / QA-HOLD (reason) • Reviewer • Date

16.2 AAR and artifact QA (neutrality, clarity, references)

When: T+1 → T+5 (AAR by T+3; lane artifacts by T+5).

A) AAR (Rapporteur + Chair)

Length ≤3 pages; plain language; neutral tone.
Structure present: Context → Facts → Uncertainties → Options → Decisions → Owners/Dates → Blockers.
Decisions written as verb + object + date; exactly one owner and one recipient per action.
References retrievable (URL/DOI/dataset/registry ID).
Label & licensing footer present (clause-licensed; no tool ownership).
COI & recusals logged; incidents (if any) noted.
Cross-consistency with lane artifacts (no contradictions).

B) Clause Pack Delta (Standards/Clause Lead)

Redline table (old → proposed) with type (Definition/Trigger/Covenant/Oversight/Remedy).
Clean copy registry-ready; no placeholders.
Collisions resolved or explicitly listed with options and owners.
Effective/transition dates included if applicable.
Registry submission path & editor of record identified.

C) Policy Option Note (Policy Lead)

Routes (statute/regulation/mandate) and oversight/remedy spelled out.
Readiness rating (Low/Med/High) with dependencies.
Pilot prompt (site/agency, timeline, metrics).
Recipient owner in RSB/NWG named.

D) Investment Note (Capital Lead)

Thesis + exposure metrics; the one predictor that matters most.
Triggers/covenants measurable; verification hooks.
Diligence asks & data-room list; no deal/price language.
Corridor lead named for GRA hand-off.

E) Comms Note (Media/Civic Lead)

Posture (On/Off record) with approvals.
Key messages (2–3) linked to evidence; EWI prompts aligned.
Narrative risk table (misreads, vulnerable groups, mitigations).
Localization plan (languages, accessibility assets) and owners.

F) Repository & permissions (Governance Secretary)

Stored in approved repo, labeled, versioned; links shared (no attachments for Internal/Restricted).
Acknowledgment requests sent to recipients; SLA clock started.

AAR & artifacts scoring (quick rubric)

3 = Excellent (meets all checks; ready now)
2 = Adequate (minor edits; does not change intent)
1 = Weak (material edits needed; may slip schedule)
0 = Unacceptable (hold; send to Working/Closed session)

16.3 Redlines & versioning of Clause Pack and Policy drafts

Goal: Keep a complete, auditable history of changes and ensure recipients always know what changed, why, and when.

A) Semantic versioning (all normative texts)

MAJOR = breaking change (new framework/authority; deprecations).
MINOR = substantive addition/change that keeps backward compatibility.
PATCH = typo/format fix; non-substantive clarification.

Filename & header example
Standards_ClausePackDelta_20251015_v2.1_Internal
Header fields: Title • Version • Label • Editor of Record • Source Baseline (ID) • Change Summary

B) Redline protocol (Clause Pack)

Baseline citation (registry ID & version).
Diff table (Old → Proposed) with rationale + evidence refs.
Collision log: where conflicts may occur (standards/jurisdictions) + options (A/B/C).
Clean copy for registry; effective/transition details.
Approvals: Chair sign-off → NSF editor acceptance (ticket/ID captured).

Post-merge hygiene

Update Change Log (who/what/why/date).
Link the registry ID back to the AAR and hand-off record.
Notify distribution with MAJOR/MINOR highlights (PATCH optional).

C) Policy draft versioning (Policy Option Note & draft text)

Version table on page 1 (vX.Y, date, sections changed).
Change matrix mapping draft sections to impacts (legal, operational, equity).
Jurisdiction map updated when scope expands.
Oversight/remedy fields must accompany any new power or mandate.
Localization tracking (which languages/editions exist; locale codes in filenames).

D) Governance & controls

Branching (if using doc control): draft/, review/, approved/; only Standards/Policy Leads can merge to approved/.
Two-reviewer rule for MAJOR/MINOR changes (Peer SME + Chair).
Freeze windows: after T-2 for pre-reads; after NSF submission for clauses (changes via new MINOR/PATCH).
Rollback: if a post-publication collision is found, issue PATCH with deprecation note and schedule a MINOR fix.

E) Retention & audit trail

Keep all versions for 6 years (Restricted: 2 years or per legal hold).
Preserve review comments, sign-offs, and COI/recusal notes with each version.

Ready-to-use QA stamps (paste into docs)

QA-PASS — Ready for distribution/hand-off.
QA-FIX — Minor edits needed (list below).
QA-HOLD — Material issues; move to Working/Closed session.
Reviewer: ___ Role: ___ Date: ___ Notes: ___

Standing guardrails: Neutrality; labels (Public/Internal/Restricted); clause licensing; membership ≠ governance; GRF does not own/develop tools; implementation/commercialization happens outside GRF via the appropriate Nexus entity.

Tooling & Repositories

Purpose. Give every participant a clear, safe, and predictable way to create, store, find, and link GRF materials—without leaks or confusion. This section defines where templates live, how files are named and tagged, how long we keep them, and how repositories link to standards registries and the CB calendar.

Principles

Single source of truth. One canonical copy per artifact, in an approved repository.
Least-privilege access. Read-only by default; edit access only to the owner/editor of record.
Labels everywhere. Public / Internal / Restricted in filename, headers/footers, and repo metadata.
Links, not attachments (except Public). All Internal/Restricted sharing is via authenticated links.
Traceability. Every artifact traces back to intake IDs and forward to registry/calendar records.

17.1 Document templates and storage locations

A) Template catalogue (standard, pre-filled with headers/metadata)

AAR (≤3 pages) — contains decision log table scaffold.
Clause Pack Delta — baseline citation, redline table, clean copy section.
Policy Option Note — policy routes, oversight/remedy, readiness, pilot prompts.
Investment Note — thesis, triggers/covenants, KPIs, diligence/data-room list.
Comms Note — on/off-record posture, key messages, EWI prompts, localization.
Evidence & Assumptions Pack — methods, parameters, uncertainty bands, EVPI.
Scenario Card — stressors, thresholds, failure modes, “no-regrets” hooks.
Handoff Cover Sheet — recipient, ask, due date, acceptance criteria.
KPI Summary (monthly) and Quarterly Track Review.
COI Declaration and COI Log.
Incident Report and Dispute Register.

Where to find templates: /GRF/Templates/ (read-only to all; editors can copy into track folders).

B) Canonical repository layout (example)

/GRF/
  /Templates/                       (read-only)
  /Tracks/
    /Research/
      /2025/08/
        /Pre-reads/                 (T-2 freeze)
        /Meeting/                   (agenda, slide deck)
        /Artifacts/                 (AAR, Clause, Policy, Investment, Comms)
        /Handoffs/                  (subfolders: GCRI, NSF, GRA, RSB-NWG, NewMedia)
        /Translations/              (locale-tagged copies; see §15.3)
        /Restricted/                (tight ACLs; no ICS links)
    /Innovation/…                   (same structure)
    /Policy/…                       (same structure)
    /Capital/…                      (same structure)
    /NewMedia/…                     (same structure)
  /Registry-Links/                  (NSF IDs, policy refs; index files)
  /CB-Calendar-Exports/             (sanitized agenda packets; ICS attachments)

C) Access roles (default)

Editors: Chair, relevant Committee Lead(s), Rapporteur (their artifact only), Governance Secretary.
Commenters: other Leads, Advisors/Fellows invited on the item, RSB/NWG focal(s) for localization.
Viewers: track distribution list (respecting label).
Vendors (interpretation/captions): time-bound access to only the labeled files needed (NDA required).

D) Where non-document assets live

Data & models (GCRI/TMDs): approved research/analytics repos; link from AAR/Evidence Pack (never embed datasets in docs).
Graphics/Explainers (New Media): /GRF/Assets/ with derivative exports (SVG/PNG/MP4) and an alt-text.txt sidecar.

17.2 Naming conventions, metadata, and retention

A) File naming (required)

[Track]_[Artifact]_[YYYYMMDD]_vX.Y[_PATCH]_[Label][_region][_locale]

Examples:
- Policy_AAR_20250824_v1.0_Public
- Research_ClausePackDelta_20250905_v2.1_Internal
- NewMedia_CommsNote_20251001_v1.2_Public_fr-CA
- Capital_InvestmentNote_20251112_v1.0_Internal_NA

Versioning: use MAJOR.MINOR (and _PATCH when needed) per §16.3.

B) Minimum metadata schema (stored in repo properties and in the doc header)

Track (Research/Innovation/Policy/Capital/NewMedia)
Artifact type (AAR, ClausePackDelta, PolicyNote, InvestmentNote, CommsNote, etc.)
Version (vX.Y[.Z])
Label (Public/Internal/Restricted)
Owner(s) (human) and Editor of Record
Recipients (entity + named owner)
Date created / last updated
Intake ID(s) (one or many)
Related registry ID(s) (NSF, policy refs)
Jurisdiction(s)/Region(s) (for localization)
Language/Locale (e.g., en, fr-CA, ar)
COI link (if applicable)
Status (Draft/Approved/Handed-off/Published)
Retention class (Public/Internal 6y; Restricted 2y unless extended)

Repos should block publishing if required metadata is missing.

C) Retention (aligns with §§7 & 16)

Public/Internal artifacts: retain 6 years (or as required by registry/contract).
Restricted artifacts: retain 2 years (or project term + 1 year), unless legal hold or registry rule requires longer.
COI records: 6 years from last activity.
Recordings: Public/Internal ≤ 12 months; Restricted by exception (define retention when created).
Deletion: only by Governance Secretary after retention expiry and verification that no legal/registry hold exists.

D) Link-sharing rules (enforced by repo policy)

Internal/Restricted: authenticated users only; view-only, download/print off by default; link expiry: Internal ≤ 90 days; Restricted ≤ 30 days.
Public: attachments allowed; otherwise, share links.
No “anyone with the link” for Internal/Restricted.
Watermark where supported; always require MFA.
Freeze: move Pre-reads to read-only at T-2 and archive with checksum.

17.3 Linkage to registries and calendars (read-only vs edit access)

A) Registries (NSF, policy reference indices)

From artifact to registry:
- Clause Pack Delta includes a field “Registry submission: [NSF-Ticket/ID]” once filed.
- Policy Option Notes cite controlling texts with stable IDs/URLs.
From registry back to artifact:
- When NSF publishes, record Published ID/Version in the artifact metadata and update the /Registry-Links/ index.
Permissions:
- Edit: Standards/Clause Lead (NSF editor of record); Policy Lead (policy index).
- Read-only: Chair, Governance Secretary, other Leads, distribution list (as label permits).

B) CB master calendar integration (see §13.2)

Every calendar item (Public Discussion, Working, Closed Technical) includes:
- Links to agenda, pre-reads folder (read-only), and the meeting link (with passcode/waiting room).
- Deadlines auto-created and linked: AAR (T+3), Artifacts (T+5), Handoff Acks (≤5 biz days), T+14 checkpoint.
Read-only vs edit:
- Read-only ICS: all members see sanitized titles/times (no Restricted content in ICS).
- Full details: only the distribution list with repo access sees links and labels.
Attachment policy:
- Public: attach PDFs if useful (also link to repo).
- Internal/Restricted: no file attachments; links only to authenticated repo items.

C) Bidirectional status signals (light automation recommended)

When an artifact’s Status changes to Handed-off or Published, the repo posts a note (or webhook) to:
- The CB calendar event (adds a comment with the link/version).
- The handoff log (updates recipient, acknowledgment clock).
When NSF registry updates an item, mirror the Published ID into:
- The original Clause Pack Delta metadata and
- The AAR that references it (append “Published as … on YYYY-MM-DD”).

D) Edit discipline & audit

Who edits? Only the Editor of Record (named in metadata) and the Governance Secretary can change approved artifacts; others comment/suggest.
Freeze points:
- Pre-reads freeze at T-2 (edits require Chair approval).
- Approved artifacts become comment-only after hand-off; changes require a version bump and change note.
Audit trail: repos must preserve version history and who/when/what for each change (immutable logs preferred).

E) Offline and embargo scenarios

If a recipient requires air-gapped review, the Secretary creates an embargo package:
- Encrypted archive + checksum + printed watermark.
- Courier or controlled transfer; sign-back receipt.
- Upload a stub record in the repo noting the transfer date, recipient, and unlock date.
Public-release embargo: store the Public file with “Publish on YYYY-MM-DD HH:MM” metadata; keep Internal version until release.

Quick checklists

When creating a new artifact

Use the correct template from /GRF/Templates/.
Save to the right track/month folder.
Apply filename pattern and metadata.
Set label in header/footer and repo.
Share link (not attachment) per label; verify permissions.

Before hand-off

Handoff Cover Sheet filled.
Recipients & named owners added in metadata.
Registry/Calendar links included.
Status set to Approved; permissions reduced to comment for non-owners.

After registry/calendar updates

Add NSF Published ID or policy reference to metadata.
Update /Registry-Links/ index.
Post note to CB calendar event; tick handoff log.

Standing guardrails

Label everything (Public / Internal / Restricted); respect least-privilege access; use MFA.
Don’t paste Restricted content into external tools.
GRF outputs are clause-licensed; membership ≠ governance; GRF does not own or develop tools. Any implementation/commercialization runs outside GRF via the appropriate Nexus entity.

Risk & Safety Management (Meetings & Content)

Purpose. Keep people safe, protect sensitive information, and comply with legal/ethical constraints while running efficient GRF sessions. This section covers sensitive topic handling, meeting safety (physical & virtual), and media/recording/consent.

Roles

Governance Secretary (SEC): lead for risk checks, labeling, access control, incident logging.
Track Chair (CH): final call in-room; may pause/redirect or change openness level.
Facilitator (FAC): enforce rules live; remove/redirect participants if needed.
Safety Officer / Duty-of-Care Contact (SAFE): named person per event (virtual/physical) for safety concerns.
Media/Civic Lead (MED): manages posture (on/off-record), press, and public materials.
Standards/Policy Leads: flag legal/export/sanctions risks; coordinate with counsel if required.

18.1 Sensitive topics protocol (sanctions/PEP checks, duty of care)

When to invoke: any item involving sanctions/export controls, Politically Exposed Persons (PEPs), national security/critical infrastructure, personal/health data, minors or vulnerable groups, ongoing litigation, indigenous/traditional knowledge, crisis/trauma topics, or proprietary/vendor-confidential material.

A) Screening & classification (before T-2)

Label early: propose Restricted by default for the topics above; downgrade only with Chair + SEC approval.
Sanctions/PEP check: SEC screens presenters and named counterparties using approved lists/tools.
- If hit/uncertainty: consult legal/compliance; restrict participation; move to Closed Technical or defer.
Export-control sweep: Standards/Policy Leads flag jurisdictions & categories (e.g., dual-use tech). Apply participation limits if required.
Data minimization: strip PII/sensitive fields; anonymize/aggregate; share only what’s needed.
Vendor & interpreter NDAs: ensure third-party service providers are under NDA and compliant systems (MFA, encryption).

B) Document & room controls

Access: invite-only; authenticated sign-in; waiting room; watermark docs; disable downloads for Internal/Restricted.
Redactions: produce a Public/Internal summary; keep Restricted content in a separate deck/folder.
COI & recusals: collect before the meeting; enforce partial/full recusal as needed.

C) Duty of care (people)

Content advisories: add a short content note at the start for trauma/crisis topics.
Participation options: allow camera-off/audio-only and chat-only participation.
Break protocol: Facilitator may call a 2-minute pause if participants show distress.
Follow-up: SAFE shares support resources post-session when appropriate.

D) Decision tree (quick)

Topic flagged sensitive? → Restricted label + screening.
PEP/sanctions uncertainty? → Closed Technical + legal consult.
Data sensitivity high? → Redact; anonymize; share via secure repo only.
Dispute about sensitivity? → Chair rules; log in AAR; option to escalate to PNG simulation if contested.

18.2 Meeting safety and venue guidelines (physical/virtual)

A) Virtual meetings (default hardening)

Entry: authenticated users; waiting room + passcode; lock meeting after 10 minutes.
Roles: at least two hosts (CH/FAC and SEC); SAFE named in chat and on slide 1.
Controls: host-only screen share; disable file transfer and private DMs (except to hosts); limit annotation; admit speakers just-in-time.
Recording: off by default; if on, announce clearly (banner + verbal) and confirm label; Restricted segments not recorded unless approved by SEC.
Breakout rooms: same rules apply; one host per room for Restricted topics.
Removal: FAC may mute/remove and lock re-entry for conduct or security breaches; log incident.

B) Physical meetings (minimum standards)

Pre-venue check: accessibility (ramps, elevators), clear emergency exits, first-aid/medical contact, security desk if needed.
Registration & badges: color dots for no-photo preference; badge color for Public/Internal/Restricted areas.
Room setup: SAFE & evacuation map visible; seating for mobility devices; assistive listening where possible.
Bag & device policy (if needed): visual check at entry for Restricted sessions; request device stickers or sealed pouches if required by host venue policy.
Photo/filming zones: marked; outside zones require consent (see 18.3).

C) Conduct & rapid response

Harassment or disruption: apply §6 protocol; FAC pauses; SEC logs; CH may terminate session or relocate to Closed Technical.
Security incident: follow §7.4 timeline; isolate, revoke access, notify, remediate.
Medical or safety issue (in-person): SAFE coordinates with venue/emergency services; debrief logged by SEC.

18.3 Media presence, recording, and consent procedures

Default posture: No media and no recording unless explicitly stated as Public in the invite and on slide 1.

A) Declaring posture (before T-2)

Comms Note sets On-record / Off-record posture and approved spokespeople.
Invite wording: clearly states if press is allowed and which segments (e.g., opening 10 minutes only).
Media registration: journalists and camera crews must be pre-approved and badged; agree to house rules.

B) Recording & transcripts

Public segments:
- May be recorded with verbal + on-screen notice.
- Host controls recording; store in approved repo; apply Public/Internal label accordingly.
Internal/Restricted segments:
- Not recorded by default. Exceptions require SEC approval + consent and must be stored Restricted with defined retention.
Transcripts/captions: treat as the same label as the session; review/redact names if needed before any sharing.

C) Consent & attribution

Individual consent: speakers consent to recording at start (verbal or written); participants notified clearly.
Image consent (in-person): use venue signage + optional consent stickers; photographers briefed on no-photo zones and no-face shots without consent in non-public segments.
Attribution rules: if Chatham House Rule is invoked, participants may use information but may not reveal identity or affiliation of speakers.

D) Press interaction

During sessions: press ask questions only in designated Public Q&A; no 1:1 interviews in Restricted spaces.
After sessions: interviews handled by MED with approved spokespeople; reference Comms Note messages.
Social media: live-posting only for Public segments; use approved hashtags/messages; no quoting individuals from Internal/Restricted segments.

E) Publishing & takedowns

Review window: MED reviews any official clips/slides before release; ensure label matches.
Errata/takedown: if sensitive content leaks, SEC initiates §7.4 response; MED issues corrected statement or removal request.

Quick checklists (paste into planning docs)

Sensitive Topic Prep (by T-2)

Label set (likely Restricted); redactions done.
Sanctions/PEP screen complete; hits cleared or session moved to Closed Technical.
Vendor NDAs & secure platforms confirmed.
Duty-of-care note added; SAFE named.

Virtual Room Hardening

Waiting room + passcode + lock after 10’
Host-only share; disable file transfer/PMs
Recording OFF (unless Public segment)
SAFE posted; co-hosts assigned

Physical Venue Readiness

Accessibility & exits verified
Badges/no-photo system ready
First-aid/security contacts posted
Photo/filming zones marked

Media & Recording

Posture set in Comms Note (On/Off record)
Press pre-approved & briefed; segment limits defined
Consent language in opening slide & verbal
Storage label & retention set

On-the-day: FAC Script (first 60 seconds)

“Today’s item is labeled [Public/Internal/Restricted]. Recording is [on/off]. If you have a COI, declare now. Media are [present/not permitted] for [segment X] only. Our Duty-of-Care contact is [SAFE name] in chat/at the back of the room. Thank you—let’s proceed.”

Standing guardrails

Respect labels (Public / Internal / Restricted), COI/recusals, and no fundraising or tool ownership in GRF rooms.
Apply least-privilege access, MFA, and link-sharing rules.
Use §7.4 incident timelines for any breach; document everything in the repository and CB calendar.

Training & Onboarding

Purpose. Give every new contributor a fast, predictable ramp; ensure Chairs and Committee Leads can run the universal model to standard; keep everyone current as rules and tools evolve.

Owners

Governance Secretary (SEC): program admin, records, invites, LMS/repo hygiene.
Track Chair (CH): mentoring & sign-offs for their track.
Committee Leads (SCI/STD/POL/CAP/MED): teach lane bootcamps; grade drills.
Rapporteur Guild / Facilitation Team: practical drills & shadowing.
CB Liaison: calendar blocks, load balancing.

19.1 30/60/90-day quick-start for new contributors

Entry prerequisites (Week 0)

Accounts provisioned; MFA enabled (§7).
Read §2–§11 (alignment, operating model, roles, outputs, handoffs).
Sign Code of Conduct & COI; complete labels & confidentiality micro-course (§6, §7).
Access to /GRF/Templates/ and your track’s current month folder (§17).

Day 1–30 (Learn & Observe)

Goals: grasp the cadence; practice evidence & labeling; contribute safely.

Orientation (Week 1)
- 60-min live walkthrough of PNG → GRF → Monthly Cycle (slides + Q&A).
- Repository tour: where pre-reads, AARs, artifacts, and handoff logs live.
- Accessibility & inclusion primer (§15).
Shadowing (Weeks 1–4)
- Attend one Public Discussion and one Working Session (your track).
- Observe COI calls, labels in practice, and the Stop–Clarify–Decide protocol (§14.1).
- Pair with a buddy (Fellow or Lead).
First task (by Day 30)
- Produce a 1-page Evidence & Assumptions memo for a small agenda item using the template.
- Pass the Pre-read QA checklist (§16.1).
- Micro-quiz (10 questions): labels, COI, handoffs.
- Deliverable: Memo filed; QA-PASS; quiz ≥ 80%.

Day 31–60 (Assist & Co-author)

Goals: co-write artifacts; practice neutral style; touch handoffs.

Co-authoring
- With Rapporteur: draft section(s) of an AAR (≤3 pp, §10.1).
- With a Lead: co-draft one lane artifact OR a redline table (Clause Pack Delta) (§10.2–10.5).
Tooling & hygiene
- Apply naming, metadata, and link-sharing rules (§17.2).
- Run through handoff cover sheet and log an acknowledgment (§11.0, §11.6).
Milestone (by Day 60)
- One co-authored artifact gets Chair sign-off; handoff acknowledged ≤5 business days.
- Deliverable: AAR section + one artifact; both archived; handoff ack logged.

Day 61–90 (Lead a slice & Close the loop)

Goals: run part of the meeting; own an output to DoD; demonstrate follow-through.

On-mic drill
- Present 3–5 minutes during segment 2 or 3 (Evidence or Options) at T-0, with Facilitator coaching.
Ownership
- Own one handoff package end-to-end (cover sheet + links + SLA tracking to T+14).
Milestone (by Day 90)
- Definition of Done: artifact published, recipient acked ≤5 days, T+14 status updated.
- Readiness check: Chair marks Ready for Independent Tasks.

90-day completion badge (recorded in /GRF/Training/Records)

✅ Orientation + micro-quiz
✅ Evidence memo (QA-PASS)
✅ Co-authored artifact (signed)
✅ Live presentation (3–5 min)
✅ Handoff to T+14

19.2 Chair & Committee Lead bootcamps (role-specific drills)

Format: two 2-hour sessions + 60-min capstone lab. Small cohorts (6–10), scenario-based, graded rubrics.
Passing: ≥80% on rubrics + one acceptable live drill. Certificates stored in /GRF/Training/Records.

A) Track Chair Bootcamp

Module 1 — Orchestration
- Build a T-0 agenda from messy intake; set timeboxes; apply session caps (§13.3).
- Drill: turn 5 intake items into a 3-item agenda; write decision questions.
Module 2 — Live control
- Run Stop–Clarify–Decide; handle COI/label disputes; move to Closed Technical.
- Drill: simulated disruption (lobbying attempt, unlabeled slide, time overrun).
Module 3 — Outcomes & KPIs
- Judge when options are “tested enough”; define owners/dates; ensure AAR by T+3.
- Capstone: chair a 20-min mock meeting; score on neutrality, pace, and clarity.

Chair rubric (examples)

Agenda fit (0–5), Guardrails adherence (0–5), Decisions quality (0–5), KPI awareness (0–5).

B) Science/Methods Lead (SCI)

Methods transparency; uncertainty bands; EVPI; provenance.
Drill: fix a pre-read with missing validation & stale sources; pass §16.1.
Capstone: 5-minute Evidence Brief with clear assumptions vs observations.

C) Standards/Clause Lead (STD)

Redline craft; collision mapping; registry readiness.
Drill: convert decisions into clauses (Definition/Trigger/Covenant/Oversight/Remedy).
Capstone: produce a Clause Pack Delta (redline + clean) that earns an NSF “ticket created”.

D) Policy/Regulatory Lead (POL)

Jurisdiction maps; oversight/remedy; pilotability.
Drill: resolve a three-jurisdiction collision; propose two policy routes.
Capstone: Policy Option Note with feasibility & first pilot prompt.

E) Capital/Investment Lead (CAP)

Exposure framing; triggers/covenants; diligence hooks; no deal-making.
Drill: design a trigger set with verification hooks tied to clause IDs.
Capstone: Investment Note with the “one predictor that flips the stance”.

F) Media/Civic Lead (MED)

Narrative risk; on/off-record posture; EWI alignment; accessibility cues.
Drill: create a 150-word Comms snippet with localization notes.
Capstone: Comms Note + public explainer outline (plain language).

G) Facilitator & Rapporteur Labs (recommended for all)

Facilitator lab: timekeeping, equitable turns, de-escalation; run a 10-min “Options under stress”.
Rapporteur lab: turn meeting notes into a ≤3-page AAR with verb+object+date decisions; reference verification.

Bootcamp outputs

One graded artifact per lane (filed in the month’s /Artifacts/Training/), plus rubric sheets.

19.3 Annual refreshers and policy updates

Cadence & scope

Annual Refresher (2 hours, per track):
- What changed: standards/clauses, security controls, templates, dispute steps.
- Hot-spots: common QA failures; incident patterns; KPI deltas (Sec. 12).
- Equity & access: new translation/localization coverage; caption/interpretation vendors (§15).
- Mini-scenario lab to re-practice Stop–Clarify–Decide and handoff SLAs.
Policy update bulletins (quarterly, 20 min async + 20 min office hours):
- Summarize changes in §6–§11 & §16–§18; link to new templates; “what you must do differently next month.”

Renewals & attestations

COI renewal: annually; before first session of the year (§6.2).
Security & privacy attestation: annual checklist (MFA, device encryption, link rules; §7).
Accessibility pledge: confirm you can produce accessible docs or request support (§15).
Template acknowledgement: confirm use of the latest versions (§17.1).

Performance ties (light but real)

Missing the annual refresher → watch status on next review (§5.3).
Two consecutive QA-HOLD outcomes → required re-training in the relevant bootcamp.
Repeated SLA misses (AAR/T+3 or artifacts/T+5) → temporary cap on agenda items (§13.3) until back to green.

Records & metrics

Attendance, scores, and certificates stored in /GRF/Training/Records with metadata (role, date, module, score).
Training KPIs reported quarterly: % current on refresher, average rubric scores, re-training rate, time-to-competency for newcomers (≤90 days target).

Ready-to-run checklists

New Contributor (print this)

Accounts + MFA set up; COI & labels course done.
Read §2–§11; tour /GRF/Templates/.
Shadow Public Discussion + Working Session.
Evidence memo (QA-PASS) by Day 30.
Co-author one artifact + AAR section by Day 60.
Lead a 3–5 min segment + complete one handoff to T+14 by Day 90.

Chair (for each new cohort)

Assign buddies; schedule shadow seats.
Approve Day-30 topics suitable for newcomers.
Give a 15-min feedback huddle post-presentation.

Governance Secretary

Send invites; provision repo spaces; log completions.
Ensure training decks/templates reflect latest §10, §11, §16–§18.
Publish quarterly training calendar; maintain /GRF/Training/Records.

Standing guardrails: neutrality; COI & confidentiality; labels (Public/Internal/Restricted); membership ≠ governance; GRF does not own or develop tools; implementation and commercialization happen outside GRF via the appropriate Nexus entity.

Track Overlays (How Each Track Applies the Universal Model)

These overlays show how each track uses the same monthly engine (Intake → Pre-reads → T-0 → AAR/Artifacts → Handoffs → T+14) with track-specific inputs, focus, outputs, and recipients. Plain language, zero jargon.

20.1 Research Track Overlay — “Turning risks into testable intelligence”

A) Who leads most here

Primary: Science/Methods Lead (R); Chair (A)
Strong support: Standards/Clause, Policy/Regulatory, Capital/Investment, Media/Civic
Rapporteur & Secretary: as in §4

B) Typical inputs (what arrives at intake)

Earth Observation (EO) feeds, sensor streams, open data portals
Model snapshots + change logs (e.g., parameters, training data, validation)
Field observations, case evidence, replication notes
Data licenses & provenance statements

Required pre-reads (T-6 → T-2)

Evidence & Assumptions Pack (methods, parameters, uncertainty bands, EVPI)
Provenance ledger (sources, timestamps, licenses, transformations)
Scenario cards (2–4) with stressors

C) Session focus at T-0 (what we actually do)

Align on facts vs assumptions
Compare model vs observed; decide if gaps are material
Set/update uncertainty bands; capture EVPI (what data would most help)
Select no-regrets indicators to watch across tracks

Example decision questions

“Do we accept parameter range R for Q3 simulations?”
“Which two data gaps get resourced this month (owner/date)?”

D) Outputs (by T+3/T+5)

AAR (≤3 pp) — facts, uncertainties, options, decisions, owners/dates
Methods tasks list (to GCRI/TMDs): data pulls, validation runs, experiment plan
Clause Pack delta (if terms change): definitions/units/quality flags
Scenario brief for Policy (policy-ready assumptions + ranges)
Signal set for Capital (leading indicators; thresholds to test)
Comms note snippet (plain-language “what we know/what we don’t”)

E) Handoffs (who receives what & when it’s “done”)

→ GCRI/TMDs: Methods tasks + test plan
Accepted when: task IDs exist, owner named, compute/data access confirmed, window scheduled.
→ NSF: Clause deltas (definitions/units/quality levels)
Accepted when: registry ticket/ID created; editor assigned.
→ Policy (via RSB/NWGs): Scenario brief for localization/pilotability
Accepted when: focal named; first pilot check-back date set.
→ GRA: Signal set (watch metrics)
Accepted when: corridor lead logs interest or evidence ask.
→ New Media: Short public explainer (if labeled Public)
Accepted when: posture set; owner and release plan noted.

F) Definition of Done (Research)

Uncertainties explicit (e.g., P10/P50/P90); every claim sourced
At least one method/data task launched with a date and owner
If terms changed, a clean clause draft exists and is filed to NSF
AAR and links archived; T+14 status posted

Common pitfalls to avoid

Hidden assumptions; stale sources; unclear licenses on data

20.2 Innovation Track Overlay — “Proving technologies before the world depends on them”

A) Who leads most here

Primary: Innovation owner (within Steering Committee) + Capital/Investment Lead (for triggers); Standards/Clause Lead (controls)
Support: Policy/Regulatory (preconditions), Science/Methods (test design), Media/Civic (narrative risk)
Chair/Facilitator/Rapporteur/Secretary: as in §4

B) Typical inputs

Product/system design, safety case, threat models, red-team reports
Digital-twin or sandbox test results (pass/fail logs)
Performance, fairness, reliability metrics; user impact assessments
Ops playbooks, rollback plans, audit trails

Required pre-reads (T-6 → T-2)

Test dossier (what was tested, how, results, known gaps)
Risk model & failure modes (incl. equity/rights checks)
Proposed controls (standards/clauses) + readiness gate proposal (Alpha/Beta/Pilot)
Valuation prompts (exposure, key metrics, candidate triggers)
Narrative risk note (misuse/misread risks, EWI messaging)

C) Session focus at T-0

Stress test failure modes and safety case
Decide readiness gate (Go / Go-with-guardrails / No-go)
Identify conformance controls and monitors (what, how, who, when)
Clarify policy preconditions and data needed for diligence

Example decision questions

“Does the control set C make this safe enough for a limited pilot?”
“Which two triggers must be live-monitored from day 1?”

D) Outputs

AAR (≤3 pp) with gate decision and conditions
Risk Test Report (concise) + guardrails (monitors, thresholds, rollback)
Clause Pack delta (controls/definitions/triggers)
Policy Preconditions Note (what must exist in law or mandate)
Investment Note (thesis, KPIs, triggers/covenants, diligence asks)
Comms Note (on/off-record posture; safety messaging)

E) Handoffs

→ NSF: Conformance controls & triggers
Accepted when: registry ticket/ID exists; collision plan noted.
→ Policy (RSB/NWGs): Preconditions & route options
Accepted when: focal named; feasibility rated; pilot window penciled.
→ GRA: Investment Note & diligence asks
Accepted when: corridor lead assigned; evidence/data-room path opened.
→ GCRI/TMDs: Expanded test plan or simulation harness
Accepted when: tasks scheduled; resources confirmed.
→ New Media: Public-safe explainer (if appropriate)
Accepted when: posture confirmed; owner and channel/date set.

F) Definition of Done (Innovation)

Gate decision recorded with conditions and monitoring plan
At least one trigger/covenant written as clause text and filed to NSF
Diligence checklist sent; corridor owner named
AAR/artifacts filed; T+14 status updated

Common pitfalls to avoid

“Demo-ware” evidence; missing rollback plans; vague triggers without verification hooks

20.3 Policy Track Overlay — “Diplomatic infrastructure for governance”

A) Who leads most here

Primary: Policy/Regulatory Lead (R); Standards/Clause Lead (legal text)
Support: Science/Methods (assumption validity), Capital/Investment (finance-ability signals), Media/Civic (public posture)
Chair/Facilitator/Rapporteur/Secretary: as in §4

B) Typical inputs

Draft statute/mandate/treaty text; oversight & remedy sketches
Jurisdiction map; collision tables across laws/standards
Implementation notes (capacity, budget, sequencing)
Impact assessments (legal, operational, equity)

Required pre-reads (T-6 → T-2)

Draft sections with change marks + Clause Pack (draft)
Jurisdiction & collision map (where conflicts likely)
Scenario cards for consequences/unintended effects
Finance-ability prompts (is this structure investable/enforceable?)
Comms posture proposal (on/off-record; key public messages)

C) Session focus at T-0

Simulate unintended effects; tighten oversight/remedy
Harmonize multi-jurisdiction clauses; choose route(s) (statute, regulation, mandate)
Decide pilot path and localization needs
Confirm finance-ability signals (what covenants/metrics enable capital later)

Example decision questions

“Which clause set D avoids the cross-border collision and remains enforceable?”
“Where should the first pilot run, and what success metric proves readiness?”

D) Outputs

AAR (≤3 pp) with chosen route(s) and owners/dates
Policy Option Note (readiness, dependencies, pilot prompts, oversight/remedy)
Simulation-attested draft sections (clean text) + Clause Pack delta (if any)
Investment signal note (if relevant): what makes this financeable later
Comms Note (public explainer outline; localization cues)

E) Handoffs

→ RSBs/NWGs: Policy Option Note + pilot prompts
Accepted when: focal named; Proceed/Scope/Hold recorded; first milestone set.
→ NSF: Clause text aligned to standards
Accepted when: registry ticket/ID created; editor assigned.
→ GRA: Finance-ability signals (optional)
Accepted when: corridor lead notes path/constraints.
→ GCRI/TMDs: Modeling assumptions for scenario runs
Accepted when: task IDs exist; schedule agreed.
→ New Media: Explainer brief for public understanding
Accepted when: posture set; owner and release plan logged.

F) Definition of Done (Policy)

At least one viable route endorsed with a named drafter and date
Oversight/remedy mechanisms written, not just implied
Pilot pathway identified (place/agency/timeline/metric)
Collision notes either resolved or explicitly queued with owners
AAR/artifacts filed; T+14 status posted

Common pitfalls to avoid

Ambiguous authority; missing remedies; policy that is not pilotable

Quick cross-track reference (what’s “unique” per overlay)

Element	Research	Innovation	Policy
Core decision	Methods/data acceptance & uncertainty	Readiness gate + guardrails	Legal route + oversight/remedy
Signature artifact	Methods tasks + Scenario brief	Risk Test Report + Triggers	Policy Option Note + Draft sections
Primary recipient	GCRI/TMDs	NSF (controls) & GRA (signals)	RSBs/NWGs (localization/pilots)
Key risk	Stale/uncertain evidence	Unsafe or unverified tech	Jurisdiction collision / unenforceability
“No-regrets” move	Fund top EVPI data gap	Ship with monitors + rollback	Pilot in one willing jurisdiction

Standing guardrails for all tracks: neutrality; COI & confidentiality labels (Public / Internal / Restricted); membership ≠ governance; all outputs are clause-licensed; GRF does not own or develop tools; implementation and commercialization happen outside GRF via the appropriate Nexus entity.

20.4 Capital & Investment Track Overlay — “Where global risk meets capital intelligence”

A) Who leads most here

Primary: Capital/Investment Lead (R)
Support: Standards/Clause (controls/covenants), Policy/Regulatory (dependencies), Science/Methods (drivers/metrics), Media/Civic (posture)
Chair/Facilitator/Rapporteur/Secretary: as in §4

B) Typical inputs (at intake)

Pipeline briefs (corridor/theme), exposure models, impact theses
Scenario ranges from Research (drivers, indicators)
Early covenant/trigger ideas; verification hooks (how we’ll check)
Sanctions/PEP prelim checks where relevant; ESG guardrails

Required pre-reads (T-6 → T-2)

Valuation & Exposure Pack (probability × impact ranges, key metrics, sensitivity)
Trigger/Covenant draft tied to clause IDs (verification source, threshold, action)
Policy dependencies (permits, mandates, data-sharing)
Narrative risk note (what can be misread; on/off-record proposal)

C) Session focus at T-0 (what we actually do)

Align on the thesis and one predictor that matters most
Test 2–4 trigger/covenant sets under stress (data gaps, policy lag, equity impacts)
Decide what evidence is still needed (diligence asks) and who will provide it
Map corridor fit and next gate (outside GRF)

Example decision questions

“Which trigger set is monitorable on day 1 and reduces downside most?”
“What single dataset must be verified before this enters the corridor?”

D) Outputs (by T+3/T+5)

AAR (≤3 pp) — decisions (verb+object+date), owners, recipients
Investment Note — thesis, exposure, triggers/covenants, KPIs, diligence asks, corridor fit
Clause Pack delta (if needed) — covenant/trigger text; oversight/remedy linkages
Policy notelet — minimal policy preconditions or conflicts (if any)
Comms Note — posture (on/off-record), key messages, EWI alignment

E) Handoffs (who receives what & acceptance)

→ GRA (primary): Investment Note + diligence checklist
- Accepted when: corridor lead named; stage & next gate set; diligence room opened/requests sent; compliance (sanctions/PEP) initiated.
→ NSF: Clause deltas for covenants/triggers
- Accepted when: registry ticket/ID created; editor of record assigned; collision plan noted.
→ Policy (RSBs/NWGs): short dependency note if legal preconditions exist
- Accepted when: focal named; feasibility status set; first check-back scheduled.
→ Research/GCRI: evidence gaps to close; metric definitions
- Accepted when: task IDs exist; owner + window scheduled.
→ New Media (only if Public): posture + explainer hooks
- Accepted when: comms owner named; release plan logged.

F) Definition of Done (Capital)

Triggers/covenants are measurable, sourceable, and written as draft clause text (if needed)
One predictor identified and recorded; KPIs listed with units and update cadence
GRA next gate agreed; owner named; diligence actions started
AAR + artifacts filed; T+14 status updated

Common pitfalls to avoid

Deal/pricing talk inside GRF; vague triggers without verification; ignoring sanctions/PEP checks; missing policy preconditions

20.5 New Media & Civic Foresight Overlay — “Public trust and narrative integrity”

A) Who leads most here

Primary: Media/Civic Lead (R)
Support: Science/Methods (evidence digest), Policy/Regulatory (standards for public communication), Standards/Clause (disclosure/attribution clauses), Capital (market-sensitivity), RSB/NWGs (localization)
Chair/Facilitator/Rapporteur/Secretary: as in §4

B) Typical inputs (at intake)

Evidence digest (what’s known/unknown, with sources)
Early-warning indicators (EWI) and thresholds from Research/Innovation
Platform/policy changes that affect information integrity
Audience analysis and comms risk map (vulnerable groups, likely misreads)

Required pre-reads (T-6 → T-2)

Narrative Risk Note (misreadings, dis/misinformation vectors, sensitivities)
Key message candidates (2–3 lines) + posture proposal (on/off-record)
Localization cues (languages/dialects, examples, accessibility)
Evidence packet with citations (for transparency pages)
Draft EWI prompts (what to say if threshold X is crossed)

C) Session focus at T-0 (what we actually do)

Agree on on/off-record posture and spokespersons
Stress-test key messages against evidence and equity impacts
Align EWI messaging: who says what, when, and where
Set localization plan (regions/languages/formats) with RSB/NWGs

Example decision questions

“What will the public most likely misunderstand—and how do we prevent harm?”
“Which EWI message is safe to pre-authorize if indicator I crosses threshold T?”

D) Outputs (by T+3/T+5)

AAR (≤3 pp) — posture decision, owners/dates
Comms Note — key messages, EWI alignment, narrative risk table, on/off-record, channels, timeline
Public explainer outline (if label allows) with plain language and accessible formats (alt text, captions)
Localization plan — languages, regional examples, accessibility services (captions/interpretation)
Feedback requests to Policy/Research — facts that need clearer wording; signals to validate

E) Handoffs (who receives what & acceptance)

→ New Media teams / Comms owners (per region): Comms Note + explainer outline
- Accepted when: regional comms owner(s) named; posture confirmed; delivery plan & date set; translation/accessibility plan defined.
→ RSBs/NWGs: localization plan + region-ready messages
- Accepted when: focal named; languages confirmed; community channels chosen; check-back scheduled.
→ Policy/NSF (if standards touch comms): disclosure/attribution clauses; platform guidance
- Accepted when: registry ticket/ID created (if clause text) or policy owner named for guidance docs.
→ Research/GCRI: signal validation/clarifications
- Accepted when: tasks opened; owner + response window set.

F) Definition of Done (New Media)

Posture decided; key messages tied to evidence; EWI prompts finalized
Localization plan active with named owners and dates; accessibility services booked if needed
Public explainer (if any) cleared for the right label; AAR + artifacts filed; T+14 status updated

Common pitfalls to avoid

Announcing before evidence is settled; ignoring vulnerable audiences; inconsistent messages across languages; forgetting on/off-record boundaries

Cross-cutting guardrails (apply to both overlays)

Neutrality; membership ≠ governance; clause-licensed outputs; GRF does not own or develop tools.
Respect labels (Public / Internal / Restricted), COI & confidentiality, and no fundraising/deal-making in GRF rooms.
Use the handoff acceptance criteria in §11.6 and quality bars in §10 and §16.

Governance Appendices

Use these appendices as ready-to-run materials: role briefs, expanded RACI, fill-in forms, labeling cheat-sheets, and the full dispute policy (PNG simulation + arbitration clause).

21.1 Role descriptions (detailed) & selection criteria

A) Core leadership roles

Track Chair (Leaders Council) — Honorary, non-fiduciary

Mandate: Set monthly agenda; uphold neutrality/guardrails; ensure outputs & handoffs meet SLAs.
Decision rights: Timeboxing; scope/risk calls in-room; sign-off on AAR and lane artifacts.
Success criteria: KPI health (Sec. 12), on-time artifacts (T+3/T+5), handoff acceptance ≥95%, incident-free compliance.
Selection criteria: ≥2 cycles of proven orchestration; strong neutrality record; two leader nominations; COI cleared.

Science/Methods Lead (SCI)

Mandate: Evidence quality, methods transparency, uncertainty bands, EVPI.
Deliverables: Evidence & Assumptions Pack; segment 2 brief; methods tasks to GCRI/TMDs.
Selection: Demonstrated rigor (replication/validation), provenance discipline, plain-language skill.

Standards/Clause Lead (STD)

Mandate: Translate decisions into clause text (Definition/Trigger/Covenant/Oversight/Remedy); manage collisions; registry readiness.
Deliverables: Clause Pack (draft & delta), clean copy for NSF registry.
Selection: Redline craft, multi-jurisdiction awareness, change-control hygiene.

Policy/Regulatory Lead (POL)

Mandate: Map enforceable policy routes; oversight/remedy; pilotability with RSBs/NWGs.
Deliverables: Policy Option Note; simulation-attested draft sections.
Selection: Comparative law/policy experience; ability to harmonize collisions.

Capital/Investment Lead (CAP)

Mandate: Turn risk into investable signals; write measurable triggers/covenants (no deals in GRF).
Deliverables: Investment Note; corridor fit; diligence asks.
Selection: Exposure modeling; accountability hooks; sanctions/PEP awareness.

Media/Civic Lead (MED)

Mandate: Narrative integrity; EWI alignment; on/off-record posture; accessibility/localization cues.
Deliverables: Comms Note; public explainer outline (when allowed).
Selection: Evidence-linked messaging; misinformation risk sense; accessibility practice.

B) Delivery roles

Facilitator (FAC)

Mandate: Run the room; apply “Stop–Clarify–Decide” protocol; protect time & safety.
Selection: Neutral moderation; de-escalation skills.

Rapporteur (RAP)

Mandate: Capture decisions as verb+object+date; draft AAR (≤3 pp).
Selection: Fast, neutral writer; reference discipline.

Governance Secretary (SEC)

Mandate: Labels, COI, access, calendar, incident/dispute logs, archival, acks.
Selection: Detail-oriented; security & privacy hygiene.

C) Extended ecosystem roles (often recipients)

GCRI/TMD Owner: Methods/data/testing task lead.
NSF Editor of Record: Registry intake and publication.
RSB/NWG Focal: Localization + pilot owner.
GRA Corridor Lead: Pipeline stage and next-gate setter.
New Media Comms Owner: Regional messaging & delivery.
Neutral Simulation Lead (for §14.2): Runs PNG simulation in cross-track disputes.
Safety Officer (SAFE): Duty-of-care contact per event.

Selection & renewal follow §5 (merit, COI cleared, 2-year terms, annual reviews, removal for cause).

21.2 RACI tables (expanded per track)

Legend — R: Responsible · A: Accountable · C: Consulted · I: Informed

21.2.1 Universal RACI (core activities, all tracks)

Activity / Output	Chair	SCI	STD	POL	CAP	MED	FAC	RAP	SEC	GCRI	NSF	RSB/NWG	GRA	New Media
Intake triage & agenda	A	C	C	C	C	C	C	I	R	I	I	I	I	I
COI screening & labels	C	I	I	I	I	I	I	I	R/A	I	I	I	I	I
Pre-read QA (Sec. 16.1)	A	R	R	R	R	R	I	I	R	C	C	C	C	C
Run T-0 meeting	A	C	C	C	C	C	R	I	R	I	I	I	I	I
AAR (≤3 pp)	A	C	C	C	C	C	I	R	R	I	I	I	I	I
Clause Pack delta	A	C	R	C	C	C	I	I	R	I	C/A	I	I	I
Policy Option Note	A	C	C	R	C	C	I	I	R	I	I	C/A	I	I
Investment Note	A	C	C	C	R	C	I	I	R	C	I	I	C/A	I
Comms Note	A	C	C	C	C	R	I	I	R	I	I	C	I	C/A
Handoff logging & acks	I	I	I	I	I	I	I	I	R/A	C	C	C	C	C
T+14 follow-through	A	C	C	C	C	C	I	I	R	C	C	C	C	C
KPI summary (Sec. 12)	A	C	C	C	C	C	I	I	R	I	I	I	I	I

21.2.2 Research — overlay deltas

SCI: A for Evidence & Assumptions Pack; R for methods tasks to GCRI/TMDs.
STD: R for definition/units updates.
POL/CAP/MED: C for scenario brief, signals, and public explainer.

21.2.3 Innovation — overlay deltas

CAP: co-A on trigger/covenant quality;
STD: A on conformance clauses;
POL: R on preconditions note;
GCRI/TMDs: C on expanded testing harness.

21.2.4 Policy — overlay deltas

POL: A on Policy Option Note & draft sections;
STD: R on harmonized clauses;
RSB/NWG: A for pilot acceptance & localization plan.

21.2.5 Capital — overlay deltas

CAP: A on Investment Note & corridor fit;
GRA: A on next gate outside GRF;
STD: R if clause-level covenants needed.

21.2.6 New Media — overlay deltas

MED: A on posture, key messages, EWI alignment;
RSB/NWG: R on localization & channels;
POL/STD: C for disclosure/attribution clauses.

21.3 Ethics & COI forms (annual + ad-hoc)

Store blank copies in /GRF/Templates/ and signed PDFs in /GRF/Compliance/COI/.

A) Annual Code of Conduct Acknowledgment (one page)

Name / Role / Track / Organization
I affirm: neutrality; civility; no lobbying or deal-making in GRF; no tool-ownership claims; label & confidentiality compliance; incident reporting duty.
Signature / Date

B) Annual COI Declaration (short form)

Identity: name, email, role(s), jurisdictions of residence/work.
Financial interests (past 24 months & current): equity/options, consulting, grants, IP royalties—entity, nature, amount band (range only).
Professional roles: boards, employment, advisory posts relevant to GRF items.
Personal ties: close family/partner ties with material interests.
Advocacy & publications: public positions on topics likely to arise.
Sanctions/PEP status: self/organization screening disclosure (Y/N).
Mitigations requested: (e.g., standing partial recusal).
Certification: true & complete; update within 7 days when facts change.
Signature / Date

C) Ad-Hoc COI & Recusal Form (per item)

Item title & date
Nature of conflict: financial/professional/intellectual/personal (explain)
Proposed mitigation: full recusal / partial (factual clarifications only) / mitigated participation
Chair/SEC decision: (tick & initial)
Logged by SEC: (COI log ID)

21.4 Confidentiality & data-labeling guide (quick reference)

Labels (pick one per document/record)

Public — safe to publish/share.
Internal — GRF distribution only; not public.
Restricted — need-to-know only; sensitive (legal, security, personal, proprietary).

Apply label in three places

Filename: [Track]_[Artifact]_[YYYYMMDD]_vX.Y_[Label]
Header/Footer: label, date, owner
Repo metadata: label field + permissions

Handling matrix

Action	Public	Internal	Restricted
Share outside GRF	Allowed	Chair/SEC approval	No
Attach to calendar/email	Allowed	Links only	No (links only; tight ACLs)
Download/print	Allowed	Usually off	Off by default
Record meetings	With notice	With notice	By exception; SEC approval
Translate via MT tools	Allowed	Allowed with SEC-approved tools	Human-only via secure channel

Decision tree (before sharing)

Contains PII, vendor confidential, sanctions/PEP, or security content? → Restricted.
Not finalized, draft policy/clauses, or raw analysis? → Internal.
Cleared for public audiences? → Public.

Email footer for Internal/Restricted

“This material is [Internal/Restricted] to GRF distribution. Do not forward or repost. COI and confidentiality rules apply.”

21.5 Dispute resolution policy text (PNG + arbitration clause)

A) Policy statement

GRF resolves disagreements quickly, fairly, and with minimal disruption. We use a three-step ladder:

Session-level resolution via Facilitator protocol and Chair ruling (§14.1).
PNG simulation for cross-track/governance disputes (§14.2).
Arbitration if still unresolved (§14.3).

Retaliation for raising disputes is prohibited.

B) Step 1 — Session-level protocol (summary)

Stop–Clarify–Decide within 3 minutes.
Chair may: continue, extend 5 minutes, table to Working/Closed, reframe, or recuse.
Rapporteur logs; SEC updates Dispute Register within 24h.

C) Step 2 — PNG simulation (required before arbitration)

Trigger conditions: multi-track impact; recipient rejects on principle; repeat dispute (≤60 days); clause/policy collision.
Timeline: acknowledge (2 days), pack & invites (by day 5), simulation (by day 10), findings (day 12), decision (day 15).
Outputs: Simulation Findings Note + Resolution Matrix; decision by Chair/Chairs’ Council/RSB/GSB/NSF as scope demands.
Confidentiality: labeled; Closed Technical if Restricted.

D) Step 3 — Arbitration clause

Scope. Any unresolved dispute arising from or relating to GRF governance, processes, or outputs after completion of the PNG simulation step.

Seat and governing law.

Seat/Venue: Zurich, Switzerland.
Governing law: Swiss law, read together with PNG/GRF instruments.

Rules & tribunal.

Arbitration under a reputable Swiss arbitration institution’s rules.
Tribunal of one or three arbitrators as per rules; English language.

Process.

Notice of Arbitration served on the other party and the Governance Secretary, with the PNG Simulation Findings attached.
Tribunal constituted within ~30–45 days; procedural schedule within 15 days thereafter.
Target final award within 120 days of constitution (extendable by tribunal).

Confidentiality & data.

Proceedings confidential; filings and awards treated as Restricted unless publication is legally required or mutually agreed.
Parties protect sensitive data; redactions permitted.

Remedies.

Declaratory and injunctive relief; orders to perform procedural obligations (e.g., run pilot, register clause).
Fees/costs allocation at tribunal’s discretion. Monetary damages generally out of scope for honorary/non-fiduciary roles.

Non-retaliation.

Parties shall not penalize, remove, or otherwise retaliate against individuals for participating in the dispute process. Protective orders may be requested.

Enforcement.

Award is final and binding; SEC records outcome; CB calendar/records updated with any mandated actions.

Placement & maintenance

Where these appendices live: /GRF/Handbook/Appendices/ (read-only to all; versioned).
Owner: Governance Secretary. Review cadence: annually, or after any material incident.
Change log fields: date, section, change summary, editor of record, approval (Chair/Trustee).

One-page printable cheats (include at end of the PDF)

Roles at a glance (bullets + who to call).
Labeling matrix (Public/Internal/Restricted).
Stop–Clarify–Decide flow.
Handoff acceptance SLA (≤5 business days).
Arbitration clause header (seat, law, language).

Standing guardrails: Neutrality; COI & confidentiality; membership ≠ governance; clause-licensed outputs; GRF does not own or develop tools; commercialization and implementation occur outside GRF via the appropriate Nexus entity.

Written by: GRF

Was this article helpful?

Like 0 Dislike 0 0 of 0 found this article helpful.

Continue reading

Next: Nexus Entities Overview

Cart review

Monthly Public Discussion — Universal Operating Model

About This Guide

PNG Alignment & Governance Map

Universal Operating Model Overview

Roles & Responsibilities (RACI)

Leadership & Access

Ethics, COI & Conduct

Security, Privacy & Digital Hygiene

Monthly Cadence (Repeatable Playbook)

Standard 90-Minute Agenda (With Objectives)

Required Outputs (Every Month)

Handoffs & Acceptance Criteria

Measurement & Reporting

Calendaring & Coordination

Dispute Resolution & Escalation

Inclusion, Accessibility & Translation

Quality Assurance

Tooling & Repositories

Risk & Safety Management (Meetings & Content)

Training & Onboarding

Track Overlays (How Each Track Applies the Universal Model)

Governance Appendices

Continue reading

Leave a Reply Cancel reply