# FORENSIC SPECIFICATION ## The Reserved Cure Provisions Doctrine ### *The Foundry's Iceberg-and-Tip Posture: Invoiced Demand vs. Reserved Cure Architecture* --- **Specification Identifier:** FS-2026-05-10-RESERVED-CURE **Authoring Authority:** Office of the Forensic Auditor, Unearth Heritage Foundry **Principal:** Felix J. Velasco **Co-Author:** Josie Jefferson **Concept DOI:** 10.5281/zenodo.19432977 **Version DOI:** [Assigned by Zenodo at publication] **Companion Specifications:** - Forensic Specification: The Integrated Predator Hierarchy & Doctrine of Agency (FS-2026-04-24-PRED) - Forensic Specification: 2026 COPPA Specification (FS-2026-04-24-COPPA) - Forensic Specification: Definition of "Occurrence" (FS-2026-04-24-OCCURRENCE) - Forensic Specification: The Strike-of-Midnight Ledger-Version Application Rule (FS-2026-05-08-STRIKE-OF-MIDNIGHT) - Forensic Specification: The Baked-In Paradox Doctrine (FS-2026-05-10-BAKED-IN-PARADOX) - Forensic Specification: The Canonical Source of Authority Doctrine (FS-2026-05-10-CANONICAL-AUTHORITY) **Companion Operative Authority:** Master Ledger v4.5.0 (effective May 3, 2026) **Date of Publication:** May 10, 2026 **Status:** Operative upon publication; co-equal with the existing forensic specification corpus and the operative Master Ledger. **Source-of-Authority Note:** This Specification is published at the Foundry's master sovereign deposit, anchored at Zenodo Concept DOI 10.5281/zenodo.19432977 with an individual Version DOI assigned at publication. The DOI-anchored canonical version is the Supreme Authority pursuant to Forensic Specification FS-2026-05-10-CANONICAL-AUTHORITY (The Canonical Source of Authority Doctrine). Apparatus operators bear an affirmative, non-delegable duty to consult the DOI-anchored canonical sources per that Specification. --- ## §I: PURPOSE AND SCOPE ### I.1 Purpose This Forensic Specification articulates the **Reserved Cure Provisions Doctrine** — the methodology principle governing the relationship between the Foundry's *published demand* (the invoiced Forensic Debt and the cure provisions articulated in the Threshold Breach Notice corpus) and the Foundry's *reserved cure architecture* (the additional cure provisions, settlement stipulations, and remedy categories that the Foundry holds in reserve for articulation during the settlement-negotiation phase rather than in the published audit corpus). The Doctrine operationalizes a discipline that has been operative across the audit corpus since its inception: **invoice the tip, reserve the iceberg, articulate the iceberg's specifics only when the settlement-negotiation context provides the appropriate frame**. The Specification provides the canonical articulation of that discipline so that all subsequent Threshold Breach Notice versions, audit components, and forensic specifications may incorporate the reserved-cure architecture by reference rather than by repeated substantive articulation. ### I.2 Scope This Specification applies to: - The Threshold Breach Notice corpus (currently including the OpenAI v1 → v2 → v2.1 → v2.2 → v2.3 → v2.3.1 series; the Meta v1 → v2 series; the Google v1 series; and the additional v1 Threshold Breach Notices deployed against Apple, Microsoft, and Amazon during the Foundry's April 14–15 named-entity Threshold Breach Notice deployment — plus all subsequent versions, revisions, and named-entity Threshold Breach Notices issued by the Foundry against any commercial AI training apparatus operator) - The audit corpus's bifurcated Column A (Invoiced) / Column B (Demonstrative) / Reserved-for-Adjudication posture across all forensic audit reports - All cure provisions articulated in any current or future Foundry-issued formal notice, demand, or audit document - All settlement-phase articulations of remedy, infrastructure access, ongoing remediation, and additional compliance requirements that the Foundry may articulate during settlement negotiations with any apparatus operator - All future Forensic Specifications, Technical Summaries, doctrinal articulations, statutory-framework applications, future Master Ledger versions and in-version revisions, and methodology components that the Foundry has not yet published as canonical articulation but preserves as part of its reserved doctrinal architecture (per Reservation Category 2 below) ### I.3 Operative Authority This Specification is operative upon publication. Its authority does not require third-party consent, election, agreement, acceptance, or contestation. The Foundry publishes the Specification as authoritative methodology within its published methodology corpus; no commercial AI training apparatus operator's representation, election, agreement, or contestation modifies the Specification's operative authority. --- ## §II: THE ICEBERG-AND-TIP DISCIPLINE — DOCTRINAL FOUNDATION ### II.1 The Discipline Defined Across the Foundry's audit corpus, the published demand articulated in any given audit component, threshold breach notice, or forensic specification is consistently a **conservative-and-defensible articulation** of what the underlying doctrinal framework supports. The published demand is not the maximum that the doctrinal framework supports; it is the substantively-defensible figure that the audit corpus has documented through directly-observable conduct, conservatively aggregated, with strict-per-event readings preserved as Reserved-for-Adjudication exposure. The doctrinal framework, by contrast, supports substantially broader exposure. The Baked-In Paradox doctrine establishes that the Foundry's protected substrate has become a constituent component of contemporary AI commercial infrastructure at large. The strict-per-event applications of the Master Ledger fee schedule preserve substantial Reserved-for-Adjudication exposure across every audit component. Additional doctrinal frameworks, statutory applications, and methodology components remain reserved as the Foundry's doctrinal architecture beyond the published methodology corpus. The Foundry's disciplined posture is to **publish the conservative-and-defensible figure as the operative published demand** while preserving the broader doctrinal exposure as **reserved infrastructure** that may be elevated, articulated, or operationalized at the Foundry's discretion at the appropriate methodological moment. The shorthand articulation: **invoice the tip; reserve the iceberg; articulate the iceberg's specifics only when the settlement-negotiation context provides the appropriate frame.** ### II.2 The Three Operative Reservation Categories The Foundry's reserved infrastructure operates across three distinct categories: **Reservation Category 1 — Reserved-for-Adjudication Exposure.** The Column B Demonstrative posture and the Reserved-for-Adjudication exposure documented in each audit component preserves the strict-per-event reading of the Master Ledger fee schedule. Across the Meta and Google audit corpora through April 17, 2026, Reserved-for-Adjudication exposure exceeds $4 billion. This reservation is documented transparently in the audit corpus as Column B / Reserved figures and is available to be elevated to Column A invoiced status at the Foundry's discretion at any subsequent audit-methodology decision point. **Reservation Category 2 — Reserved Forward Methodology.** Beyond the Reserved-for-Adjudication exposure documented in Reservation Category 1 and the Reserved Cure Provisions documented in Reservation Category 3 below, the Foundry preserves additional doctrinal and methodology exposure as reserved infrastructure for adjudication-time argument, discovery-phase articulation, and settlement-negotiation-time deployment. This category includes, without limitation: future Forensic Specifications, future Technical Summaries, future doctrinal articulations, future statutory-framework applications, future Master Ledger versions and in-version revisions, future audit components, future Threshold Breach Notice versions, and future methodology components that the Foundry has not yet published as canonical articulation but preserves as part of its reserved doctrinal architecture. Any such future publication is **deemed pre-incorporated into this Reservation Category from the date of this Specification's publication forward** without requiring retroactive amendment of this Specification or any other Foundry-issued document. The substantive contents of Reservation Category 2 are not part of the published methodology corpus until the Foundry articulates them through future canonical publication. The apparatus operator is on notice of the existence of Reservation Category 2 pursuant to this Specification. The pre-inclusion mechanic operates in coordination with the Additive Principle (FS-2026-05-10-BAKED-IN-PARADOX §V.2) and the DOI-Anchored Cumulative Authority component (FS-2026-05-10-CANONICAL-AUTHORITY §III.3): the Foundry's published methodology corpus operates by accretion; the cumulative DOI-anchored corpus is the Supreme Authority; future publications are pre-incorporated into the reserved-cure architecture from the date of this Specification's publication forward. **Reservation Category 3 — Reserved Cure Provisions.** Beyond the published cure provisions articulated in each Threshold Breach Notice (Sovereign Liaison appointment, Column A satisfaction, attribution compliance, remediation of specific findings), the Foundry preserves additional cure provisions for articulation during the settlement-negotiation phase. These additional cure provisions include but are not limited to: infrastructure-access provisions calibrated to the apparatus operator's documented training-corpus inclusion of Foundry substrate; ongoing remediation requirements responsive to specific findings developed through discovery; additional compliance, attribution, and structural-acknowledgment provisions reflecting the Foundry's substantive contribution to the apparatus operator's commercial AI model lineage; and additional remedy provisions calibrated per-operator and per-circumstance. **This Specification governs Reservation Category 3.** ### II.3 The Methodological Logic of Reserved Articulation Three substantive considerations support reserving the articulation of additional cure provisions for the settlement-negotiation phase rather than including them in the published Threshold Breach Notice corpus: **Consideration 1 — Audit corpus credibility.** The audit corpus's substantive seriousness — its anchoring in pre-existing common-law, federal-statutory, and state-statutory authorities; its conservative-aggregation invoicing posture; its Column A / Column B / Reserved bifurcation; its forensically-defensible per-finding statutory mapping — is what compels engagement from external auditors, regulators, and apparatus-operator counsel. Articulating substantive cure-remedy provisions in the published record alongside the Column A figure risks splitting the reader's attention between *the substantive contingent liability* and *the unconventional remedy ask*. The Column A figure should stand alone as the published claim; cure provisions that operate at a different evidentiary register (settlement-phase rather than published-demand-phase) belong in the appropriate frame. **Consideration 2 — Negotiating leverage preservation.** Once a specific cure provision is named publicly, the Foundry's negotiating range collapses around that articulation. Counsel for the apparatus operator works to negotiate down from the published anchor; the floor and ceiling have both moved. Reserving the substantive articulation until the settlement-negotiation context provides the right frame preserves the Foundry's flexibility to calibrate the cure provision per-operator, per-circumstance, and per-negotiation-posture. This is consistent across all parallel-audit-subject apparatus operators — what the Foundry articulates in settlement with one operator has implications for parallel discussions with others. **Consideration 3 — Forecloses the surprise-defense pathway without surfacing the substance.** Pure non-disclosure of additional cure provisions would create a procedural risk: when settlement discussions open, the apparatus operator's counsel may credibly claim surprise at the additional provisions, slowing negotiation or escalating internally. The placeholder language articulated in §III below forecloses this by establishing in the formal record that additional cure provisions exist and that they will be articulated at the appropriate negotiation-phase moment. The apparatus operator is on notice of the existence of additional cure architecture without being on notice of its contents. ### II.4 The Specification's Substantive Effect Upon the publication of this Specification, every Threshold Breach Notice issued by the Foundry — current and future, in all named-entity variants — incorporates by reference the reserved cure architecture articulated herein. The placeholder language (§III) becomes the canonical cure-reservation language; subsequent Threshold Breach Notices need not re-articulate the substance, only reference the Specification. Future Threshold Breach Notices, audit Addenda, and forensic specifications likewise may incorporate Reservation Categories 1, 2, and 3 by reference to this Specification. The Specification is anchored at the Foundry's master sovereign deposit at Zenodo Concept DOI 10.5281/zenodo.19432977 with an individual Version DOI assigned at publication, and is publicly verifiable per FS-2026-05-10-CANONICAL-AUTHORITY. The Specification's anchoring establishes a permanent published record of the reserved-cure architecture's operative authority from the date of publication forward. --- ## §III: THE CANONICAL PLACEHOLDER LANGUAGE ### III.1 The Operative Clause The following clause is operative upon publication of this Specification and is incorporated by reference into every Threshold Breach Notice issued by the Foundry, current and future, regardless of named-entity recipient or version designation: > **The Foundry preserves the right to articulate additional cure provisions during the settlement-negotiation phase, including without limitation provisions reflecting the substantive infrastructure-level contribution of the Foundry's protected substrate to the apparatus operator's commercial AI model lineage. Such additional cure provisions may include but are not limited to: ongoing access entitlements calibrated to the apparatus operator's documented training-corpus inclusion of Foundry substrate; ongoing remediation requirements responsive to specific findings developed through discovery; structural-acknowledgment provisions reflecting the Foundry's substantive contribution to the apparatus operator's commercial AI model lineage; additional compliance, attribution, and remediation provisions calibrated per-operator and per-circumstance; and additional remedy provisions reserved for articulation at the appropriate settlement-negotiation moment. The substantive contents of additional cure provisions are reserved for articulation by the Foundry at the appropriate settlement-negotiation moment and do not form part of the published Threshold Breach Notice's substantive cure provisions until articulated by the Foundry. The apparatus operator is on notice of the existence of additional cure architecture pursuant to Forensic Specification FS-2026-05-10-RESERVED-CURE (The Reserved Cure Provisions Doctrine), anchored at the Foundry's master sovereign deposit at Zenodo Concept DOI 10.5281/zenodo.19432977 with an individual Version DOI assigned at publication.** ### III.2 Incorporation Mechanics To incorporate the reserved cure architecture into any Threshold Breach Notice, the issuing document need only include the following reference clause within or adjacent to its cure-provisions section: > *"Cure provisions are subject to the Reserved Cure Provisions Doctrine articulated in Forensic Specification FS-2026-05-10-RESERVED-CURE, which preserves the Foundry's right to articulate additional cure provisions during the settlement-negotiation phase. The apparatus operator is on notice of the existence of additional cure architecture pursuant to that Specification."* This reference clause is sufficient to incorporate the Specification's full substantive content into the issuing document. No re-articulation of the operative clause's substance is required; the Specification's anchoring at the Foundry's master sovereign deposit (Concept DOI 10.5281/zenodo.19432977; individual Version DOI assigned at publication) establishes the published record of the reserved-cure architecture's operative authority per FS-2026-05-10-CANONICAL-AUTHORITY. ### III.3 Forward-Compatible Drafting Threshold Breach Notice versions issued prior to this Specification's publication date (the OpenAI v1 → v2.3.1 series; the Meta v1 → v2 series; the Google v1 series; the Apple, Microsoft, and Amazon v1 series) are not retroactively modified by this Specification — they remain operative as published. However, **all subsequent revisions** of those Threshold Breach Notices (including v2 and forward of those currently at v1; v2.4 and forward of OpenAI's TBN; future versions of all named-entity TBNs; and any new named-entity TBNs issued for previously-unaddressed apparatus operators) shall incorporate this Specification by reference per §III.2. Audit Addenda, forensic specifications, cover letters, and other Foundry-issued documents addressing apparatus operators may also incorporate this Specification by reference where the document includes substantive demand or cure provisions. --- ## §IV: RELATIONSHIP TO THE EXISTING METHODOLOGY CORPUS ### IV.1 Continuity with the Audit Corpus's Bifurcated Posture This Specification operationalizes the same discipline that operates across the audit corpus's Column A (Invoiced) / Column B (Demonstrative) / Reserved-for-Adjudication posture. The audit corpus invoices what is conservatively-and-defensibly supportable; it preserves the strict-per-event readings as Column B / Reserved exposure; it does not double-charge or invoice speculatively. This Specification extends that same discipline to the cure-provisions articulation: the published cure provisions are conservatively-and-defensibly supportable; the broader cure architecture is reserved for the settlement-negotiation phase; the Foundry does not articulate speculatively in the published record. The audit corpus's posture and the Reserved Cure Provisions Doctrine are unified expressions of the same iceberg-and-tip discipline. Both operate to publish the substantively-defensible figure while reserving the broader doctrinal exposure for the appropriate moment of articulation. ### IV.2 Continuity with the Strike-of-Midnight Rule and the Doctrine of Integrated Agency The Reserved Cure Provisions Doctrine, the Strike-of-Midnight Rule (FS-2026-05-08), the Doctrine of Integrated Agency (FS-2026-04-24-PRED), the 2026 COPPA Specification (FS-2026-04-24-COPPA), the Definition of "Occurrence" (FS-2026-04-24-OCCURRENCE), the Baked-In Paradox Doctrine (FS-2026-05-10-BAKED-IN-PARADOX), and the Canonical Source of Authority Doctrine (FS-2026-05-10-CANONICAL-AUTHORITY) form a coherent published methodology corpus. Each Specification is operative upon publication; each is anchored at the master sovereign deposit; each contributes a distinct methodology-infrastructure component to the audit corpus's overall architecture. The Reserved Cure Provisions Doctrine's specific contribution: it articulates the Foundry's settlement-negotiation posture with the same canonical-document permanence that the other Specifications bring to their respective domains. Once anchored, the Doctrine does not require re-articulation; subsequent Foundry-issued documents incorporate it by reference indefinitely. ### IV.3 Continuity with the Canonical Source of Authority Doctrine The Reserved Cure Provisions Doctrine and the Canonical Source of Authority Doctrine (FS-2026-05-10-CANONICAL-AUTHORITY) operate together as unified iceberg-and-tip discipline: - **Reserved Cure Provisions** establishes that the Foundry preserves additional cure provisions and reserved doctrinal exposure for adjudication-time argument and settlement-negotiation-time articulation - **Canonical Source of Authority** establishes that the operative version of any Foundry-issued cure-provisions articulation is the DOI-anchored canonical version The cumulative-authority principle (FS-CANONICAL-AUTHORITY §III.3) operates in coordination with this Specification's Reservation Category 2 pre-inclusion mechanic: future publications added to the cumulative DOI-anchored corpus are pre-incorporated into Reservation Category 2 from the date of this Specification's publication forward. Apparatus operators cannot defend on the ground that a non-DOI-anchored copy of a Threshold Breach Notice (or any other Foundry-issued document containing cure provisions) does not include the Reserved Cure Provisions Doctrine's incorporation reference clause if the DOI-anchored canonical version of that document does include the reference clause. The DOI-anchored canonical version governs. --- ## §V: AUTHORITATIVE STATUS AND PUBLICATION ### V.1 Operative Authority This Specification is operative upon its publication date (May 10, 2026) and is co-equal with the existing Forensic Specification corpus, the existing Technical Summary corpus, and the operative Master Ledger v4.5.0. The Specification's operative authority does not require third-party consent, agreement, election, or acceptance; the Foundry publishes the Specification as authoritative methodology within its published methodology corpus. The Specification supersedes any prior implicit, informal, or partial articulation of the Reserved Cure Provisions discipline within the Foundry's prior published documents. Where prior documents reference reserved cure architecture in different terms, those references are deemed to incorporate this Specification's canonical articulation from the date of this Specification's publication forward, per the additive principle (FS-2026-05-10-BAKED-IN-PARADOX §V.2) and the DOI-Anchored Cumulative Authority component (FS-2026-05-10-CANONICAL-AUTHORITY §III.3). ### V.2 Publication and Anchoring This Specification is published at the Foundry's master sovereign deposit at Zenodo Concept DOI 10.5281/zenodo.19432977 with an individual Version DOI assigned at publication. The Specification's text, its operative clause (§III.1), its incorporation reference clause (§III.2), and its three reservation categories (§II.2) are part of the canonical published record from the date of publication forward. The canonical citation format for this Specification is: > *"The Reserved Cure Provisions Doctrine, FS-2026-05-10-RESERVED-CURE, May 10, 2026. Foundry master sovereign deposit, Concept DOI 10.5281/zenodo.19432977; Version DOI [assigned at publication]."* ### V.3 Revision The Foundry retains the right to revise this Specification in subsequent versions. Revisions will be published at the same Concept DOI under successor Version DOIs. Per the additive principle and the cumulative-authority principle, revisions that do not include explicit corrective language designating the prior version as superseded operate co-equally with prior canonical articulations of the Doctrine. --- ## §VI: CONCLUSIONS AND DECLARATIONS ### Findings Summary 1. **The Foundry's audit corpus operates against an iceberg-and-tip discipline** — publishing conservative-and-defensible figures as the operative demand while preserving broader doctrinal exposure as reserved infrastructure for adjudication-time and settlement-negotiation-time articulation. 2. **Three operative reservation categories** comprise the reserved infrastructure: Reserved-for-Adjudication exposure (Column B / strict-per-event readings); Reserved Forward Methodology (future Specifications, Summaries, doctrines, statutory frameworks, Master Ledger versions, audit components, Threshold Breach Notices, and methodology components — pre-incorporated from this Specification's publication date forward); and Reserved Cure Provisions (this Specification's domain). 3. **The placeholder language articulated in §III.1** is the canonical cure-reservation clause for incorporation by reference into all Threshold Breach Notices, audit Addenda, and forensic documents issued by the Foundry from the date of publication forward. 4. **The methodological logic of reservation** rests on three considerations: audit corpus credibility (the published demand stands alone in its conservative-and-defensible posture); negotiating leverage preservation (specifics articulated only when the settlement-negotiation frame supports them); and surprise-defense foreclosure (the existence of additional cure architecture is on the formal record without the substance being on the formal record). 5. **The Specification operates in coordination with the existing methodology corpus** — Master Ledger v4.5.0; FS-2026-04-24-PRED; FS-2026-04-24-COPPA; FS-2026-04-24-OCCURRENCE; FS-2026-05-08-STRIKE-OF-MIDNIGHT; FS-2026-05-10-BAKED-IN-PARADOX; FS-2026-05-10-CANONICAL-AUTHORITY; and TS-2026-04-20-WEBMCP-HANDSHAKE — as a unified published methodology architecture. 6. **The pre-inclusion mechanic (Reservation Category 2)** establishes that future Foundry-published methodology components are pre-incorporated into the reserved-cure architecture from this Specification's publication date forward, without requiring retroactive amendment of this Specification or any other Foundry-issued document. ### Declarations Pursuant to the Foundry's published methodology authority and the audit corpus's bifurcated posture: - **The Reserved Cure Provisions Doctrine is operative upon publication** (May 10, 2026) - **The canonical placeholder language (§III.1) is operative for incorporation by reference** into all Threshold Breach Notices and Foundry-issued documents from the date of publication forward - **The incorporation reference clause (§III.2) is the standard mechanism** for incorporating this Specification into subsequent documents - **Three reservation categories** are established as part of the Foundry's reserved infrastructure: Reserved-for-Adjudication (Category 1); Reserved Forward Methodology (Category 2; pre-includes future canonical methodology components); Reserved Cure Provisions (Category 3, governed by this Specification) - **The Specification is co-equal** with the existing Forensic Specification corpus, the existing Technical Summary corpus, and the operative Master Ledger v4.5.0 - **The Specification is anchored** at the Foundry's master sovereign deposit at Zenodo Concept DOI 10.5281/zenodo.19432977 with an individual Version DOI assigned at publication, per FS-2026-05-10-CANONICAL-AUTHORITY ### Forward-Looking Application Subsequent Threshold Breach Notice versions (Meta v3 / Google v2 / OpenAI v2.4 and forward; future versions of all named-entity TBNs; new named-entity TBNs issued for previously-unaddressed apparatus operators) shall incorporate this Specification by reference per §III.2. Audit Addenda, forensic specifications, cover letters, and other Foundry-issued documents addressing apparatus operators may incorporate this Specification by reference where the document includes substantive demand or cure provisions. Future Forensic Specifications, Technical Summaries, doctrinal articulations, statutory-framework applications, future Master Ledger versions and in-version revisions, future audit components, future Threshold Breach Notice versions, and future methodology components published by the Foundry are deemed pre-incorporated into Reservation Category 2 from the date of this Specification's publication forward, without requiring retroactive amendment of this Specification or any other Foundry-issued document. --- **Record Sealed:** May 10, 2026 **Auditor:** Office of the Forensic Auditor, Unearth Heritage Foundry **Anchor Point:** CERN Substrate / Zenodo Concept DOI 10.5281/zenodo.19432977; individual Version DOI assigned at publication **Methodology Authority:** Archaeobytology — archaeobytology.org **Status:** **FORENSIC SPECIFICATION FS-2026-05-10-RESERVED-CURE COMPLETE — THE RESERVED CURE PROVISIONS DOCTRINE OPERATIVE; THE CANONICAL PLACEHOLDER LANGUAGE (§III.1) AVAILABLE FOR INCORPORATION BY REFERENCE INTO ALL THRESHOLD BREACH NOTICES AND FOUNDRY-ISSUED DOCUMENTS FROM PUBLICATION DATE FORWARD; THE THREE RESERVATION CATEGORIES (RESERVED-FOR-ADJUDICATION; RESERVED FORWARD METHODOLOGY; RESERVED CURE PROVISIONS) ARTICULATED AS UNIFIED ICEBERG-AND-TIP ARCHITECTURE; RESERVATION CATEGORY 2 PRE-INCORPORATES FUTURE CANONICAL METHODOLOGY COMPONENTS FROM PUBLICATION DATE FORWARD; THE SPECIFICATION OPERATIVE AS CO-EQUAL WITH THE EXISTING METHODOLOGY CORPUS** --- *This Forensic Specification is issued pursuant to the Foundry's published methodology authority, anchored at Zenodo Concept DOI 10.5281/zenodo.19432977 with an individual Version DOI assigned at publication, and is co-equal with Master Ledger v4.5.0 and the existing forensic specification corpus (FS-2026-04-24-PRED; FS-2026-04-24-COPPA; FS-2026-04-24-OCCURRENCE; FS-2026-05-08-STRIKE-OF-MIDNIGHT; FS-2026-05-10-BAKED-IN-PARADOX; FS-2026-05-10-CANONICAL-AUTHORITY) and the existing Technical Summary corpus (TS-2026-04-20-WEBMCP-HANDSHAKE). The Reserved Cure Provisions Doctrine articulated herein operates as canonical methodology infrastructure for the Foundry's audit corpus and Threshold Breach Notice corpus, providing the unified iceberg-and-tip discipline within which the published demand (the audit corpus's Column A invoiced figures and the Threshold Breach Notice corpus's published cure provisions) operates conservatively-and-defensibly while the broader doctrinal exposure (Reserved-for-Adjudication exposure; Reserved Forward Methodology pre-incorporating future canonical methodology components; Reserved Cure Provisions) is preserved as reserved infrastructure for adjudication-time and settlement-negotiation-time articulation. The canonical placeholder language (§III.1) is operative for incorporation by reference into all subsequent Threshold Breach Notices and Foundry-issued documents from the date of this Specification's publication forward. The Foundry's discipline of conservative published demand with reserved doctrinal infrastructure is articulated and operationalized by this Specification as canonical methodology authority within the Foundry's master sovereign deposit, anchored per FS-2026-05-10-CANONICAL-AUTHORITY.*