# II. Mission

### Part 2 — Mission, Mandate, Scope Boundary, and Reliance

#### 1. Mission

1.1 **Mission statement.** The Guild exists to measurably reduce systemic digital risk by stewarding web resilience as critical infrastructure through open, reproducible, rights-preserving R\&D, enterprise-grade measurement doctrine, and correctionable evidence artifacts.

1.2 **Outcome orientation.** The Guild’s work is governed by outcomes that remain testable under scrutiny, including:\
1.2.1 reduced exploitability and cascade risk across the web stack;\
1.2.2 improved integrity, contestability, and correctionability of web-risk claims;\
1.2.3 increased interoperability and comparability across jurisdictions, standards bodies, and enterprises;\
1.2.4 safer adoption of emerging web capabilities (AI agents, decentralized infrastructure) without enabling harm;\
1.2.5 measurable improvement in accessibility and inclusion as resilience, not “compliance theatre.”

1.3 **Public-good posture.** The Guild advances methods and shared infrastructure that make web risk governance cheaper, faster, and more reliable for all adopters—especially critical infrastructure operators, public institutions, and low-resource environments.

***

#### 2. Mandate

2.1 **Mandate scope.** The Guild’s mandate is limited to research, measurement, tooling, and governance-grade artifacts, including:\
2.1.1 observatory-grade measurement doctrine and safe collection methods;\
2.1.2 reference implementations and reproducible test harnesses;\
2.1.3 datasets, benchmarks, and longitudinal measurement programs;\
2.1.4 enterprise-grade Assurance & Evidence Packs and decision-support templates;\
2.1.5 open education and capacity-building materials;\
2.1.6 standards mappings and interoperability guidance aligned to W3C/IETF/ICANN and adjacent ecosystems.

2.2 **Mandate exclusions.** The Guild does not perform regulated execution, operational command, enforcement, or certification.

2.3 **Minimum integrity duty.** Every mandated output must be correctionable by design, labeled with reliance bounds, and distributable under handling discipline.

***

#### 3. What the Guild Produces and Does Not Produce

3.1 **Guild work products (permitted).** The Guild may produce, subject to validity-by-record:\
3.1.1 **methods** (collection, normalization, verification, analysis, dissemination) with explicit uncertainty disclosure;\
3.1.2 **measurement reports** (trend, comparative, and longitudinal) with methodology publication and anti-gaming controls;\
3.1.3 **datasets** with lineage, refresh policy, bias/drift notes, and access tiering;\
3.1.4 **benchmarks** with sampling disclosure, appeals path, drift monitoring, and correction discipline;\
3.1.5 **reference code** and **test harnesses** with signed releases and supply chain posture;\
3.1.6 **Assurance & Evidence Packs** including reproducibility and evidence sufficiency gradings;\
3.1.7 **interoperability mappings** and schema/ontology artifacts;\
3.1.8 **education** (labs, curricula, reproducible tutorials) consistent with do-no-harm publication.

3.2 **Explicit non-products (prohibited).** The Guild shall not produce:\
3.2.1 operational SOC/EOC services, managed detection and response, or incident command;\
3.2.2 enforcement actions, takedowns, censorship operations, or coercive moderation blueprints;\
3.2.3 compliance determinations, legal opinions, or “certifications” of organizations, products, or systems;\
3.2.4 procurement steering, “approved vendor” lists, or bid-shaping requirements;\
3.2.5 exploit playbooks, weaponization guides, evasion recipes, or step-by-step offensive instructions;\
3.2.6 market manipulation cues or trading/placement/underwriting activity.

3.3 **No implied assurance.** “Guild-Reviewed,” “Lab-Validated,” or “Enterprise-Deployable” markings do not constitute certification, warranty, or compliance determination.

***

#### 4. Scope Boundary

4.1 **Hard perimeter.** The Guild’s activities must remain strictly within an R\&D and measurement perimeter, including:\
4.1.1 non-intrusive observatory methods and consented telemetry where applicable;\
4.1.2 governance-grade evidence packaging and decision record templates;\
4.1.3 reproducible evaluation and benchmarking;\
4.1.4 standards-aligned interoperability artifacts.

4.2 **Operational exclusion.** The Guild shall not:\
4.2.1 dispatch responders, manage live incidents, or direct operational containment;\
4.2.2 act as a substitute for internal security teams, regulators, or CERT/CSIRT operations;\
4.2.3 issue binding instructions to operators or users.

4.3 **Regulated advice exclusion.** The Guild shall not provide:\
4.3.1 legal advice;\
4.3.2 regulatory compliance determinations;\
4.3.3 audit opinions;\
4.3.4 investment, underwriting, or placement advice.

4.4 **Non-manipulation and non-weaponization.** The Guild shall not publish content that materially enables exploitation, targeted harassment, mass coercion, or market manipulation.

4.5 **Intelligence boundary.** Intelligence work is limited to lawful, non-intrusive collection and analysis consistent with the observatory posture; intelligence does not become enforcement, surveillance, or censorship.

