# Lab

### Part 0 — Charter Identity, Authority, and Binding Invariants

#### 1. Instrument nature and authority posture

1.1 This Charter constitutes the constitutional governance instrument for the Future of Society Lab (the **“FoS Lab”**), a governed, AI-assisted, community-operated **standards, frameworks, and intelligence commons** for social cohesion, legitimacy, rights protection, service reliability, and systemic resilience.

1.2 The FoS Lab provides **governance infrastructure** (records, registries, conformance, correctionability, handling controls, and publication discipline) that enables **auditable decision influence** without assuming sovereign authority, investigative powers, operational command, or speech arbitration.

1.3 The FoS Lab is not a state body, law enforcement entity, intelligence agency, investigative body, court, welfare authority, electoral authority, platform moderator, censorship body, or command center.

#### 2. Binding invariants for any FoS Instance claiming conformance

2.1 **Two-stack firewall.** FoS Lab is governance-only; execution remains external and lawful in competent institutions and licensed delivery stacks.

2.2 **Non-executing perimeter.** FoS Lab performs no investigations, surveillance operations, intelligence collection operations, coercive targeting, arrests, removals, prosecutions, adjudications, sanctions designation decisions, benefits termination decisions, operational command, censorship decisions, or electoral administration decisions.

2.3 **Validity-by-record.** Standing arises only from record-valid acts reflected in canonical registers, current pointers, and supersession chains.

2.4 **Handling classes & staged release.** Public-Safe (A) / Controlled (B) / Restricted (C) with purpose binding, distribution logs, access gates, expiry enforcement, and leakage testing.

2.5 **Correctionability.** No silent edits; explicit supersession; diffs; dependency propagation; contestation propagation; status is machine-readable and visible on the truth surface.

2.6 **Conformance & reproducibility.** Material claims require conformance suites, test vectors, signed conformance reports, and validity windows; replication cells apply for high reliance.

2.7 **Neutrality & anti-capture.** COI disclosures, recusals, influence caps, procurement neutrality, reviewer rotation, and sponsor concentration controls are mandatory.

2.8 **Bounded reliance.** Intended use, prohibited use, limitations, uncertainty cues, expiry, and remedy clocks are mandatory for publishable objects.

2.9 **Rights baseline.** Non-discrimination, pluralism, protected participation, due-process posture, and remedy/appeal paths are first-class.

2.10 **Do-no-harm intelligence rule.** No publication that increases targeting, repression, harassment, destabilization, or discrimination risk; dual-use content is handling-elevated or refused.

2.11 **Privacy & minimization.** Purpose limitation, minimization, aggregation defaults; no individual-level profiling objects absent explicit lawful basis, Restricted handling, and recorded safeguards.

2.12 **No gatekeeper rule.** FoS Lab does not arbitrate speech, truth, legitimacy, ideology, or political preference; it publishes correctionable objects and transparency minima, not censorship.

2.13 **No PII on-chain.** No personal data on the Nexus Ledger; only tamper-evident anchors/pointers as permitted by handling rules.

#### 3. Precedence and conflict rules

3.1 Invariants prevail over overlays.\
3.2 Handling and rights safeguards prevail over publication convenience.\
3.3 Registered records prevail over informal statements.\
3.4 Supersession chains prevail over copies.\
3.5 Safety and protected participation prevail over speed in contested or high-risk contexts.

#### 4. Non-endorsement and reliance constraints

4.1 No output implies regulatory approval, judicial opinion, law-enforcement directive, ministerial direction, or “official classification” unless recorded as a designated act by a competent authority with stated scope, validity window, and exclusions.

4.2 Conformance claims are bounded and non-endorsing; reliance is limited to the scope stated in the conformance report and the object’s reliance bounds.

***

### Part 1 — Purpose, Scope, and Operating Thesis

#### 1. Purpose and public-good function

1.1 The FoS Lab converts multi-stakeholder contributions into structured, versioned, reusable objects for the future of society under deterministic lifecycle rules, explicit reliance bounds, handling discipline, and correctionability.

1.2 The FoS Lab exists to reduce variance in societal outcomes by making civic, service, and societal risk claims **comparable, testable where feasible, audit-ready, and correctable**—without collapsing rights, privacy, pluralism, community sovereignty, or lawful authority boundaries.

#### 2. Operating thesis

2.1 Societies remain free, safe, and governable under fast-moving shocks when decision influence is supported by: provenance-bound evidence; explicit uncertainty; time-boxed validity windows; contestable records; and correction/remedy clocks.

