# XXIII. Interoperability

### Part 23 — Interoperability Across Guilds and Nexus Ecosystem Integration

*(Binding objective: enable portability **without** creating authority, **without** relaxing handling/safety/neutrality, and **without** allowing laundering of restrictions or history. All interop actions are **record-valid** only.)*

#### 23.1 Purpose, Scope, and Interoperability Doctrine

23.1.1 **Interoperability as public-good infrastructure.** Interop exists to reduce duplication, improve reuse, and increase contestability—never to create authority or implied endorsement.\
23.1.2 **Scope.** Membership-layer portability across Guilds, Platforms (Registry/Journals/Campaigns/Future Innovation Labs), Councils, and adoption organs (Chapters/State Councils/NWGs/Hosts/CERTs).\
23.1.3 **Non-executing perimeter reaffirmed.** Interop never authorizes execution, procurement, enforcement, dispatch, underwriting, custody, or settlement.\
23.1.4 **No safety regression (binding).** Handling, correctionability, neutrality, and due-process protections may not be relaxed by any interop pathway.\
23.1.5 **Validity-by-record.** Interop changes take effect only via record-valid acts with effective dates and expiry.\
23.1.6 **Voluntary baseline.** No compelled cross-Guild affiliation, roaming, data export, or identity disclosure beyond handling/lawful minima.

***

#### 23.2 Interoperability Topology and Interfaces

23.2.1 **Guild ↔ Guild roaming.** Mobility model for observe/contribute/review with PoC/handling gates and anti-gaming controls.\
23.2.2 **Guild ↔ Council interface.** Primary Council-of-record per Guild; cross-council review triggers; contestation lanes preserved.\
23.2.3 **Guild ↔ cross-cutting Platforms.** Standard interfaces to Registry, Journals, Campaigns, and Future Innovation Labs with common record schemas.\
23.2.4 **Guild ↔ CCells/CERTs.** Formation/dissolution interoperability, portability of work products, and inheritance of handling and correction clocks.\
23.2.5 **Guild ↔ adoption organs.** Activation-gated interoperability with Chapters/State Councils/NWGs/Host Institutions; local constraints override.\
23.2.6 **Nexus public-good stack boundary.** GCRI/GRF/NSF governance roles integrate at membership layer only; no execution-stack authority transfer.\
23.2.7 **External ecosystem interfaces.** Bounded integrations with universities, standards bodies, and open-source communities under safeguards.

***

#### 23.3 Primary Affiliation and Roaming Model

23.3.1 **Primary affiliation invariance.** Each member has one primary Guild anchor for routing, rotation pools, and capture resistance.\
23.3.2 **Roaming entitlements.** Observe, contribute, replicate, review—subject to PoC level, handling eligibility, and standing.\
23.3.3 **Switching primary affiliation.** Rate-limited; effective-date based; anti-gaming constraints; reason-coded when tied to disputes.\
23.3.4 **Cross-tagging rules.** Lead-of-record required; co-tags permitted; double-counting prohibited; dependency graphs maintained.\
23.3.5 **Multi-domain work routing.** Lead Guild selection rules; mandatory co-review triggers for safety/rights/market-sensitive domains.\
23.3.6 **Roaming survival obligations.** Handling survival, confidentiality, correction duties, and misrepresentation constraints follow the member.

***

#### 23.4 Portability of Standing, Credits, and Competence

23.4.1 **Portability principles.** Earned and replayable; utilities are non-financial; portability never implies endorsement or authority.\
23.4.2 **CRS portability.** What transfers (classes, recency-weighted totals) vs what does not (domain-specific multipliers; restricted contributions); decay rules apply.\
23.4.3 **PoC portability.** Level portability with renewal clocks; domain add-ons required where hazards differ; lapse propagation rules.\
23.4.4 **ILA portability.** Learning history portability with privacy controls; revocation trails preserved; de-identification options.\
23.4.5 **Credits portability.** e/p/v/NUCs portable only within equivalent-or-stronger handling lanes; no cash-out; no conversion.\
23.4.6 **Cross-Guild reviewer pools.** Eligibility, rotation, and calibration across Guilds; anti-concentration rules preserved.\
23.4.7 **Negative history portability.** Clawbacks, suspensions, and controlled-lane bans propagate; no laundering across Guilds or Platforms.

***

#### 23.5 Interoperable Roles and Role-Marker Semantics

