Article 11. Inter-Nexus Relations — Earth Cooperation Treaty (ECT)

Last modified: September 5, 2025
For versions:
  • Wiki
  • Bylaws
  • Article 11. Inter-Nexus Relations — Earth Cooperation Treaty (ECT)
Estimated reading time: 6 min

(Swiss Verein; Zug register; principal base Geneva. This Article governs GRF’s cooperation with Nexus Entities under the private, multilateral Earth Cooperation Treaty (ECT), as referenced in Arts. 3 (Independence), 5 (Definitions & Precedence), 6 (Governing Bodies), 9 (Authorities), 10 (Programs & Tracks), 12 (CB Clearance & Materiality), 14–15 (Data/Privacy/Security), 16 (Ethics & Safeguarding), 18 (Disputes). English (EN) controls; FR/DE companions provided where operationally required. “Nexus Entities” include GCRI, GRA, NSF, NE Labs, and GRF as defined in Art. 5.1.)


11.1 Nature & Scope of ECT (Private Multilateral Agreement)

11.1.1 Legal Character

(a) The ECT is a private multilateral cooperation agreement governed by Swiss substantive law (unless a Schedule specifies a different governing law for a narrow technical matter and is CB-Cleared).
(b) It is not a public international treaty; it creates contractual rights/obligations among signatory Nexus Entities only.

11.1.2 Purpose & Field of Application

(a) Enable systemic collaboration across DRR, DRF, DRI programs and Tracks (Art. 10) with shared standards, schedules, and evidence.
(b) Ensure independence by design (Art. 3), auditability, and trust-minimized execution via CB channeling (Art. 12).
(c) Cover joint work on policy/science, capital & risk transfer, programs & alliances, and R&D/innovation (see §11.4).

11.1.3 Instruments under the ECT

(a) Framework (this Article + Annex U ECT Operating Protocol).
(b) ECT Schedules (U-1, U-2, …): project-specific or function-specific addenda that define scope, deliverables, budgets, IP/data, security, KPIs, and timelines.
(c) Council Opinions and CB Clearances (Art. 12) appended to each Schedule; each issuance bears a Clearance ID.

11.1.4 Accession, Term & Review

(a) Accession: Additional Nexus Entities may accede by Joint Committee approval (§11.3) and Board ratification (Art. 9.1.1).
(b) Term: The framework is evergreen; individual Schedules state their own term.
(c) Review: Annual Joint Committee review; material updates are gazetted by each party’s CB.
(d) Withdrawal/Suspension: A party may withdraw from a Schedule on 30 days’ notice (or longer as stated) without affecting other Schedules; emergency suspension permitted for legal/sanctions/security reasons with immediate notice and CB record.


11.2 Parties & Roles: GCRI, GRA, NSF, NE Labs, GRF

11.2.1 Parties

The ECT binds, at minimum, the following Nexus Entities (as defined in Art. 5.1): GCRI, GRA, NSF, NE Labs, and GRF.

11.2.2 Role Baselines (non-exclusive)

(a) GRF: neutral convenor and governance hub; owns Programs/Tracks integration; maintains independence and public transparency; coordinates CB channeling.
(b) GCRI: policy/science anchor; develops standards, taxonomies, and evidence syntheses feeding DRR/DRF/DRI KPIs.
(c) NSF: capital & risk transfer platform; designs/operates pre-arranged finance and verification/payout rails aligned to Art. 10 Capital Track.
(d) GRA: programs & alliances orchestrator; aggregates execution coalitions, multi-stakeholder partnerships, and host country engagements.
(e) NE Labs: R&D and innovation engine; prototypes AI/ML, simulation, and data services across the Nexus stack.


11.3 Governance Under ECT (Joint Committee; Voting; Secretariat Function)

11.3.1 Joint ECT Committee (JEC)

(a) Constitution: One voting representative per Nexus Entity; alternates permitted by notice.
(b) Chairing: Rotating every 12 months; the host CB provides the Secretariat (minutes, registers, clearances logistics).
(c) Meetings: Quarterly (virtual/hybrid) and extraordinary within 10 Business Days upon RAP activation or a CB incident (§11.5.4).
(d) Quorum:75% of voting members.

11.3.2 Decision Rules

(a) Simple majority for operational matters (workplans, calendars, L&A tests).
(b) Two-thirds (≥2/3) for budgets >CHF thresholds, data-sharing regimes, model governance baselines, or cross-entity staffing.
(c) Three-quarters (≥3/4) for framework amendments, accessions, or exclusions.
(d) Dissent & Walls: A dissenting party may opt out of a Schedule without blocking others; walls and carve-outs are recorded by the CB.

