{
  "boundary_note": "Synthetic portable export bundle for public renderer fixtures. It is deterministic fixture metadata only; it does not perform live profile redaction, private corpus access, or receipt verification.",
  "bundle_id": "GARPEDIA-BUNDLE-CP-SIG-44",
  "citation_summary": {
    "anchor_resolution_label": "Anchors not applicable",
    "anchor_resolution_status": "not_applicable",
    "citation_span_total": 0,
    "source_publication_counts": {
      "public": 0,
      "redacted_for_render": 0,
      "restricted": 0
    },
    "source_total": 0,
    "verification_counts": {
      "normalized_verified": 0,
      "not_applicable": 0,
      "unverified": 0,
      "verbatim_verified": 0
    }
  },
  "export_metadata": {
    "bundle_format": "garpedia.portable_export_bundle.v1.fixture",
    "exported_at": "2026-03-17T00:00:00Z",
    "page_model_json": "/garpedia/page-models/CP-SIG-44.json",
    "record_export_ids": [],
    "source": "synthetic_fixture"
  },
  "generated_by": "garpedia-portable-export-bundle-fixture",
  "lint_references": {
    "exempted_count": 0,
    "finding_codes": [],
    "freshness_posture": "not_provided",
    "highest_severity": null,
    "represented": false,
    "review_posture": "not_provided",
    "severity_counts": {
      "error": 0,
      "info": 0,
      "warning": 0
    },
    "total": 0
  },
  "page_model_json": "/garpedia/page-models/CP-SIG-44.json",
  "portable_summary_markdown": "# Nvidia Nemotron Coalition and Mistral Leanstral: Multi-Party Model Training Without Record Custody Governance\n\nRecord: CP-SIG-44\nProfile: Counterpose Publication\nStatus: active\nLifecycle: published\nAnchor posture: Anchors not applicable\n\n## Sections\n\n### Signal body\n\n# Nvidia Nemotron Coalition and Mistral Leanstral: Multi-Party Model Training Without Record Custody Governance Counterpose | CP-44 | March 17, 2026 A publication of Vega Commons Project, Inc. --- On March 16, 2026, Nvidia announced the Nemotron Coalition at GTC, a global collaboration between open model builders and AI developers. Inaugural members include Black Forest Labs, Cursor, LangChain, Mistral AI, Perplexity, Reflection AI, Sarvam, and Thinking Machines Lab. The first project will be a base model co-developed by Mistral AI and Nvidia, trained on Nvidia DGX Cloud, and released as open source. Coalition members will contribute data, evaluations, and domain expertise to support post-training and continued development. On the same date, Mistral AI published its Leanstral announcement, introducing a 120B-parameter open-source code agent for Lean 4 formal verification. The model is available through a free API endpoint, through Mistral Vibe with integrated MCP support, and as downloadable Apache 2.0 licensed weights. Mistral stated it is keeping the API endpoint \"highly accessible for a limited period to gather realistic feedback and observability data to fuel the next generation of verified code models.\" ## Multi-Party Data Flows Without Custody Architecture A custody surface is the set of records an AI system generates during operation that can be discovered, subpoenaed, or compelled through legal process. An interaction record is the log of what a user asked, what the system responded, and any reasoning the system performed. When Cursor contributes \"real-world performance requirements and evaluation datasets,\" those datasets originate from developer interactions with Cursor's AI coding assistant. When LangChain contributes agent execution data and observability information, that data originates from agent interactions running through LangChain's frameworks, which the announcement states process over 100 million monthly downloads. When Perplexity contributes its development expertise, the underlying data reflects user query behavior at scale. The coalition creates a multi-party data contribution architecture in which interaction records, or artifacts derived from interaction records, flow from individual member platforms to a shared training pipeline. The announcement does not specify what happens to contributed data after training: no retention schedules for contributed datasets, no access controls governing which members can see which contributed data, no deletion procedures after model training is complete, and no verification mechanisms for confirming that contributed data has been handled according to any governance framework. The term \"open\" in the coalition's framing refers to the model weights that result from training. Open weights are a contribution to the AI ecosystem. They do not address the custody posture of the data that produced those weights. An open-weight model trained on interaction-derived data does not make the training data open, recoverable, deletable, or governable. ## Leanstral's Data Collection Statement Mistral's statement that it is keeping the API endpoint \"highly accessible for a limited period to gather realistic feedback and observability data\" is an explicit acknowledgment that API interactions generate records that Mistral retains and uses for training purposes. The temporal framing (\"for a limited period\") indicates that free access is a data collection mechanism, not a permanent service offering. Even in a release explicitly branded as open-source, with Apache 2.0 licensed weights available for self-hosting, the API-hosted version operates as a record collection surface. Users who interact with the hosted API contribute interaction records to Mistral's training pipeline. Users who download the weights and run locally do not. The custody posture differs by deployment mode. Leanstral's MCP integration creates additional record surfaces. When an MCP-connected tool provides context to the model, the interaction record includes not only the user's prompt and the model's response but also data retrieved from connected services, tool calls made, and results returned. In the Leanstral case, the lean-lsp-mcp connection means the model's interactions include data from the user's development environment: source code, proof states, and compiler output. ## A New Custody Topology The coalition introduces a custody topology that has not previously appeared in this corpus. In a single-vendor arrangement, the custody surface is relatively straightforward: the vendor holds the training data, the model weights, and the interaction records. In the coalition model, the custody surface fragments across multiple contributing organizations, a shared training infrastructure, and whatever distribution or hosting arrangements follow the model release. If a legal process demands production of training data used to create a Nemotron 4 model, which entity responds, and from whose infrastructure is the production made? That question is not addressed by the coalition announcement, which is consistent with the pattern documented across the corpus: model development announcements describe capabilities, performance benchmarks, and licensing terms for output weights while saying nothing about the governance of input data or records generated during training. The question the Nemotron Coalition raises is whether multi-party model development, which pools data contributions from organizations that each hold their own interaction record custody surfaces, will develop a data contribution governance framework, or whether the pooling will proceed on the basis of capability and commercial interest without any participant addressing what happens to the contributed data after the model ships. --- ## Sources | Source | Date | Description | URL |\n|--------|------|-------------|-----|\n| Nvidia Newsroom | March 16, 2026 | Nemotron Coalition announcement | https://nvidianews.nvidia.com/ |\n| Mistral AI Blog | March 16, 2026 | Leanstral launch, data collection statement | https://mistral.ai/news/ |\n| AI Business (Scarlett Evans) | December 5, 2025 | Prior Nvidia-Mistral partnership context |  | --- ## Amendment Log *No amendments to date.* --- The observations presented reflect analytical assessment of publicly available information and do not constitute legal, insurance, or investment advice. Counterpose maintains no formal relationship with any vendor, regulator, or standards body referenced in this publication.",
  "profile": {
    "admission_boundary": "Captured Counterpose signal republished from the GARPedia admitted pool. The editorial body is projected verbatim and unverified: GARPedia records that the signal was admitted and renders it, but asserts no independent citation, source, or anchor verification over its claims.",
    "label": "Counterpose Publication",
    "profile_id": "counterpose_publication"
  },
  "receipt_references": [],
  "record_id": "CP-SIG-44",
  "record_route": "/records/CP-SIG-44",
  "schema_version": 1,
  "slug": "cp-sig-44",
  "source_references": [],
  "title": "Nvidia Nemotron Coalition and Mistral Leanstral: Multi-Party Model Training Without Record Custody Governance",
  "traversal_references": [
    {
      "detail": "cp-sig-44",
      "href": "/garpedia/page-models/CP-SIG-44.json",
      "kind": "page_model_json",
      "label": "Page model JSON export",
      "relation": "page_model_export",
      "target_id": "CP-SIG-44"
    }
  ]
}