***

#### 5. Intended Users and Adoption Contexts

5.1 **Primary adoption contexts.** The Guild’s outputs are intended for:\
5.1.1 enterprises managing web risk (security, privacy, integrity, accessibility, reliability);\
5.1.2 infrastructure providers (registries/registrars, DNS operators, CDNs, hosting/cloud platforms);\
5.1.3 public institutions and critical infrastructure operators reliant on web availability and trust;\
5.1.4 standards bodies and technical governance communities;\
5.1.5 researchers, civil society, and educators requiring reproducible methods and datasets.

5.2 **Adoption posture.** Adopters may use Guild outputs as decision-support inputs within their own governance and legal authority, subject to reliance bounds, handling discipline, and independent verification requirements.

***

#### 6. Reliance Bounds and Safe-Use Warnings (R0–R4)

6.1 **Reliance marking requirement.** Every artifact must declare a reliance bound category and explicit prohibited uses.

6.2 **R0 — Informational only.**\
6.2.1 Use: background, education, and exploratory analysis.\
6.2.2 Prohibited: operational decisions, enforcement actions, compliance conclusions.

6.3 **R1 — Research decision-support.**\
6.3.1 Use: internal hypothesis formation, measurement design, and control selection.\
6.3.2 Prohibited: automated actioning; public allegations; procurement decisions without independent validation.

6.4 **R2 — Operational planning support (non-automated).**\
6.4.1 Use: prioritization, risk review, control roadmap, and tabletop preparedness.\
6.4.2 Conditions: multi-source corroboration; local context review; documented human approval.\
6.4.3 Prohibited: live incident command; enforcement; unilateral adverse action against external parties.

6.5 **R3 — Enterprise decision support under governance.**\
6.5.1 Use: governance-approved risk decisions where the adopter holds authority, maintains audit logs, and can contest/correct.\
6.5.2 Conditions: decision record; human-in-the-loop; uncertainty acceptance; appeals/correction path.\
6.5.3 Prohibited: sole-source automated blocking/takedown; any use that constitutes regulated advice.

6.6 **R4 — High-impact consequential use (restricted).**\
6.6.1 Use: only where expressly authorized by adopter governance, with independent verification, heightened audit controls, and legal review as applicable.\
6.6.2 Conditions: dual-control approvals; enhanced monitoring; post-action review; explicit error budgets; documented fallback procedures.\
6.6.3 Prohibited: coercive or discriminatory actions; mass surveillance; censorship blueprinting; any deployment that removes contestability.

6.7 **No single-source decisions.** No Guild artifact may be represented or used as the sole basis for high-impact decisions affecting rights, access, eligibility, or public allegations.

***

#### 7. Enterprise Safety Posture

7.1 **Uncertainty is mandatory.** All claims must carry limitations, confidence posture, and known failure modes.

7.2 **Separation of observation and inference.** Artifacts must distinguish measured facts from analytic judgment and from recommendations (where permitted as research guidance).

7.3 **Human accountability.** For any consequential use, the adopter must maintain:\
7.3.1 a decision record linking the artifact to the action;\
7.3.2 a review pathway for disputes and corrections;\
7.3.3 auditability and distribution logs for the artifact versions relied upon.

7.4 **Safe-mode principle.** Where artifact uncertainty is material or drift is suspected, the safe-mode default is to **defer action**, **seek corroboration**, or **reduce impact**.

***

#### 8. Interoperability Commitment

8.1 **Standards alignment.** The Guild aligns outputs to W3C, IETF, and ICANN artifacts and norms where relevant, and publishes mapping notes that enable:\
8.1.1 schema interoperability (e.g., Schema.org, OpenAPI, JSON-LD patterns);\
8.1.2 measurement comparability and reproducibility;\
8.1.3 portability across governance regimes without claiming equivalence.

8.2 **Non-equivalence warnings.** Standards mappings are informational and may not be represented as:\
8.2.1 proof of legal compliance;\
8.2.2 certification or conformance claims;\
8.2.3 endorsement by standards bodies.

8.3 **Change disclosure.** Interoperability artifacts must declare versioning, deprecation, backward compatibility expectations, and migration guidance.

***

#### 9. Cross-Domain Coupling Thesis

9.1 **Web as upstream risk amplifier.** The Guild treats the web as a coupled dependency layer for water, energy, food, health, finance, and critical infrastructure, where outages, manipulation, identity failures, supply-chain compromise, and centralization can cascade into physical and societal harms.

9.2 **Coupling-aware measurement.** Measurement programs and benchmarks must include coupling indicators where feasible (dependency concentration, blast radius, cross-domain reliance signals), without crossing into surveillance or enforcement.

9.3 **Safety-first disclosure across domains.** Where cross-domain coupling increases harm potential, the Guild shall apply heightened dual-use gating, distribution controls, and abstraction requirements.


---

# 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-web/ii.-mission.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.