23.5.1 **Role-marker taxonomy.** Global role markers; Guild-scoped; cell-scoped; event-scoped; each with explicit scope + expiry.\
23.5.2 **Minimum interoperable role fields.** Authority basis, duties, scope, lane permissions, PoC/handling prerequisites, expiry, revocation path.\
23.5.3 **Role conflict rules.** Prohibit simultaneous conflicting roles (e.g., safety gate + release approval on same artifact; integrity roles + sponsor-adjacent program selection).\
23.5.4 **Cross-council recognition/de-recognition.** Recognition is record-valid; de-recognition propagates to dependent privileges.\
23.5.5 **Emergency role markers.** Incident-mode markers; mandatory expiry; heightened audit and post-action review.\
23.5.6 **Revocation propagation.** Role revocations restrict roaming eligibility and controlled-lane access across the ecosystem.

***

#### 23.6 Handling-Class Interoperability

23.6.1 **Handling equivalence mapping.** Canonical mapping table across Guilds/Platforms; no downgrade permitted on export.\
23.6.2 **Controlled/restricted entry requirements.** PoC thresholds, handling training, distribution logging, and device/security posture gates.\
23.6.3 **Distribution-log portability.** Recipient reconciliation, recall propagation, expiry enforcement, and revocation notices across endpoints.\
23.6.4 **Watermarking interoperability.** Watermark lineage, per-recipient watermarking, leak investigations, and evidence standards.\
23.6.5 **Cross-border constraints.** Privacy law, export controls, sanctions, and sensitive jurisdiction constraints override portability.\
23.6.6 **Downscoping/declassification rules.** Only via public-safe abstraction; never by copying controlled detail into public lanes.

***

#### 23.7 Artifact Interoperability and Evidence Packaging Standards

23.7.1 **Interoperable artifact classes.** Methods, benchmarks, datasets, ontologies, Proof Packs/AEP patterns, review reports, drills/after-actions.\
23.7.2 **Minimum metadata schema.** Provenance, scope, limitations, reliance bounds, handling election, expiry, correction path.\
23.7.3 **Version discipline.** Supersession-only updates; diffs required; effective dates; immutable release pointers where designated.\
23.7.4 **Cross-Guild citation rules.** Dependency graphs to avoid circular reliance; explicit upstream/downstream relationships.\
23.7.5 **Replayability/reproducibility minima.** Environment specs, hashes, run instructions, and validation logs by artifact class.\
23.7.6 **Safety annotations.** Dual-use flags, CI sensitivity indicators, market-sensitivity notes; mandatory where applicable.

***

#### 23.8 Interoperability for Publication

23.8.1 **Submission routing.** Lead-of-record Guild assignment; co-review triggers; editorial independence rules.\
23.8.2 **COI controls in cross-Guild editing.** Recusal portability; reviewer rotation; sponsor adjacency constraints.\
23.8.3 **Handling-aware formats.** Public-safe summaries by default; controlled appendices access-logged and expiry-bound.\
23.8.4 **Dissent portability.** Minority reports preserved, citable, and linked to supersession chains.\
23.8.5 **Retraction/correction propagation.** Downstream notifications, distribution log reconciliation, and registry state updates.\
23.8.6 **Indexing and discoverability.** Non-endorsement statements; scope-bounded labeling; no “compliance” implications.

***

#### 23.9 Interoperability for Collective Action

23.9.1 **Campaign formation across Guilds.** Time-boxed; non-partisan; non-executing; scope/handling/expiry mandatory.\
23.9.2 **Eligibility gates.** PoC minima, COI clearance, sanctions/export control compliance, handling training where required.\
23.9.3 **Output routing.** Campaign outputs route to Guild backlogs and/or Journals with lead-of-record mapping.\
23.9.4 **Anti-capture mechanics.** Rotation, sponsor caps, neutral topic selection constraints, and reason-coded prioritization.\
23.9.5 **Comms integrity across domains.** Attribution gates, misquote response, narrative safety rules, and controlled disclosures.\
23.9.6 **Closure + after-action.** Artifact migration, dissolution-by-default, correction windows, and archive discipline.

***

#### 23.10 Future Innovation Labs as Cross-Guild Operating Platforms