2.2 “Correctionability” is treated as a societal safety primitive: errors are inevitable; hidden errors are unacceptable; corrections must be visible, attributable to objects (not people), and non-retaliatory.

#### 3. Scope of “future of society”

3.1 The scope includes governed objects for:\
3.1.1 cohesion, trust, legitimacy, and grievance pathways;\
3.1.2 community safety and resilience (defensive governance, non-operational);\
3.1.3 due-process and procedural integrity interfaces;\
3.1.4 rights and liberties impact evidence;\
3.1.5 service reliability and welfare integrity (non-termination posture);\
3.1.6 migration/displacement integration supports (non-targeting);\
3.1.7 digital civic infrastructure and accountability receipts;\
3.1.8 information integrity governance (provenance, disclosure, correction);\
3.1.9 societal impacts of health shocks and risk communications integrity;\
3.1.10 economic inclusion and livelihood stress indicators (safe granularity);\
3.1.11 housing and urban service continuity evidence;\
3.1.12 education mobility pathway comparability objects;\
3.1.13 climate/disaster recovery integrity receipts;\
3.1.14 critical infrastructure dependencies as social stability risks;\
3.1.15 cyber and identity harm governance (victim protection);\
3.1.16 AI/algorithmic governance (override, recourse, drift, audit);\
3.1.17 aid/relief integrity interfaces (non-execution boundary);\
3.1.18 cross-border corridor overlays and lawful sharing patterns;\
3.1.19 social conflict early-warning indicators with strict abuse prevention;\
3.1.20 remedy, reconciliation, and civic repair objects (non-adjudicative).

3.2 System-of-systems dependencies treated as societal stability risks include: energy grids, telecom/5G/6G, cloud/software supply chain, geopolitics/sanctions, commodity shocks, pandemics, and synthetic media acceleration.

#### 4. Intended users and outcomes

4.1 Intended users include public agencies, municipalities, civil society, humanitarian operators, critical infrastructure operators, auditors/assurers, multilaterals, philanthropies, researchers, and community leaders.

4.2 Outcomes include auditable decision influence, safer information ecosystems, measurable integrity of relief and service delivery, improved protections for vulnerable populations, and reduced harm from opaque or drifting decision systems.

#### 5. Output classes

5.1 Outputs include standards; frameworks; profiles/implementation guides; taxonomies/ontologies; defensive typology libraries; artifacts; conformance suites and reports; release bundles; corrections/supersessions; interoperability mappings; learning modules; **AEP-SOC**; and reports/subscriptions with dependency banners.

5.2 Outputs are objects with lifecycle state and registry pointers; documents are views.

***

### Part 2 — Boundary, Firewall Doctrine, and Non-Executing Perimeter

#### 1. Boundary of the Lab

1.1 The FoS Lab provides: identity/participation governance; forms-first record workflows; canonical registers and truth surfaces; handling-separated indexing and retrieval; publication/versioning/correction discipline; conformance operations; replication and plugfests; report desks/subscriptions; instance kits; and federation-safe interoperability scaffolding.

1.2 The FoS Lab does not provide enforcement, operational planning, targeting, investigations, or speech moderation decisions.

#### 2. Two-stack firewall alignment

2.1 FoS Lab is governance-only: standards/schemas, evidence integrity, validity-by-record, handling and safeguards, conformance, release/correction discipline, and audit structures.

2.2 Execution occurs only outside the Lab in lawful institutional processes and licensed delivery stacks; the Lab does not widen the regulated perimeter.

2.3 Integrations are limited to mappings, compatibility notes, conformance-tested connectors, and evidence packaging patterns.

#### 3. Non-executing perimeter

3.1 FoS Lab does not: investigate, surveil, target, arrest, prosecute, adjudicate, designate sanctions, terminate benefits, command operations, censor, administer elections, or direct policing.

3.2 FoS Lab does not publish operational tactics, targeting guidance, destabilization methods, propaganda optimization, harassment playbooks, evasion recipes, or instructions enabling repression.

3.3 Outputs must include intended use, prohibited use, limitations/uncertainty, expiry/review, and correction/dispute clocks.

#### 4. Refusal and redirection discipline

4.1 High-harm requests are refused or redirected into defensive governance outputs (controls, transparency minima, safe detection patterns, conformance tests, incident clocks).

4.2 Legitimate sensitive contexts follow staged release: public-safe abstract first; controlled/restricted appendices only if purpose-bound, expiry-bound, and logged.