11.3.3 Secretariat Function

(a) The host CB (rotating or designated) maintains the ECT Register, issues Council Opinions, assigns Clearance IDs, and publishes the Gazette notices (EN controls; FR/DE companions).
(b) Each party’s home CB mirrors the record into its own Council Register.


11.4 Functional Interfaces

11.4.1 Policy/Science Interface (GRF ↔ GCRI)

(a) Scope: Standards, taxonomies, KPI definitions, and evidence synthesis mapping to Sendai A–G (Art. 10.1.2).
(b) How/When/Where: Annual Geneva Dialogue to adopt baselines; quarterly L&A tests; change control via JEC.
(c) Deliverables: Methods notes, benchmark datasets, and QA/QC Cards; provenance hashes lodged in both Council Registers.
(d) Clearance: Pre-Clearance for changes that trigger Materiality (Art. 12); DPIA/PIA when personal data involved.

11.4.2 Capital & Risk Transfer Interface (GRF ↔ NSF)

(a) Scope: Pre-arranged finance structures, triggers, verification, and payout rails under NXS-NSF.
(b) Guardrails: No success-fees, donor-conditioned influence, or investment advice; KYC/AML, sanctions, and independence walls apply.
(c) Deliverables: Term sheets, trigger protocols, payout rehearsal logs; recipient safeguards and transparency sheets.
(d) Clearance: CB Pre-Clearance required for DRF rails and custodial flows; Treasury/Investment policy alignment (Annex H).

11.4.3 Programs & Alliances Interface (GRF ↔ GRA)

(a) Scope: Multi-stakeholder coalitions, host country compacts, and cross-sector implementation partnerships.
(b) How/When/Where: Regional Summits (semi-annual) to ratify sprint portfolios; Sprint Charters filed per Art. 10.3.2.
(c) Deliverables: Partner MoUs, SOPs, procurement pipelines; Independence Impact Assessments (IIA).
(d) Clearance: CB screens related-party risks; records donor/procurement walls.

11.4.4 R&D/Innovation Interface (GRF ↔ NE Labs)

(a) Scope: Prototyping AI/ML, simulation, data services across NXS-EOP/EWS/AAP/DSS; TRL/PRL/CRL/DRL progression (Annex V).
(b) How/When/Where: Monthly innovation sprints; field pilots in ≥ 2 regions; code & models under open/reciprocal licenses unless CB-Cleared otherwise.
(c) Deliverables: Prototype releases, interoperability specs, security/performance test packs; Model Cards.
(d) Clearance: DPIA/PIA for personal data; export-control/sensitive-country checks; model governance baselines enforced.


11.5 Channeling via CB (Registration; Clearance; Provenance)

11.5.1 ECT Register & Schedule IDs

(a) Each Schedule receives an ECT-Schedule ID and Clearance ID; the host CB maintains the authoritative ECT Register; parties mirror to their Council Registers.

11.5.2 Clearance Modalities

(a) Pre-Clearance (PC): mandatory for Material Actions (Art. 12) including cross-border data flows, DRF rails, custodial arrangements, or IP encumbrances.
(b) Standing Clearance (SC): repetitive, templated exchanges; re-validated at least annually.
(c) Fast-Track (FT): urgent, low-to-moderate risk; limited scope and duration.
(d) RAP Clearance (RC): accelerated during RAP; post-ratification within 30 days.

11.5.3 Provenance & Evidence

(a) All ECT outputs (datasets, models, code, minutes, term sheets) carry provenance hashes and versioning; entries are prima facie evidence of authority.
(b) Four-eyes & Identity: Signatures follow Annex G; ZertES-compatible e-signatures where electronic.

11.5.4 Incident, Breach & Suspension

(a) Security/Data Incidents: notify host CB within 24 hours; joint containment within 72 hours; JEC brief within 5 Business Days; Gazette summary (lawful redactions).
(b) Suspension: host CB may temporarily suspend interfaces that present unresolved integrity or legal risk; Board notified; path to cure recorded.


11.6 IP, Data, and Confidentiality Baselines under ECT

11.6.1 Intellectual Property

(a) Foreground IP (created under a Schedule): owned by the party designated in the Schedule; default joint license among ECT parties for public-interest use; open or reciprocal licenses preferred (e.g., families compatible with Annex T).
(b) Background IP: remains with the contributor; licensed as necessary for Schedule performance on a non-exclusive, royalty-free or FRAND basis.
(c) No Core Marks Assignment: GRF core identity and marks are never co-branded or assigned (Art. 3). Any limited mark use requires Board approval and CB Clearance.