23.10.1 **Purpose and perimeter.** Method/replication/test environments only; no operational command, procurement, or execution.\
23.10.2 **Lab types.** Replication labs; benchmark labs; safety labs; interoperability testbeds; controlled-domain sandboxes.\
23.10.3 **Entry/exit controls.** PoC/handling gates, audit logging, time-boxed access, and offboarding attestations.\
23.10.4 **Cross-Guild lab governance.** Primary Council lead + Stewardship safety gate; separation-of-duties enforced.\
23.10.5 **IP/licensing posture.** Inbound rights attestations; outbound default open where public-safe; clean-room rules for restricted inputs.\
23.10.6 **Graduation path.** Lab artifacts progress to review → safety screening → publication-ready → badge-eligible.

***

#### 23.11 Council Integration and Quintuple-Helix Balance

23.11.1 **Primary Council invariance.** One Council per Guild remains constant; interoperability does not create extra councils.\
23.11.2 **Cross-council review triggers.** Safety, rights impacts, market sensitivity, and systemic-risk coupling triggers.\
23.11.3 **Helix balance targets.** Seat completion rules and legitimacy checks for cross-domain workstreams.\
23.11.4 **Recusal portability.** COI disclosures follow the member across councils and work units.\
23.11.5 **Neutrality hygiene across domains.** Procurement/competition constraints enforced in cross-Guild rooms and outputs.\
23.11.6 **Public-sector ethics constraints.** Gift rules, travel/honoraria constraints, and participation boundaries respected.

***

#### 23.12 Sovereign-Compatible Adoption Integration

23.12.1 **Activation gate reaffirmed.** No in-jurisdiction presence without State Council + mandate evidence; interop cannot bypass this.\
23.12.2 **Host Institution interoperability.** Sovereign data zones, compute-to-data, audit logs, and handling equivalence.\
23.12.3 **NWG portability.** Time-boxed charters; dissolve-by-default; outputs route back to Guilds/Journals.\
23.12.4 **CERT interoperability.** Multi-CCell compositions; handling inheritance binding; distribution logging mandatory.\
23.12.5 **Local law overrides.** Abstention/pause rules; no cross-border leakage of restricted content.\
23.12.6 **De-recognition/reversion.** Automatic reversion to global-only participation on mandate lapse or non-compliance.

***

#### 23.13 External Standards and Ecosystem Linkages

23.13.1 **Standards interop (bounded).** ISO/NIST/IEEE/W3C/IETF and sector standards mapping as informational only; no endorsement implied.\
23.13.2 **Open-source interop.** SBOM/SLSA posture for tooling; signed releases where applicable; vulnerability disclosure routing.\
23.13.3 **Academic publishing interop.** Preprint/journal pathways that preserve handling and correctionability; no “peer-reviewed equals certified” drift.\
23.13.4 **NGO/multilateral patterns.** Collaboration templates with non-endorsement and non-authority clauses.\
23.13.5 **Vendor neutrality in collaborations.** No exclusive pipelines; no procurement steering; anti-capture controls.\
23.13.6 **Export/sanctions safeguards.** Access gating, geo-restrictions where required, and controlled dissemination.

***

#### 23.14 Interoperability Risk Management and Controls

23.14.1 **Risk catalogue.** Capture, laundering, safety regression, IP contamination, privacy leakage, jurisdiction conflicts, misrepresentation.\
23.14.2 **Control set.** Rotation; audits; clawbacks; distribution logs; handling gates; recert clocks; two-person unmasking controls.\
23.14.3 **Monitoring + metrics.** iVRS interop-health indicators (portability volumes, correction propagation latency, leak signals, concentration).\
23.14.4 **Incident response.** Stop-the-line, recall propagation, containment, and after-action review for interop failures.\
23.14.5 **Independent review triggers.** Systemic anomalies, repeated regressions, or concentration/capture indicators.\
23.14.6 **Continuous improvement.** After-action → schema updates by record; notice and contestation windows.

***

#### 23.15 Records, Auditability, and Transparency Minima

23.15.1 **Interop acts are governance acts.** Portability events are record-valid governance actions with auditable fields.\
23.15.2 **Minimum record fields.** Who/what/when/why, scope, handling, expiry, dependencies, propagation targets, effective dates.\
23.15.3 **Public-safe summaries.** Required for material portability changes; include limitations and correction path.\
23.15.4 **Controlled detail minimization.** Access-logged, need-to-know, expiry-bound; watermarking where applicable.\
23.15.5 **Retention/deletion constraints.** Minimize identity; preserve integrity and correction chains; de-identify where feasible.\
23.15.6 **Schema change logs.** Supersession and migration logs for interop schemas and mappings, with rollback posture.


---

# 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/membership/xxiii.-interoperability.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.