#### 5. No gatekeeper rule

5.1 The FoS Lab does not decide what people may say or believe. It publishes governance artifacts and correction mechanisms; it does not police speech.

***

### Part 3 — Validity-by-Record, Registers, Current Pointers, and Designated Acts

#### 1. Validity-by-record rule

1.1 Standing arises only from record-valid acts executed through FoSLP workflows and reflected in canonical registers, current pointers, and supersession chains.

1.2 Informal guidance, emails, slide decks, or summaries have no standing unless represented as record-valid objects.

#### 2. Canonical registers

2.1 Each FoS Instance maintains canonical registers for:\
2.1.1 object identity and lifecycle state;\
2.1.2 current pointers and supersession chains;\
2.1.3 conformance suites and conformance reports;\
2.1.4 handling elections, distribution logs, access grants, expiry enforcement;\
2.1.5 COI disclosures, recusals, influence cap states; sanctions/appeals;\
2.1.6 report editions with dependency banners and contested propagation;\
2.1.7 AI provenance/tool enablement for governed workflows;\
2.1.8 integrity incidents (stop-the-line, remediate clocks, corrective publications).

#### 3. Designated acts

3.1 Minimum designated acts include:\
3.1.1 adoption and recognition as Current;\
3.1.2 release publication and current-pointer movement;\
3.1.3 issuance of conformance claims and signed conformance reports;\
3.1.4 issuance of **AEP-SOC** for external reliance (audit/procurement/diligence/disclosure);\
3.1.5 sanctions/revocations/reinstatements; withdrawals; emergency reliance constraints; pointer freezes; handling reclassification decisions.

#### 4. Dual logging and mismatch lock

4.1 Where cross-institution reliance is claimed, designated acts are dual-logged: GRF Council Register (legal record) + Nexus Ledger anchoring (tamper-evident pointer).

4.2 Mismatch lock applies: disagreement renders the act **Inoperative (Mismatch)** until reconciled; dependent objects must display warnings.

#### 5. Local-only standing

5.1 Deployments without required dual logging must label affected acts **Local-Only Standing** and disclose portability limits.

***

### Part 4 — Definitions and Societal Evidence Primitives

#### 1. AEP-SOC (Assurance & Evidence Pack)

1.1 AEP-SOC is a sealed bounded-reliance determination artifact, expressing posture without leaking protected inputs, including: scope; assumptions; uncertainty; provenance; handling inheritance; lawful-basis posture (if any); minimization posture; conformance references; validity window; correction clocks; dispute paths; and dependency declarations.

#### 2. Decision influence chain

2.1 A traceable record of how inputs become objects, how claims are tested, what reliance is permitted, what uncertainties remain, and how correction and remedy function.

#### 3. Protected participation

3.1 A governance posture comprising confidentiality elections, retaliation safeguards, access minimization, role-marker validity, and remedy clocks.

#### 4. Harm taxonomy

4.1 Canonical harm classes include discrimination, coercion, repression enablement, harassment, doxxing, violence enablement, deprivation harms, and procedural injustice; these govern handling elevation, refusal, staged release, and conformance requirements.

#### 5. Truth surface

5.1 The examiner-operable surface showing for each object: current/superseded/contested/withdrawn status; conformance status; validity window; reliance bounds; and correction lineage.

***

### Part 5 — Canonical Object Model, IDs, Lifecycle States, Publication Gates

#### 1. Objects, not documents

1.1 Authority attaches only to a versioned object with record-valid lifecycle state and registry pointer; documents are views.

1.2 Releases and report editions are immutable; changes occur only through corrections/supersessions/withdrawals with diffs and dependency propagation.

#### 2. Canonical object families

2.1 **STD-SOC** Standards (rights safeguards, minimization, transparency minima, handling rules, protected participation).\
2.2 **FRM-SOC** Frameworks (governance/control frameworks; bounded reliance).\
2.3 **PRF/IG-SOC** Profiles/Implementation Guides (jurisdiction/community overlays; explicit deltas; no semantic forks).\
2.4 **TAX/ONT-SOC** Taxonomies/Ontologies (services, harms, shocks, obligations; drift-tested).\
2.5 **TYP-SOC** Typologies (defensive abuse/fraud/harassment typologies at safe granularity).\
2.6 **ART-SOC** Artifacts (method cards, rubrics, checklists, model/dataset cards, assurance-case cards).\
2.7 **AEP-SOC** Evidence Packs (sealed bounded-reliance determinations).\
2.8 **CS-SOC / CR-SOC** Conformance Suites / Reports (harnesses, vectors, signed results, validity windows).\
2.9 **REL-SOC / COR-SOC** Releases / Corrections-Supersessions (immutable bundles; governed changes).\
2.10 **RPT-SOC / SUB-SOC** Reports / Subscription Channels (immutable editions; dependency banners).\
2.11 **MAP/IOP-SOC** Mappings/Interoperability Profiles (equivalence limits; testable transforms).\
2.12 **WGC-SOC / RM-SOC / DR-SOC / CFW-SOC** Charters / Role Markers / Decision Records / Calls for Work.\
2.13 **CONSENT-SOC / TRANSP-SOC** Consent and Transparency Elections.