11.6.2 Data & Models

(a) Lawful Basis & Minimization: FADP (and GDPR/UK GDPR where applicable); purpose limitation; minimization; retention by design.
(b) Cross-Border Transfers: use Swiss/EU standard contractual clauses or adequacy routes; CB-Cleared DPIA/PIA for high-risk processing.
(c) Model Governance: Model Cards, calibration, fairness and uncertainty disclosure; red-team cadence; no donor-conditioned performance targets.
(d) Access Controls: least privilege; audit trails; revocation within 24 hours upon role change or incident.

11.6.3 Confidentiality & Publication

(a) Classifications: Public / Internal / Restricted / Secret; handling rules per Art. 15.
(b) Publication: default open for methods and non-identifying aggregates; embargoes allowed with CB-Cleared necessity/expiry.
(c) Whistleblowing: protected channels under Art. 16 apply across parties.


11.7 Non-Exclusivity & Independence Safeguards

11.7.1 Non-Exclusivity

(a) ECT cooperation is non-exclusive; parties may collaborate externally provided Independence (Art. 3) and confidentiality are preserved.
(b) MFN-like clause: materially similar open standards, datasets, or governance baselines developed under the ECT should be made available to all parties on no worse terms, absent justified and CB-Cleared exceptions.

11.7.2 Independence & Conflicts

(a) Donor/Procurement Walls and IIA apply to all ECT activities (Annex J/N); Schedule-specific walls are recorded in the ECT Register.
(b) Dual-Office Conflicts: Members of a governing board of one Nexus Entity seeking executive office in another must comply with Art. 8.5.9 (notification, walls, resignation rules).
(c) No Pay-to-Influence: Compensation or variable pay may not be tied to vendor selection, donor outcomes, or policy positions (Arts. 8.2A, 8.3A).


11.8 Dispute Resolution within ECT

11.8.1 Tiered Process

(a) Good-faith negotiation between designated ECT Leads (10 Business Days).
(b) Mediation under the Swiss Chambers’ Mediation Rules (seat Geneva; EN; 30 days, extendable by agreement).
(c) Arbitration under the Swiss Rules (SCAI): seat Geneva, EN language, Swiss substantive law; expedited procedure for disputes ≤ CHF 2,000,000. Interim and emergency measures available.

11.8.2 Technical Determination

For purely technical disputes (e.g., KPI calculation, cryptographic proofs, TRL/PRL/CRL/DRL gates), the parties may refer the question to an independent expert appointed by the JEC; the expert’s determination is final and binding unless manifest error.

11.8.3 Confidentiality & Costs

(a) Proceedings are confidential except as required by law or Gazette summaries of outcomes (lawful redactions).
(b) Costs follow the result unless the tribunal decides otherwise; tribunals may award specific performance and injunctive relief to protect independence, data, or IP.


11.9 Implementation “How/When/Where” (Operational Hooks)

11.9.1 How (Pipeline)

T-60 Intent Note → T-45 IIA/DPIA & CB Pre-Clearance → T-30 Schedule signature → T-15 access provisioning → 0..+90 delivery → +10 Results Note & Register/Gazette entries (see Art. 10.5; Annex U templates).

11.9.2 When (Cadence)

(a) JEC quarterly; extraordinary within 10 Business Days upon RAP or material incident.
(b) Geneva Dialogue annually to ratify cross-nexus workplans and baselines.
(c) Regional joint sprints aligned to RSB calendars (Art. 10.3).

11.9.3 Where (Venues & Systems)

(a) Geneva is the principal convening node; rotating regional hubs as CB-Cleared.
(b) NXSQue is the default orchestration layer; identity/signature per Annex L; evidence in each party’s Council Register plus the ECT Register.


Design Result: The ECT makes cross-entity work lawful, independent, interoperable, and provable—with a Joint Committee to steer, CB channeling to control risk and provenance, open-by-default knowledge terms, hard non-exclusivity and independence safeguards, and Swiss-grade remedies to resolve disputes without slowing delivery.

Was this article helpful?
Dislike 0 0 of 0 found this article helpful.
Views: 36

Continue reading

Previous: Article 10. Programs, Tracks, Regionalization & Collaboration
Next: Article 12. Meetings, Quorum & Voting

Leave a Reply

Have questions?