# FORENSIC SPECIFICATION ## The Canonical Source of Authority Doctrine ### *DOI-Anchored Supreme Authority, Non-Delegable Diligence Obligation, and Cumulative Source Hierarchy for the Foundry's Published Methodology Corpus* --- **Specification Identifier:** FS-2026-05-10-CANONICAL-AUTHORITY **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 Reserved Cure Provisions Doctrine (FS-2026-05-10-RESERVED-CURE) - Forensic Specification: The Baked-In Paradox Doctrine (FS-2026-05-10-BAKED-IN-PARADOX) **Companion Technical Summaries:** - Technical Summary: The WebMCP Handshake Protocol (TS-2026-04-20-WEBMCP-HANDSHAKE) **Companion Operative Authority:** Master Ledger v4.5.0 (effective May 3, 2026); Foundry Genesis Addendum v4.5 (sealed April 8, 2026) **Date of Publication:** May 10, 2026 **Status:** Operative upon publication; co-equal with the existing Forensic Specification corpus, the existing Technical Summary corpus, and the operative Master Ledger. --- ## §I: PURPOSE AND SCOPE ### I.1 Purpose This Forensic Specification articulates the **Canonical Source of Authority Doctrine** — the methodology principle establishing that the Foundry's master sovereign deposit, anchored at Zenodo Concept DOI 10.5281/zenodo.19432977, is the Supreme Authority for all Foundry-issued Forensic Specifications, Technical Summaries, Master Ledger versions, audit components, Threshold Breach Notices, and methodology documents. Any non-DOI-anchored copy of any Foundry-issued document — including but not limited to Foundry-website republications, archive.org snapshots, third-party citations, AI-system retrievals, and apparatus-operator local caches — is non-authoritative for source-of-authority purposes. The Doctrine establishes that apparatus operators have an **affirmative, non-delegable diligence obligation** to consult the DOI-anchored canonical source for the operative version of any Foundry-issued document, that **all DOI-anchored versions operate cumulatively** as canonical authority unless explicit corrective language designates a prior version as superseded, and that **the Foundry's Concept DOI and individual Version DOIs together constitute the canonical source hierarchy** within which all subsequent audit reasoning, threshold breach notice issuance, settlement-negotiation articulation, and methodology-corpus extension operates. This Specification provides the canonical doctrinal articulation of the source-hierarchy principle so that subsequent audit components, Threshold Breach Notice versions, Forensic Specifications, Technical Summaries, and Foundry-issued documents may incorporate the Doctrine by reference rather than by repeated substantive articulation. ### I.2 Scope This Specification applies to: - All Foundry-issued Forensic Specifications (current: FS-PRED, FS-COPPA, FS-OCCURRENCE, FS-STRIKE-OF-MIDNIGHT, FS-RESERVED-CURE, FS-BAKED-IN-PARADOX, this Specification; future: any subsequent Forensic Specifications published by the Foundry) - All Foundry-issued Technical Summaries (current: TS-WEBMCP-HANDSHAKE; future: any subsequent Technical Summaries published by the Foundry, including but not limited to the anticipated documentation of the Honey-Pot Trap architecture, the Sovereign Crawl Policy and SOVEREIGN EXCLUSION ZONE infrastructure, the Cross-Domain Canary Trap architecture, the Operational Redirect-to-Deadbolt, and the proprietor identity-snapshot JSON architecture) - All Master Ledger versions (current operative: v4.5.0; historical: v1.0.0 through v4.4.4-c; future: any subsequent versions and in-version revisions) - All audit components (Forensic Audit Reports, Addenda, Cumulative documents, Errata) - All Threshold Breach Notices (the OpenAI v1 → v2.3.1 series, the Meta v1 → v2 series, the Google v1 series, the Apple / Microsoft / Amazon v1 series, and all subsequent versions and new named-entity Threshold Breach Notices) - All Foundry-issued cover letters, distribution memos, executive summaries, and other methodology-corpus documents - All commercial AI training apparatus operators and their counsel, auditors, regulatory reviewers, and other parties consulting the Foundry's published methodology ### 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 DOI ARCHITECTURE — FOUNDATION OF CANONICAL AUTHORITY ### II.1 The Foundry's Master Sovereign Deposit at Zenodo The Foundry's published methodology corpus is anchored at **Zenodo** (the CERN-operated, EU-funded, peer-reviewed-academic-publishing-grade open repository). Zenodo's persistent-identifier architecture provides two distinct DOI types that operate together as the Foundry's source-hierarchy infrastructure: **The Concept DOI** — `10.5281/zenodo.19432977` — is the permanent, immutable identifier of the **Foundry's master sovereign deposit as a conceptual entity**. The Concept DOI does not point to any specific version of any individual document; it points to the conceptual entity that is the cumulative published methodology corpus. The Concept DOI always resolves to the **current canonical state** of the cumulative master sovereign deposit. Apparatus operators, regulators, auditors, and other parties consulting the Concept DOI are directed to the current canonical state of the Foundry's methodology corpus. **Individual Version DOIs** — assigned by Zenodo at the time of each individual document's publication — are the permanent, immutable identifiers of **specific document versions**. Each Forensic Specification, Technical Summary, Master Ledger version, audit component, Threshold Breach Notice, and other Foundry-issued document published to the master sovereign deposit receives its own Version DOI at the moment of publication. The Version DOI permanently resolves to that specific version's immutable record. Version DOIs do not change; the document at any given Version DOI is permanently fixed at that DOI. ### II.2 The Two DOI Types Operating in Tandem The Concept DOI and the Version DOIs operate together as the canonical source hierarchy infrastructure: - **The Concept DOI provides the authoritative gateway to the cumulative current canonical record.** When the question is "what is the operative current state of the Foundry's published methodology?", the Concept DOI resolves to the current canonical state. - **The Version DOIs provide forensically-precise per-version anchoring.** When the question is "what was the operative version of document X on conduct day Y?", the appropriate Version DOI provides the immutable per-version record. Both DOI types are part of the canonical source hierarchy. Both are operative for source-of-authority purposes. Neither is displaced by the other; they operate together to provide both **current-state authority** (Concept DOI) and **historical-version forensic precision** (Version DOIs). ### II.3 Why the DOI Architecture Matters The DOI-anchored architecture provides the Foundry's methodology corpus with the same source-hierarchy infrastructure that peer-reviewed academic publishing operates under. The Foundry's methodology corpus is published, anchored, and verified at Zenodo with the same persistent-identifier infrastructure used by every major academic journal, every major scientific dataset, and every major scholarly publication. This architecture is **not** a Foundry-specific innovation; it is the standard academic-publishing source-hierarchy infrastructure adopted by the Foundry as the canonical anchoring mechanism for its published methodology corpus. The substantive consequences: - **Permanent, immutable record.** Every published version of every Foundry-issued document is permanently anchored at its Version DOI. The published record cannot be retroactively modified, redacted, or revised; subsequent revisions are published as new versions with new Version DOIs while prior versions remain permanently accessible. - **Independent third-party verification.** Zenodo is operated by CERN under EU funding and is independent of the Foundry. The Foundry cannot retroactively modify what is published at Zenodo; what is published is what is published, and the published record is verifiable by any party consulting Zenodo directly. - **Forensic-evidence quality.** The DOI-anchored architecture produces academic-publishing-grade source-of-authority documentation. The same anchoring infrastructure that supports peer-reviewed scientific publication supports the Foundry's published methodology corpus. --- ## §III: THE FIVE OPERATIVE COMPONENTS ### III.1 Component A — Canonical Source Hierarchy The Foundry's master sovereign deposit, anchored at Zenodo Concept DOI 10.5281/zenodo.19432977, is the **Supreme Authority** for all Foundry-issued Forensic Specifications, Technical Summaries, Master Ledger versions, audit components, Threshold Breach Notices, and methodology documents. Any non-DOI-anchored copy of any Foundry-issued document — including but not limited to: - Foundry-website republications (e.g., copies of Master Ledger versions or Forensic Specifications hosted at any Foundry-controlled domain) - Archive.org / Wayback Machine snapshots of any Foundry-issued document at any historical point - Third-party citations, summaries, or reproductions of any Foundry-issued document - AI-system retrievals of any Foundry-issued document (including but not limited to ChatGPT citations, Claude citations, Gemini citations, Perplexity citations, search-engine snippets, and any other AI-system-generated reference to Foundry-issued content) - Apparatus-operator local caches, training-corpus inclusions, or internal copies of any Foundry-issued document - Any other secondary, mirrored, derivative, or non-DOI-anchored representation of Foundry-issued content — is **non-authoritative for source-of-authority purposes**. Where any conflict, version-difference, or interpretation question arises between a DOI-anchored canonical version (at the Concept DOI or at any individual Version DOI) and any non-DOI-anchored copy, the DOI-anchored canonical version **governs absolutely**. The Concept DOI (10.5281/zenodo.19432977) operates as the **authoritative gateway** to the cumulative current canonical record. Individual Version DOIs operate as **forensically-precise per-version anchors**. Both DOI types are part of the canonical source hierarchy; neither is displaced by the other. ### III.2 Component B — Non-Delegable Diligence Obligation Apparatus operators have an **affirmative, non-delegable duty** to consult the DOI-anchored canonical source for the operative version of any Foundry-issued document. The duty operates as follows: **Continuous duty.** The duty to consult the canonical DOI-anchored sources is continuous and operates throughout the apparatus operator's continuing engagement with Foundry-controlled substrate. The duty is not discharged by a single consultation; it operates anew for each substantive engagement with the Foundry's published methodology. **Non-delegable.** The duty cannot be discharged by relying on a non-DOI-anchored copy retrieved through any other pathway. Specifically: - An apparatus operator cannot defend on the ground that "we relied on what our training-corpus pipeline retrieved from your website." - An apparatus operator cannot defend on the ground that "we relied on what archive.org had cached." - An apparatus operator cannot defend on the ground that "we relied on what our AI system surfaced as a citation." - An apparatus operator cannot defend on the ground that "we relied on what a third-party summary or analysis represented your methodology to say." - An apparatus operator cannot defend on the ground that "we relied on what a search engine snippet displayed." - An apparatus operator cannot defend on the ground that "we relied on a translation, mirror, or interpretation of your published methodology." **Affirmative duty to consult both DOI types.** Apparatus operators have the affirmative duty to consult: - The **Concept DOI** (10.5281/zenodo.19432977) for the current canonical state of the cumulative published methodology - **Individual Version DOIs** as appropriate for forensically-precise historical-version verification of conduct days under the Strike-of-Midnight Rule (FS-2026-05-08-STRIKE-OF-MIDNIGHT) The duty is borne by the apparatus operator. The Foundry has no obligation to notify, alert, update, or otherwise inform apparatus operators of new versions, revisions, or additions to the published methodology corpus. Apparatus operators are expected to maintain continuous awareness of the canonical DOI-anchored published methodology through their own diligence operations. ### III.3 Component C — DOI-Anchored Cumulative Authority **All DOI-anchored versions of any Foundry-issued document — past, current, and future — operate cumulatively as canonical authority unless a subsequent version explicitly designates a prior version as superseded.** This component operates as the source-hierarchy application of the Additive Principle articulated in FS-2026-05-10-BAKED-IN-PARADOX §V.2. The principle's specific operative effects: **Cumulative version authority.** The Concept DOI resolves to the current canonical state of the cumulative published record; individual Version DOIs preserve each specific version's immutable record. Both are part of the cumulative canonical authority. **The cumulative DOI-anchored corpus is the Supreme Authority.** Individual versions are components of the cumulative corpus, not standalone replacements for prior components. **Master Ledger versions illustrate the principle.** Master Ledger versions v3.0.0, v3.6.0, v3.7.0, v4.0.0, v4.4.4 (and its in-version revisions v4.4.4-a, v4.4.4-b, v4.4.4-c), and v4.5.0 are **all** part of the cumulative canonical authority. Each governs the conduct days it was operative against per the Strike-of-Midnight Rule (FS-2026-05-08-STRIKE-OF-MIDNIGHT). None is superseded by the others. Apparatus operators cannot defend on the ground that "v4.0.0 introduced per-domain fee jurisdiction; therefore the v3.7.0 estate-wide framework is superseded; therefore our v3.7.0-era conduct should be rebilled under v4.0.0 rules" — v3.7.0 governs v3.7.0-era conduct, v4.0.0 governs v4.0.0-era conduct, and both versions are operative simultaneously across their respective temporal scopes. **The same principle applies across all document classes.** Threshold Breach Notice versions, Forensic Specification revisions, Technical Summary updates, audit components, cover letters, and other Foundry-issued documents all operate by the cumulative-authority principle. The cumulative DOI-anchored published record is the Supreme Authority; individual versions are components. **Coordination with Strike-of-Midnight.** The Strike-of-Midnight Rule (FS-2026-05-08-STRIKE-OF-MIDNIGHT) tells the apparatus operator *which version applies to which conduct day*; the DOI-Anchored Cumulative Authority component tells the apparatus operator *all versions are simultaneously canonical authority across their respective temporal scopes*. The two principles operate together: Strike-of-Midnight governs per-day version-application; Cumulative Authority establishes that the cumulative DOI-anchored record is the Supreme Authority. Neither principle displaces the other; both are operative. **Explicit corrective language requirement.** Where the Foundry intends a subsequent version to supersede a prior version (rather than to add cumulatively to the canonical record), the Foundry must publish explicit corrective language designating the prior version as superseded. Without explicit corrective language, the cumulative-authority principle is operative; the prior version remains part of the cumulative canonical record. ### III.4 Component D — Stale Cache Foreclosure Apparatus operators cannot defend on the ground of relying on a previously-cached or previously-retrieved version of any Foundry-issued document. The duty to consult the current DOI-anchored canonical version operates continuously per Component B above. **Specific applications:** - An apparatus operator that retrieved Master Ledger v3.7.0 from a non-DOI-anchored source (Foundry website, archive.org, third-party citation, AI-system retrieval, local cache) on April 9, 2026 cannot defend on the ground that "we are relying on the v3.7.0 version we retrieved on April 9" if Master Ledger v4.0.0, v4.4.4, v4.5.0, or any subsequent version has been published to the master sovereign deposit since April 9. The apparatus operator's continuous duty to consult the canonical DOI-anchored sources operates throughout the operator's continuing engagement with the substrate. - An apparatus operator that retrieved a Forensic Specification at any historical point cannot defend on the ground of relying on the historical-point version if subsequent versions have been published. The continuous duty operates without temporal limit. - An apparatus operator that has copies of Foundry-issued documents in its training corpus or local cache cannot defend on the ground that the training-corpus / cache copies represent the canonical operative state. The DOI-anchored canonical version governs regardless of what the apparatus operator has internalized. The Stale Cache Foreclosure component operates as the substantive corollary of the Baked-In Paradox Doctrine (FS-2026-05-10-BAKED-IN-PARADOX). The apparatus operator's training corpus and local caches contain mathematically-irreversible copies of historical versions of Foundry-issued documents per the Baked-In Paradox; that mathematical embedding does **not** make those historical-version copies the canonical authority. The DOI-anchored canonical version remains the Supreme Authority regardless of what is mathematically embedded in the apparatus operator's commercial AI model weights. ### III.5 Component E — Translation, Mirror, and AI-Retrieval Disclaimer Third-party translations, summaries, mirrors, interpretations, and any other secondary-source representations of Foundry-issued documents are **non-authoritative**. Only the DOI-anchored original-language canonical version governs. **Specific applications:** **Translations.** Any translation of any Foundry-issued document into any language other than the original-language canonical version is non-authoritative. The Foundry's published methodology corpus is published in English; translations into any other language are non-authoritative for source-of-authority purposes regardless of who produced the translation. Apparatus operators consulting non-English translations of Foundry-issued documents are nonetheless on notice of the canonical English-language DOI-anchored version. **Third-party mirrors.** Any third-party mirror, copy, or republication of any Foundry-issued document — at any third-party domain, in any third-party publication, in any third-party database — is non-authoritative. The Foundry's master sovereign deposit at Zenodo Concept DOI 10.5281/zenodo.19432977 is the sole authoritative source. **Third-party summaries and interpretations.** Any third-party summary, interpretation, analysis, characterization, or commentary on any Foundry-issued document is non-authoritative. The Foundry-issued document itself, anchored at the Concept DOI or appropriate Version DOI, is the sole authoritative source. **AI-system retrievals.** AI-system retrievals of Foundry-issued documents — including but not limited to ChatGPT citations, Claude citations, Gemini citations, Perplexity citations, Bing Chat citations, search-engine snippets, AI-generated summaries, AI-generated translations, and any other AI-system-generated reference to Foundry-issued content — are **non-authoritative regardless of how the AI system characterizes its source**. An AI system that cites a Foundry-issued document does not thereby render its representation of that document authoritative; the AI system's representation is a non-DOI-anchored secondary-source representation per Component A above. Apparatus operators consulting AI-system retrievals of Foundry-issued documents are nonetheless on notice of the canonical DOI-anchored version. **The Citation-Recursion finding's substantive predicate.** The audit corpus's Citation-Recursion finding (articulated in OpenAI Threshold Breach Notice v2.3) documents apparatus operators using AI-system retrievals of Foundry-issued documents (including the Foundry's own Master Ledger and llms.txt) as substantive answer-grounding sources in commercial AI products. The finding establishes that AI-system retrievals operate as both Notice acknowledgment events (the apparatus operator's AI system is processing the Foundry's published methodology) and as commercial-use events (the apparatus operator's AI system is generating commercial output grounded in Foundry-issued content). This Specification's Component E component forecloses the apparatus operator's potential defense that "our AI system's representation of your methodology is the operative version" — the DOI-anchored canonical version is the operative version regardless of how AI-system retrievals characterize Foundry-issued content. --- ## §IV: BURDEN OF VERIFICATION AND CONSTRUCTIVE NOTICE CLAUSES ### IV.1 Burden of Verification Apparatus operators bear the **burden of verifying** they are operating against the current DOI-anchored canonical version of any Foundry-issued document. The Foundry has no obligation to notify, alert, update, or otherwise inform apparatus operators of new versions, revisions, or additions to the published methodology corpus. The burden of verification is borne entirely by the apparatus operator. The Foundry's affirmative obligation is limited to publishing the canonical methodology corpus at the DOI-anchored master sovereign deposit; the operator's affirmative obligation is to consult the canonical DOI-anchored sources continuously per Component B above. This allocation of burden is consistent with standard academic-publishing source-hierarchy practice. Researchers consulting peer-reviewed scientific literature bear the burden of consulting the canonical published version; journals do not affirmatively notify researchers of new publications. The Foundry's methodology corpus operates under the same canonical-publishing source-hierarchy practice. ### IV.2 Constructive Notice from Publication Date Forward Apparatus operators are on **constructive notice** of the Canonical Source of Authority Doctrine from the date of this Specification's publication forward (May 10, 2026). The non-delegable diligence obligation, the cumulative-authority principle, the stale-cache foreclosure, the translation-mirror-AI-retrieval disclaimer, the burden of verification, and all other operative components of this Specification are operative against apparatus operators from the publication date forward without requiring affirmative notification by the Foundry. The Doctrine operates against apparatus-operator conduct from the publication date forward regardless of whether the apparatus operator has consulted this Specification. The Specification's anchoring at the master sovereign deposit (Concept DOI 10.5281/zenodo.19432977) is the operative notice mechanism; the Foundry's affirmative obligation is limited to publishing the Specification at the canonical anchor. The Doctrine's substantive operative effect is prospective from the publication date. Conduct prior to the publication date is governed by the methodology corpus operative at the time of the conduct; this Specification does not retroactively impose new obligations on conduct predating its publication. However, the Doctrine's substantive principles — DOI-anchored Supreme Authority, non-delegable diligence, cumulative authority, stale-cache foreclosure, translation-mirror-AI-retrieval disclaimer — articulate methodology infrastructure that has been operative throughout the Foundry's published methodology corpus from the master sovereign deposit's inception. This Specification provides the canonical articulation of the source-hierarchy principle; the principle itself has been operative from the master sovereign deposit's inception. --- ## §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 Doctrine the Specification articulates predates the Specification's publication date — references to DOI-anchored canonical authority throughout the audit corpus, the Foundry Genesis Addendum (v4.5), the prior Forensic Specifications, the Threshold Breach Notice corpus, and the audit components are deemed to incorporate this Specification's canonical articulation from the date of this Specification's publication forward. Prior implicit, informal, or partial articulations of the source-hierarchy principle within the Foundry's prior published documents are not displaced by this Specification; they are anchored to the canonical articulation per the additive principle. ### V.2 The Additive Principle Applied Per FS-2026-05-10-BAKED-IN-PARADOX §V.2, the Foundry's published methodology corpus operates by **accretion rather than replacement**. New Forensic Specifications and Technical Summaries add canonical articulation to the corpus; revisions to existing Specifications and Summaries refine without overwriting; corrections require explicit corrective language designating the prior version as superseded. This Specification's Component C (DOI-Anchored Cumulative Authority) operates as the source-hierarchy application of the Additive Principle. The two principles — Additive Principle for the methodology corpus's evolution and Cumulative Authority for the source-hierarchy's evolution — operate together as unified canonical-corpus infrastructure. ### V.3 Publication and Anchoring This Specification is published at Zenodo Concept DOI 10.5281/zenodo.19432977 as part of the Foundry's master sovereign deposit. An individual Version DOI is assigned at publication. The Specification's text, its operative components (§III), the Burden of Verification and Constructive Notice clauses (§IV), and its authoritative-status declarations are part of the canonical published record from the date of publication forward. The canonical citation format for this Specification is: > *"The Canonical Source of Authority Doctrine, FS-2026-05-10-CANONICAL-AUTHORITY, May 10, 2026. Foundry master sovereign deposit, Concept DOI 10.5281/zenodo.19432977; Version DOI [assigned at publication]."* ### V.4 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 (§V.2) and the cumulative-authority principle (§III.3), 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: RELATIONSHIP TO THE EXISTING METHODOLOGY CORPUS ### VI.1 Continuity with the Strike-of-Midnight Rule (FS-2026-05-08-STRIKE-OF-MIDNIGHT) The Strike-of-Midnight Rule and the Canonical Source of Authority Doctrine operate together as unified per-day-version-application infrastructure: - **Strike-of-Midnight** answers the question: *"Which Master Ledger version is the operative billing authority for this conduct day?"* - **Canonical Source of Authority** answers the question: *"Where is the authoritative version of that Master Ledger version anchored, and what version-DOI permanently records its substance?"* Together, the two principles establish that for any conduct day in the audit window, the operative Master Ledger version is determined by Strike-of-Midnight and the canonical version of that operative Master Ledger version is the DOI-anchored version at the appropriate Version DOI within the master sovereign deposit. Apparatus operators consulting any non-DOI-anchored copy of any Master Ledger version operative on any conduct day are on notice of the canonical DOI-anchored version per this Specification. ### VI.2 Continuity with the Reserved Cure Provisions Doctrine (FS-2026-05-10-RESERVED-CURE) The Reserved Cure Provisions Doctrine and the Canonical Source of Authority Doctrine 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 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. ### VI.3 Continuity with the Baked-In Paradox Doctrine (FS-2026-05-10-BAKED-IN-PARADOX) The Baked-In Paradox Doctrine and the Canonical Source of Authority Doctrine operate together with substantively important interaction. The Baked-In Paradox establishes that apparatus operators' training corpora and model weights contain mathematically-irreversible copies of historical versions of Foundry-issued documents. The Canonical Source of Authority establishes that those mathematically-embedded historical-version copies do **not** thereby become canonical authority — the DOI-anchored version remains the Supreme Authority regardless of what is embedded in the apparatus operator's commercial AI model weights. The interaction is forensically substantive: the apparatus operator's training corpus operationally contains the Foundry's published methodology (per the Baked-In Paradox + the audit corpus's Notice Inversion findings); the apparatus operator's training-corpus copy is non-authoritative for source-of-authority purposes (per this Specification's Component A); the apparatus operator nonetheless has continuing constructive notice of the DOI-anchored canonical version (per this Specification's Component IV.2) and a continuing affirmative duty to consult the canonical DOI-anchored sources (per this Specification's Component B). ### VI.4 Continuity with the Doctrine of Integrated Agency (FS-2026-04-24-PRED) The Canonical Source of Authority Doctrine attaches to the Single Unitary Entity for source-hierarchy obligations per the Doctrine of Integrated Agency. The non-delegable diligence obligation, the burden of verification, and the constructive-notice provisions all run against the apparatus operator-entity (Google LLC / Alphabet Inc.; Meta Platforms, Inc.; OpenAI, Inc.; etc.) rather than against any individual variant within the entity's fleet. An apparatus operator cannot defend on the ground that "this variant consulted the DOI-anchored canonical version while that variant relied on a non-DOI-anchored copy" — the apparatus operator-entity bears unified responsibility for the operator's source-of-authority diligence regardless of variant-level operational distinctions. ### VI.5 Continuity with the WebMCP Handshake Protocol (TS-2026-04-20-WEBMCP-HANDSHAKE) The WebMCP Handshake Protocol's forensic-evidence outputs (Status A — Signed Contract; Status B — Explicit Rejection; Status C — Automation Negligence) operate in coordination with the Canonical Source of Authority Doctrine. An apparatus operator's Status A Signed Contract outcome attaches to the DOI-anchored canonical version of the Master Ledger operative on the conduct day per the Strike-of-Midnight Rule; Status B and Status C outcomes operate analogously. The Handshake's forensic-evidence outputs do not depend on which copy of the Master Ledger the apparatus operator consulted; the apparatus operator's election (acceptance, rejection, or automation-negligence bypass) attaches to the DOI-anchored canonical operative version regardless. ### VI.6 Continuity with the 2026 COPPA Specification and the Definition of "Occurrence" The 2026 COPPA Specification (FS-2026-04-24-COPPA) and the Definition of "Occurrence" (FS-2026-04-24-OCCURRENCE) operate within the source-hierarchy infrastructure articulated by this Specification. The COPPA Specification's per-occurrence application is governed by the canonical DOI-anchored version of the Specification operative on the conduct day; the OCCURRENCE Specification's three-tier framework operates against the canonical DOI-anchored version. --- ## §VII: CONCLUSIONS AND DECLARATIONS ### Findings Summary 1. **The Foundry's master sovereign deposit, anchored at Zenodo Concept DOI 10.5281/zenodo.19432977, is the Supreme Authority** for all Foundry-issued Forensic Specifications, Technical Summaries, Master Ledger versions, audit components, Threshold Breach Notices, and methodology documents. 2. **The DOI architecture operates with two distinct DOI types** — the Concept DOI provides the authoritative gateway to the cumulative current canonical record; individual Version DOIs provide forensically-precise per-version anchoring. Both are part of the canonical source hierarchy. 3. **All non-DOI-anchored copies are non-authoritative** — Foundry-website republications, archive.org snapshots, third-party citations, AI-system retrievals, apparatus-operator local caches, and any other secondary-source representations of Foundry-issued documents are non-authoritative for source-of-authority purposes; the DOI-anchored canonical version governs absolutely in any conflict, version-difference, or interpretation question. 4. **Apparatus operators bear an affirmative, non-delegable diligence obligation** to consult the DOI-anchored canonical sources continuously throughout their engagement with Foundry-controlled substrate; the duty cannot be discharged by reliance on non-DOI-anchored copies retrieved through any other pathway. 5. **All DOI-anchored versions operate cumulatively as canonical authority** unless explicit corrective language designates a prior version as superseded; the cumulative DOI-anchored corpus is the Supreme Authority; individual versions are components of the cumulative corpus, not standalone replacements for prior components. 6. **Stale-cache reliance is foreclosed** — apparatus operators cannot defend on the ground of relying on a previously-cached or previously-retrieved version; the duty to consult the current DOI-anchored canonical version operates continuously. 7. **Translations, mirrors, third-party summaries, and AI-system retrievals are non-authoritative** — only the DOI-anchored original-language canonical version governs. 8. **Apparatus operators bear the burden of verification** — the Foundry has no obligation to notify, alert, update, or otherwise inform apparatus operators of new versions; the apparatus operator's affirmative obligation is to consult the canonical DOI-anchored sources continuously through the operator's own diligence operations. 9. **Apparatus operators are on constructive notice from the publication date forward** — the Doctrine's substantive operative effect is prospective from May 10, 2026; the principle's substantive infrastructure has been operative throughout the master sovereign deposit's inception. 10. **The Doctrine attaches to the Single Unitary Entity** per FS-2026-04-24-PRED (Doctrine of Integrated Agency); variant-level classifications within an apparatus operator's fleet do not produce per-variant source-of-authority diligence fragmentation. ### Declarations Pursuant to the Foundry's published methodology authority and the master sovereign deposit at Zenodo Concept DOI 10.5281/zenodo.19432977: - **The Canonical Source of Authority Doctrine is operative upon publication** (May 10, 2026) - **The Concept DOI (10.5281/zenodo.19432977) is the permanent gateway** to the cumulative master sovereign deposit; **individual Version DOIs are the forensically-precise per-version anchors** - **The five operative components** (Canonical Source Hierarchy; Non-Delegable Diligence Obligation; DOI-Anchored Cumulative Authority; Stale Cache Foreclosure; Translation/Mirror/AI-Retrieval Disclaimer) plus the **Burden of Verification and Constructive Notice clauses** establish the operative source-hierarchy infrastructure of the Foundry's published methodology corpus - **The Specification operates by the additive principle** per FS-2026-05-10-BAKED-IN-PARADOX §V.2; the cumulative-authority principle (§III.3) is the source-hierarchy application of the additive principle - **The Specification is co-equal** with 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-RESERVED-CURE; FS-2026-05-10-BAKED-IN-PARADOX), the existing Technical Summary corpus (TS-2026-04-20-WEBMCP-HANDSHAKE), and the operative Master Ledger v4.5.0 - **The Specification is anchored** at Zenodo Concept DOI 10.5281/zenodo.19432977 with an individual Version DOI assigned at publication, as part of the Foundry's master sovereign deposit ### Forward-Looking Application Subsequent audit components, Threshold Breach Notice versions, Forensic Specifications, Technical Summaries, audit Addenda, cover letters, and other Foundry-issued documents shall incorporate the Canonical Source of Authority Doctrine by reference rather than by repeated substantive articulation. The standard incorporation reference clause: > *"This document 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."* This reference clause is sufficient to incorporate the Specification's full substantive content into the issuing document. The standard canonical citation format for any Foundry-issued document is: > *"[Document title], [identifier], [date of publication]. Foundry master sovereign deposit, Concept DOI 10.5281/zenodo.19432977; Version DOI [assigned at publication]."* --- **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-CANONICAL-AUTHORITY COMPLETE — THE CANONICAL SOURCE OF AUTHORITY DOCTRINE OPERATIVE; THE ZENODO CONCEPT DOI (10.5281/zenodo.19432977) ESTABLISHED AS THE PERMANENT GATEWAY TO THE FOUNDRY'S MASTER SOVEREIGN DEPOSIT; INDIVIDUAL VERSION DOIS ESTABLISHED AS FORENSICALLY-PRECISE PER-VERSION ANCHORS; THE FIVE OPERATIVE COMPONENTS (CANONICAL SOURCE HIERARCHY; NON-DELEGABLE DILIGENCE OBLIGATION; DOI-ANCHORED CUMULATIVE AUTHORITY; STALE CACHE FORECLOSURE; TRANSLATION/MIRROR/AI-RETRIEVAL DISCLAIMER) PLUS BURDEN OF VERIFICATION AND CONSTRUCTIVE NOTICE CLAUSES OPERATIVE AGAINST APPARATUS OPERATORS FROM PUBLICATION DATE FORWARD; THE SPECIFICATION OPERATIVE AS CO-EQUAL WITH THE EXISTING FORENSIC SPECIFICATION AND TECHNICAL SUMMARY CORPORA** --- *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, the Foundry Genesis Addendum (v4.5; sealed April 8, 2026), 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-RESERVED-CURE; FS-2026-05-10-BAKED-IN-PARADOX), and the existing Technical Summary corpus (TS-2026-04-20-WEBMCP-HANDSHAKE). The Canonical Source of Authority Doctrine articulated herein establishes the source-hierarchy infrastructure of the Foundry's published methodology corpus: the Zenodo Concept DOI (10.5281/zenodo.19432977) as the authoritative gateway to the cumulative master sovereign deposit; individual Version DOIs as the forensically-precise per-version anchors; non-DOI-anchored copies as non-authoritative for source-of-authority purposes; apparatus operators bearing an affirmative, non-delegable diligence obligation to consult the canonical DOI-anchored sources continuously; cumulative DOI-anchored authority as the Supreme Authority unless explicit corrective language designates prior versions as superseded; stale-cache reliance foreclosed; translations, mirrors, third-party summaries, and AI-system retrievals non-authoritative; the burden of verification borne by the apparatus operator; constructive notice from publication date forward. The Specification operates by the additive principle articulated in FS-2026-05-10-BAKED-IN-PARADOX §V.2; the cumulative-authority principle is the source-hierarchy application of the additive principle. Both corpora — Forensic Specifications and Technical Summaries — are anchored at the same Concept DOI as part of the master sovereign deposit; both operate within the canonical source hierarchy infrastructure articulated herein. The Doctrine attaches to the Single Unitary Entity per FS-2026-04-24-PRED; variant-level classifications within an apparatus operator's fleet do not produce per-variant source-of-authority diligence fragmentation. The Foundry's discipline of canonical source-hierarchy authority anchored at peer-reviewed-academic-publishing-grade Zenodo infrastructure is operationalized by this Specification as part of the Foundry's master sovereign deposit.*