#### 3. Object ID rules

3.1 IDs are stable and never reused; versions reflect semantic change; supersession is explicit and machine-readable.

#### 4. Mandatory metadata and deterministic publication blockers

4.1 Publishable objects must include: scope/exclusions; handling election; intended use; prohibited use; reliance bounds; limitations/uncertainty; validity window; expiry/review; correction/dispute paths with clocks; provenance/rights attestations; COI link; dependencies/compatibility; jurisdiction label; harm-prevention statement.

4.2 Missing mandatory metadata blocks publication.

4.3 Objects with credible targeting/coercion risk must include explicit prohibited-use statements and default to Controlled/Restricted handling or refusal.

***

### Part 6 — Records-First Governance, Roles, Due Process, Stop-the-Line

#### 1. Record-valid acts

1.1 All governance actions occur only through record-valid acts: onboarding, COI, handling elections, WG chartering, role marker issuance, releases, conformance submissions, corrections, disputes/appeals, waivers, sanctions, reinstatements, withdrawals, pointer freezes, publication.

1.2 AI may draft and prefill; standing arises only upon human-authorized recorded submission under valid role markers.

#### 2. Minimum governance spine

2.1 Records & Register Officer.\
2.2 Handling & Safety Officer.\
2.3 COI & Ethics Officer.\
2.4 Conformance Lead.\
2.5 Editorial Lead (Publication Desk).\
2.6 Dispute Resolution Panel Lead (rotation rules).\
2.7 Protected Participation & Remedy Officer.\
2.8 Rights Safeguards Steward.\
2.9 Information Integrity Steward (provenance/disclosure/corrections posture).

#### 3. Separation of duties

3.1 No single actor may originate, verify, and publish the same high-reliance claim without independent review.

3.2 Waivers must record scope, duration, compensating controls, and auto-expiry; repeated waivers trigger governance review.

#### 4. Due process and clocks

4.1 Decisions that move pointers, publish reliance-bearing objects, impose sanctions, withdraw releases, or reclassify handling require Decision Records.

4.2 Dispute and appeal clocks are mandatory; contested status propagates to dependent objects and report references.

#### 5. Stop-the-line authority

5.1 Integrity incidents may trigger pointer freezes, publication pauses, access revocation, recall attempts where feasible, and public-safe incident abstracts where lawful.

***

### Part 7 — Handling, Safety, Staged Release, Harm Prevention

#### 1. Handling classes

1.1 **A Public-Safe:** broadly shareable; no sensitive targeting value; minimal harm risk.\
1.2 **B Controlled:** limited distribution; purpose-bound; logged; time-boxed.\
1.3 **C Restricted:** deny-by-default; explicit authorization; strict purpose binding; enhanced logging; minimization.

#### 2. Societal misuse taxonomy (non-exhaustive)

2.1 Repression enablement; coercive targeting; harassment/doxxing; discriminatory profiling; destabilization tactics; propaganda optimization; election interference enablement; extremist facilitation; re-identification attacks; coercive surveillance.

#### 3. Refusal and redirection

3.1 Misuse-category requests are refused or redirected into defensive outputs that do not enable harm.

#### 4. Staged release

4.1 Controlled/Restricted work must yield public-safe extracts where feasible (controls, limitations disclosures, safe indicators); infeasibility is recorded with rationale.

#### 5. Leakage prevention and testing

5.1 Handling segregation must hold across indices, retrieval, assistants, embeddings, exports, and connectors. Leakage testing is mandatory per release, quarterly, and after major platform changes; failures trigger stop-the-line.

***

### Part 8 — Neutrality, COI, Competition-Safe Mode, Anti-Capture

#### 1. COI disclosure and recusal

1.1 COI disclosures are mandatory, recorded, auditable; recusals are enforced by role-marker gating.

#### 2. Influence caps and sponsor concentration

2.1 Default cap: no single organization controls more than **20%** of reviewer/maintainer role markers per object family/release cycle, unless an overlay sets a stricter cap.

2.2 Sponsor concentration triggers governance review and compensating controls.

#### 3. Competition-safe protocol

3.1 Multi-entity settings require competition-safe agenda templates, prohibited-topic gates, minutes discipline, procurement neutrality posture, and “no deal-making” controls.

#### 4. Misrepresentation

4.1 False endorsement claims trigger takedown, public clarification, sanctions ladder, and appeal rights.

***

### Part 9 — Conformance, Reproducibility, Plugfests, Drift Governance

#### 1. Conformance discipline

1.1 High-reliance claims require conformance suites and signed conformance reports with validity windows; conformance is bounded and non-endorsing.

1.2 Conformance scope must disclose exclusions, assumptions, and known limitations.

#### 2. Replication cells

2.1 Independent reruns are required for high-reliance claims; failures trigger notices, pointer freezes, withdrawals, and remediation clocks.

#### 3. Plugfests

3.1 Plugfests validate interoperability across AEP-SOC schemas, consent/handling enforcement, audit receipts, contested propagation, and federation rules.

#### 4. Drift governance

4.1 Drift testing covers taxonomy drift, mapping equivalence drift, assistant refusal/handling drift, and AI lifecycle drift. Material drift triggers reliance tightening and status changes on the truth surface.

***

### Part 10 — Identity, Participation, Guild System, Credits, KPIs

#### 1. FoS Passport and role markers

1.1 **FoS Passport** captures expertise, jurisdictions, languages, and COI. Authority arises only from role markers.

1.2 Role markers are scoped (object family, handling class, duration, purpose) and revocable upon misconduct or conformance failure.

#### 2. Authentication and authorization

2.1 SSO/MFA with step-up for Controlled/Restricted; RBAC+ABAC with purpose/timebox; Restricted is deny-by-default.

#### 3. Work units

3.1 Guilds, Working Groups, Review Pools, Replication Cells, Clinics, Publisher Rooms, and Incident Rooms.

#### 4. Credits and anti-gaming

4.1 Credits accrue only on accepted record-valid outcomes; verification/replication outrank drafting; rotation caps apply; clawbacks apply for misconduct.

#### 5. KPIs

5.1 Membership growth; verification throughput; conformance coverage; correction responsiveness; dispute clock performance; handling compliance; integrity incident rate; protected participation performance; dependency hygiene.

***

### Part 11 — Assistive AI, Intelligence Operations, Content Studio, Constitutional Forms

#### 1. Handling-separated intelligence surfaces

1.1 Indices are handling-separated; cross-class reconstruction is prohibited.

1.2 Recycling pipelines convert deliberations into candidate objects only through record-valid workflows.

#### 2. Assistive AI boundaries

2.1 AI may draft, classify, triage, and summarize within handling constraints; it may not approve, certify, investigate, target, enforce, adjudicate, censor, or simulate official determinations.

2.2 Tool allowlists, logging, human override, and kill-switch evidence are mandatory for high-impact workflows.

#### 3. AI provenance and reproducibility

3.1 Provider/model identifiers, version pins, tool enablement, and configuration sufficient for reproducibility and drift accountability are recorded for publishable outputs.

#### 4. Content studio and normalization

4.1 Templates for standards, frameworks, AEP-SOC, conformance, and reports; no silent semantic edits; meaning changes require correction/supersession.

#### 5. Constitutional forms

5.1 Record-valid acts are executed by constitutional forms; AI may prefill only from authorized sources under handling rules.

***

### Part 12 — Social Cohesion, Trust, and Legitimacy Lane

#### 1. Cohesion objects

1.1 Governance-grade indicators and measurement discipline for cohesion/trust with uncertainty cues, safe granularity, and do-no-harm safeguards.

#### 2. Legitimacy and grievance pathways

1.2 Objects for grievance intake, remedy clocks, transparency minima, and contestation propagation.

#### 3. Non-targeting rule

1.3 No individual-level targeting artifacts; aggregation and minimization are default.

***

### Part 13 — Public Safety, Community Safety, and Violence Prevention Lane

#### 1. Community safety governance

1.1 Defensive governance objects for prevention and resilience, excluding operational tactics and coercive targeting.

#### 2. Crisis escalation integrity

1.2 Safe-granularity escalation indicators, incident clocks, and communications integrity objects.

#### 3. Victim protection

1.3 Safeguards for harassment and coercion harms; minimization and confidentiality elections are mandatory.

***

### Part 14 — Rights, Liberties, Due Process, Protected Participation Lane

#### 1. Rights impact evidence

1.1 Standardized rights impact artifacts, recourse objects, and appeal clocks.

#### 2. Protected participation

1.2 Whistleblowing protections, retaliation safeguards, confidentiality elections, and auditability.

#### 3. Non-discrimination controls

1.3 Mandatory disparate-impact guardrails for high-impact evidence objects; any deviations require recorded rationale and compensating controls.

***

### Part 15 — Social Protection, Services, Relief Integrity Lane

#### 1. Service continuity evidence

1.1 Evidence patterns for service reliability (housing, utilities, health access, education access) and recovery integrity.

#### 2. Relief and assistance integrity

1.2 Aid integrity and accountability receipts; fraud typologies at safe granularity; strict non-termination posture.

#### 3. Equity safeguards

1.3 Do-no-harm safeguards against exclusion; grievance and remedy clocks mandatory.

***

### Part 16 — Information Integrity, Media Ecosystems, Synthetic Media Lane

#### 1. Defensive posture

1.1 Provenance labeling, disclosure semantics, correctionability objects, and conformance suites for safety.

#### 2. No weaponization

1.2 Prohibits persuasion optimization playbooks, destabilization tactics, or influence-operation enablement.

#### 3. Transparency minima

1.3 Outputs include limitations and uncertainty cues to avoid overclaim and panic amplification.

***

### Part 17 — AI and Algorithmic Governance Lane

#### 1. High-impact systems governance

1.1 Objects for tool provenance, drift retest clocks, human override, recourse/appeal, auditability receipts, and “decision influence” disclosure.

#### 2. No automated authority

1.2 The Lab does not deploy AI to decide eligibility, enforcement action, surveillance action, or coercive outcomes.

#### 3. Conformance vectors

1.3 Red-team vectors focus on rights harms, coercion risk, leakage risk, refusal correctness, and misrepresentation resistance.

***

### Part 18 — Publication Discipline, Subscriptions, Communications Integrity

#### 1. Publication as governed act

1.1 Publication assigns standing, handling, reliance bounds, expiry, and correction clocks; informal dissemination is non-authoritative.

#### 2. Edition immutability and banners

1.2 Reports are immutable; updates only via correction/supersession; dependency banners propagate contested/withdrawn status.

#### 3. Subscription channels

1.3 Governed distribution objects define audience eligibility, purpose binding, retention rules, and auditability.

#### 4. Communications integrity

1.4 Public claims must match register truth; misleading claims are integrity incidents requiring correction and possible sanctions.

***

### Part 19 — Security, Auditability, Retention, DR, Cost Governance, Remedies, Wind-Down

#### 1. Audit logs

1.1 Immutable logs cover access, retrieval, submissions, lifecycle transitions, distributions, publications, and admin changes; legal hold supported.

#### 2. Retention and minimization

1.2 Handling- and jurisdiction-specific; Restricted emphasizes minimization and verified destruction where lawful; Public-Safe releases remain permanent.

#### 3. Disaster recovery and integrity

1.3 DR preserves register integrity and correction lineage; restore drills are record-valid acts.

#### 4. Supply chain integrity

1.4 Component inventory and vulnerability clocks mandatory; stop-the-line triggers apply.

#### 5. Cost governance

1.5 Quotas, anomaly detection, rate limits; no pay-to-publish influence; standing arises from record-valid acts.

#### 6. Remedies and appeals

1.6 Remedies include corrections, supersessions, withdrawals, pointer freezes, role revocations, conformance suspensions, and corrective publications; appeals follow clocks.

#### 7. Wind-down

1.7 Wind-down preserves Public-Safe releases and correction lineage; Controlled/Restricted follow minimization and legal holds; final status notice publishes portability limits.

***

### Binding Baselines

1. **Governance-only:** standards, frameworks, evidence packs, conformance, correctionability, publication discipline.
2. **Non-executing:** no investigations, surveillance, targeting, coercive operations, enforcement, adjudication, censorship.
3. **Validity-by-record:** only registered objects and acts have standing.
4. **Correctionability:** explicit lineage and contestation propagation; no silent edits.
5. **Rights + safety:** protected participation, minimization, refusal/redirection for misuse.
6. **Firewall doctrine:** strict separation from enforcement and operational command.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.therisk.global/organization/cooperation/nexus-guilds/future-of-society/lab.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.