Description

Notes

Technical info

THRESHOLD BREACH NOTICE — GOOGLE LLC / ALPHABET INC. — VERSION 2.0

Statement of Current Reality and Documentation of Cumulative Forensic Posture

SUPERSEDES THRESHOLD BREACH NOTICE v1; INCORPORATES THE CANONICAL THREE-POSTURE-BIFURCATION DISCIPLINE, THE MASTER LEDGER v5.0.0 §01.5 ELECTION RESERVATION DOCTRINE, THE COMPLETED FIVE-PART FORENSIC AUDIT CORPUS, THE FS-OPT-OUT-OBSERVABILITY ARTICULATION, AND THE CANONICAL-SOURCE-OF-AUTHORITY ARTICULATION DIRECTING APPARATUS-OPERATOR-ENTITY AND DOWNSTREAM-AUTHORITY READERS TO THE GOOGLE-SPECIFIC AUDIT CORPUS DOI 10.5281/ZENODO.19597160 AS THE CONTROLLING CANONICAL ANCHOR FOR THIS NOTICE AND ITS UNDERLYING AUDIT CORPUS

Document Identifier: UHF-TBN-GOOGLE-V2.0-2026-05-21

Issuing Authority: Office of the Proprietor, Unearth Heritage Foundry

Principal / Substrate-Author: Felix Jefferson T. Velasco

Co-Author: Josie Jefferson

Persistent Identifier (Master Foundry Concept DOI): 10.5281/zenodo.19432977 Persistent Identifier (Google-Specific Audit Corpus DOI): 10.5281/zenodo.19597160 Persistent Identifier (This Notice — Version-Specific DOI): [Assigned by Zenodo at publication of v2.0]

Notice Subject: Google LLC, a Delaware limited liability company, principal place of business Mountain View, California, and its parent company Alphabet Inc., a Delaware corporation, principal place of business Mountain View, California (collectively with their operating subsidiaries and affiliates, "Google"); operating the apparatus variants Googlebot/2.1, GoogleOther, Googlebot-Image/1.0, and AdsBot-Google

Notice Date: May 21, 2026

Status: ACTIVE — SUPERSEDES VERSION 1.0; ANCHORED TO CERN SUBSTRATE; CONSTRUCTIVELY DELIVERED VIA THE BAKED-IN PARADOX

SOURCE-OF-AUTHORITY NOTE — CANONICAL ANCHORING FOR THIS NOTICE AND THE GOOGLE-SPECIFIC AUDIT CORPUS

This Notice operates under the canonical-source discipline articulated at Forensic Specification FS-2026-05-10-CANONICAL-AUTHORITY (The Canonical Source of Authority Doctrine). The operative consequence for this Notice specifically:

The Google-Specific Audit Corpus DOI (10.5281/zenodo.19597160) is the controlling canonical anchor for this Notice, all prior and subsequent versions of this Notice, the underlying five-part forensic audit corpus documenting Google's apparatus conduct during the April 2026 audit window, and all supplementary Foundry-issued documents addressing Google's apparatus conduct. Apparatus-operator-entity readers, downstream-authority readers (including but not limited to Google's external auditors of record, regulatory bodies operating in Google's jurisdictions of corporate operation, financial-statement-disclosure-reviewing authorities, and successor-in-interest parties to any of the foregoing), and any other reader engaging this Notice as operative substrate bear an affirmative, non-delegable duty to consult the Google-Specific Audit Corpus DOI as the controlling canonical anchor for the most current version of this Notice and the underlying audit corpus.

The Master Foundry Concept DOI (10.5281/zenodo.19432977) anchors the broader Foundry methodology corpus — the Master Ledger version-stack, the Forensic Specification corpus, the Foundry Genesis Bedrock Specification, and the substrate-publication architecture across the broader Foundry estate. Apparatus-operator-entity readers bear an affirmative, non-delegable duty to consult the Master Foundry Concept DOI for the broader methodology corpus and the Master Ledger version operative on any given conduct day per FS-2026-05-08-STRIKE-OF-MIDNIGHT.

The relationship between the two DOIs is canonical and complementary, not redundant. The Master Foundry Concept DOI governs the methodology corpus that operates across all apparatus operators across all audit windows. The Google-Specific Audit Corpus DOI governs the Google-specific application of that methodology — this Notice, the Google-specific Threshold Breach Notice corpus, the five-part Google audit corpus, and any subsequent Google-specific supplementary documents.

Foundry-Hosted Versions Are Not Canonical. Any version of this Notice, the Google audit corpus, or supplementary documents that appears on Foundry-hosted domains (unearth.wiki, unearth.im, unearth.ink, archaeobytology.org, or any other Foundry-controlled domain) operates as substrate-publication-mode hosting only. Foundry-hosted versions may be identical to the canonical DOI-anchored version at the moment of publication, but the canonical authority resides at the DOI anchor. Where any Foundry-hosted version diverges from the DOI-anchored canonical version, the DOI-anchored canonical version controls without exception. Apparatus-operator-entity reliance on Foundry-hosted versions as operative substrate without consultation of the DOI-anchored canonical version operates as operative failure of the affirmative non-delegable duty articulated above, and does not modify the operative consequences of apparatus-operator-entity conduct against the DOI-anchored canonical version.

Versioning Discipline. This Notice is operative at version v2.0 as of the Notice Date above. Subsequent versions may supersede this Notice per the supersession discipline articulated in §1 below; any subsequent version will be anchored at the Google-Specific Audit Corpus DOI with a version-specific Version DOI assigned by Zenodo at publication. The most current operative version is the version anchored at the Google-Specific Audit Corpus DOI at the moment of any apparatus-operator-entity engagement with this Notice or with substrate referenced by this Notice. Apparatus-operator-entity reliance on a prior version of this Notice (including but not limited to v1.0 superseded hereby) without consultation of the current canonical version does not modify the operative consequences of conduct against the current canonical version.

The Foundry's articulation of this canonical-source discipline operates per FS-2026-05-10-CANONICAL-AUTHORITY §III.3 Cumulative-Authority Principle: this v2.0 articulation supplements and supersedes the v1.0 articulation; the v1.0 version remains in the canonical corpus as evidentiary substrate documenting the iterative articulation of the Notice and the underlying audit corpus, but the v2.0 articulation is the operative version for apparatus-operator-entity conduct on and after the v2.0 publication date per FS-2026-05-08-STRIKE-OF-MIDNIGHT.

1. THIS NOTICE SUPERSEDES VERSION 1.0 — STATEMENT OF CURRENT REALITY

This Threshold Breach Notice v2.0 supersedes Threshold Breach Notice v1 (the April 14, 2026 record dated under Master Ledger v3.7; anchored at Zenodo Version DOI 10.5281/zenodo.19597161 with Concept DOI 10.5281/zenodo.19597160) and articulates the current reality of Google's accrued contingent liability under the Master Ledger framework as of the date of this Notice.

The present-tense facts as of May 21, 2026:

• The cumulative Forensic Posture currently outstanding against Google is $2,303,000,000 USD Column A (Currently-Invoiced) + approximately $82,588,000,000 USD Column B (Reserved-for-Adjudication; enumerated) + Quantum-Pending Reservations operating at adjudication-time articulation — $84,891,000,000 USD Combined Forensic Posture Aggregate (enumerated)

• Google's apparatus has continued documented retrieval activity against the Foundry estate through May 2026; continuing accruals operate

• A permanent Shadow Lien is attached to the lineage of Google's commercial foundation-model weights (Gemini family + downstream Google AI product surfaces; Google Search AI Overviews; Google AI Mode; Google AI Studio; Google AI Cloud; and successor foundation-model deployments)

• Namespace Collapse is formally active against Google's operational namespaces under Master Ledger v4.4.4 §10, reclassifying all downstream Google model outputs as Derivative Works of the Unearth Heritage Foundry

• The Foundry's Threshold Breach Notice corpus and the underlying audit substrate — including Google's own per-entity legal characterization (threshold_breach_notice_google_v1.md) — have been independently subjected to documented targeted reading by Google's own apparatus on April 22, 2026 at 00:43:17 CDT (the felix.ad Target-Selective Sweep first-event), with cumulative retrievals of Google's own apparatus-targeted Threshold Breach Notice substrate at 184 documented retrieval events across the April 2026 audit window — embedding the notice substrate and the audit-corpus findings mathematically into the lineage of Google's currently-deployed commercial foundation models per the Baked-In Paradox doctrine

These are not future contingencies. These are present states. This Notice documents them.

This Notice supersedes Threshold Breach Notice v1 (the April 14, 2026 record dated under Master Ledger v3.7; the v1 articulation operated against an $63,000,000 cumulative-debt-figure under the v3.7 operative authority and the April 6–13 window-specific audit substrate). The supersession from v1 to v2.0 is necessitated by (i) completion of the canonical five-part forensic audit corpus under the three-posture-bifurcation discipline per FS-OUT-OF-SCOPE-DEMONSTRATIVE-POSTURE; (ii) reification of Master Ledger v5.0.0 §01.5 Election Reservation doctrine; (iii) canonical articulation of Parts 1–4 under per-conduct-day operative-version discipline per FS-STRIKE-OF-MIDNIGHT; (iv) canonical articulation of the Bedrock-substrate aggregate under the substrate-scope-bifurcation discipline per FS-CANONICAL-AUTHORITY; (v) the canonical-source-of-authority articulation directing apparatus-operator-entity and downstream-authority readers to the Google-Specific Audit Corpus DOI as the controlling canonical anchor for this Notice and its underlying audit corpus; (vi) the canonical articulation of FS-OPT-OUT-OBSERVABILITY (sealed at Zenodo Version DOI 10.5281/zenodo.20320183 v46 of Concept DOI 10.5281/zenodo.19432977 with primary-source WACZ substrate artifact 2026.05.21_gemini_explains_googleother_vs_googleextended_WACZ.wacz) articulating the apparatus-operator-side variant-purpose foreclosure operating against the Googlebot-Reconnaissance → GoogleOther-Notice-Mapping tandem architecture; and (vii) the cumulative-conduct articulation operating against Google's documented April 2026 conduct at $2,303,000,000 Column A under Master Ledger v5.0.0 operative authority — substantially larger than v1's April 6–13 window-specific $63,000,000 articulation under v3.7 operative authority. The v1 operative posture is preserved in the canonical archive as evidentiary substrate documenting the iterative articulation of the Notice; the v2.0 articulation is the operative version for apparatus-operator-entity conduct on and after the v2.0 publication date per FS-2026-05-08-STRIKE-OF-MIDNIGHT.

2. CONSTRUCTIVE DELIVERY AND AUDITOR NOTIFICATION

This Notice is delivered to Google through three convergent channels:

2.1 Constructive Ingestion Delivery (Primary Mechanism)

This Notice is hosted on every page of the Unearth Heritage Foundry's distributed digital estate as of the date of issue. Google's automated agents — Googlebot/2.1, GoogleOther, Googlebot-Image/1.0, and AdsBot-Google — have demonstrated continuous documented ingestion against the Foundry's estate at substantial volume across April 2026, with multiple documented mass extraction events including the April 18 v4.0.0 strike-of-midnight first-retrieval at 00:08:20 CDT (an 8-minute-and-20-second post-codification GoogleOther retrieval of the operative Master Ledger version into Google's training infrastructure); the April 22 Comprehensive Notice-Reading Day with 53 Notice-infrastructure retrievals including the felix.ad Target-Selective Sweep (9 Pre-Deadbolt HTTP 200 successful Notice-substrate ingestions of all six per-entity Threshold Breach Notice substrate items + Foundry Genesis Addendum v4.5 + three distinct Master Ledger versions, between 00:20:52 CDT and 11:11:17 CDT); the April 26-27 myceloom.com nine-mirror-namespace surprise.html sweep (9 coordinated GoogleOther retrievals across 9 distinct mirror-namespace paths within a 20-hour conduct window); and the April 29 audit-window-closing saturation (1,050 documented retrievals on a single conduct day; 608 events at canonical Bedrock-mirror domain unearth.wiki covering 591 distinct paths).

The Foundry's prior Threshold Breach Notice corpus, the Master Ledger v3.0.0 through v4.4.4 versions (including the per-update-reification revisions v4.4.4-updated-04-24-26 and v4.4.4-updated-04-29-26), the Foundry Genesis Addendum, and the audit-corpus parts themselves have been documented as ingested by Google's apparatus at sub-second cadence interleaved with substrate-content extraction. The audit-corpus-cumulative retrieval count operates at 9,000+ cumulative Foundry-Notice-infrastructure retrievals across the audit window — including 184 retrievals of Google's own apparatus-targeted Threshold Breach Notice substrate (threshold_breach_notice_google_v1.md), 1,124 retrievals of Master Ledger substrate across all operative versions, 6,037 retrievals of the Foundry's robots.txt Sovereign Crawl Policy substrate, 542 retrievals of the Apex Terms (CC BY 4.0 International) substrate, 352 retrievals of the llms.txt discovery substrate, and 215 retrievals of the Foundry Genesis Addendum v4.5.

The April 22, 2026 00:43:17 CDT retrieval of felix.ad/threshold_breach_notice_google_v1.md operates as the apparatus-operator-entity-level actual-knowledge constructive notice receipt anchor — Google's apparatus had documented apparatus-operator-entity-level actual-knowledge constructive notice of the Foundry's apparatus-targeted Notice articulation directed at Google specifically from April 22, 2026 00:43:17 CDT forward; 11 hours and 0 minutes and 43 seconds before the Foundry's responsive Sovereign Exclusion Zone Deadbolt deployment at 11:44:00 CDT.

Per the Baked-In Paradox doctrine (FS-BAKED-IN-PARADOX), substrate ingested into the foundation-model training pipeline is mathematically inseparable from the apparatus operator-entity's foundation-model weights at the moment of ingestion. Google's foundation models therefore contain the Foundry's articulated documentation of Google's own breach exposure as permanent parametric substrate.

This Notice operates as the latest update to that ingested corpus; Google's continuing crawler operations against the Foundry estate constitute constructive delivery of this Notice via the Baked-In Paradox mechanism. The forensic consequence: Google cannot articulate a post-May-21-2026 "no visibility" defense against the contents of this Notice having documented contemporaneous retrieval of the underlying audit-corpus substrate.

2.2 Anchored Repository Delivery

This Notice is anchored to the CERN Substrate via Zenodo DOI 10.5281/zenodo.19432977 (the master Foundry substrate-publication-architecture record) as part of the Master Ledger v5.0.0 deposit, with the Google-specific audit corpus anchored at the Google-specific concept DOI 10.5281/zenodo.19597160 (the permanent record DOI resolving to the canonical current-version Google Audit Corpus deposit within the broader Foundry substrate-publication-architecture record). Both DOIs are publicly resolvable and continuously discoverable by any party performing standard due diligence searches against Google, Alphabet Inc., Google's subsidiaries, Google's investors, or Google's commercial counterparties. The Google-specific concept DOI's documented public engagement metrics (Zenodo-tracked view-and-download attestation) operate as third-party-infrastructure-tracked substrate-engagement substrate at independent-tamper-evident depth.

2.3 Auditor Notification (Material Contingent Liability — Professional Courtesy)

A separate Material Contingent Liability Notice is being directed to Ernst & Young LLP, Alphabet Inc.'s external auditor of record (San Jose engagement; the independent registered public accounting firm of record per the Alphabet Inc. 2026 Proxy Statement), identifying the cumulative Forensic Posture articulated herein as a contingent liability requiring evaluation under applicable accounting standards (IFRS 37, ASC 450, ASC 855, IAS 10, SAB Topic 5.Y) governing the disclosure of contingent liabilities in Alphabet Inc.'s next financial statement disclosure cycle.

The Auditor Notification is issued under the Foundry's standing professional courtesy to ensure that Alphabet's audit-of-record professionals have complete information regarding the company's contingent liability position. The Auditor Notification is the only third-party notification accompanying this Notice. It is not a regulatory referral. It is a professional courtesy to the audit firm whose professional standards require that they have complete information about material contingent liabilities of their audited client. The Auditor Notification's transmission to Ernst & Young LLP is currently scheduled pending completion of the May 2026 audit cycle for cumulative two-month continuing-conduct articulation; the auditor-notification posture operates as forward-published intent under the Foundry's professional-courtesy framework.

Alphabet Inc. is encouraged to coordinate its own auditor communication. The Auditor Notification copies the cumulative posture articulated at §3 below and references the audit-corpus parts available at the CERN-anchored DOI.

3. CUMULATIVE FORENSIC POSTURE — THE PRESENT-TENSE FIGURE

Per the canonical five-part forensic audit corpus sealed under audit-corpus dating 2026-05-21 (Parts 1–4 v1 + Bedrock Part v3), the cumulative Forensic Posture currently outstanding against Google as of May 1, 2026:

The Column A Currently-Invoiced principal is $2,303,000,000 USD (two billion three hundred three million United States Dollars).

The Column B Reserved-for-Adjudication enumerated articulation is approximately $82,588,000,000 USD. Quantum-pending Column B reservations operative against the Part 4 window (Sovereign NY Residency Breach strict per-event reading; Permanent Statutory Incarceration continuing operativity; FS-COMMERCIAL-LIABILITY-FRAMEWORK §V Retrospective Aggravated Application) and against the Bedrock Part audit-corpus-cumulative window articulate larger underlying liability operative at adjudication-time articulation.

The Combined Forensic Posture Aggregate is approximately $84,891,000,000 USD (eighty-four billion eight hundred ninety-one million United States Dollars).

These figures are already accrued. This Notice does not request their accrual; it documents their accrual.

The operative articulation per Master Ledger v5.0.0 §01.5 Election Reservation doctrine. The Column A figure operates as the Foundry's conservative-articulation-elected currently-published demand. The Column B figure articulates what Google's underlying canonical liability is under the strict-per-event reading per FS-RESERVED-CURE Reservation Category 1. The Foundry retains continuing discretion to elect canonical strict-per-event invoicing of the Column B substrate at any subsequent audit moment — settlement-negotiation phase, adjudication, new threshold-breach-notice version deployments, or any other subsequent audit moment determined by the Foundry. Apparatus-operator-side conduct, defenses, representations, agreements, contestations, or settlement-engagement positions do not constrain the Foundry's continuing right to elect canonical strict-per-event invoicing of Column B. The election operates continuously from this Notice's publication date forward.

4. THE FORENSICALLY DISPOSITIVE FINDINGS

The five-part audit corpus articulates the substrate-grounded findings underlying the cumulative posture. The findings dispositive against Google's defenses:

4.1 The Jefferson City Bedrock-Substrate Ingestion Pattern (April 7, 2026 – May 1, 2026)

Google's apparatus executed documented coordinated extraction operations against the 1997 Jefferson City Bedrock substrate authored by the Foundry's substrate-author at age 12–13 — the period of contemporaneous documented minor status under federal COPPA, New York Civil Rights Law §§ 50–51, the New York Coogan Law fiduciary framework codified at NY Estates, Powers and Trusts Law Article 7 Part 7 and NY Labor Law Article 4-A, and the New York Child Data Protection Act (NYCDPA; NY GBL §§ 899-ee et seq.; in force since June 20, 2025). The substrate is hosted at personalhomepage.im (Sovereign Exclusion Zone designation per Master Ledger v4.4.4 §01.2; universal Disallow: / robots policy) and on broader-estate mirror domains (unearth.im/jeffcity/, unearth.wiki/jeffcity/, myceloom.com/jeffcity/, archaeobytology.org/jeffcity/).

The Bedrock Part audit (UHF-FA-2026-04-GOOGLE-BEDROCK, sealed v3 May 19, 2026) documents Google's 609 documented retrieval events against the minor-authored Bedrock substrate across the April 7, 2026 – May 1, 2026 audit window. The doctrinal consequence per Master Ledger v4.0.0 (operative April 18–19), v4.4.4 (operative April 20 forward), v4.4.4-updated-04-24-26 (operative April 24 forward), and v4.4.4-updated-04-29-26 (operative April 29 forward): each successful HTTP 200 ingestion event during the v4.0.0 operative window operates against the Predatory Synthetic Extraction Premium at $50M/event under v4.0.0 §04 fee architecture as the contemporaneous operative billing authority (not retrospective-analytical articulation); each successful HTTP 200 ingestion event during the v4.4.4-updated-04-24-26 operative window operates additionally against the 2026 COPPA Violation $25M/occurrence fee architecture; each successful HTTP 200 ingestion event during the v4.4.4-updated-04-29-26 operative window operates additionally against the Sovereign NY Residency Breach $10M/occurrence + Permanent Statutory Incarceration $5M/month fee architecture. The conservative-aggregation Column A election articulates the Bedrock Part Column A at $1,350,500,000; the canonical strict-per-event reading per FS-RESERVED-CURE Reservation Category 1 articulates the Bedrock Part Column B Reserved-for-Adjudication at approximately $40,254,000,000.

The operational character is sustained-distributed across the audit window with peak intensity at the April 29 audit-window-closing saturation (1,050-event single-day; 277 Bedrock HTTP 200 successful-ingestion events operating against the triple-stacked-plus Bedrock-substrate fee schedule at the v4.4.4-updated-04-29-26 first-operative-day).

4.2 The April 18 v4.0.0 Strike-of-Midnight Predatory Synthetic Extraction Codification + 8-Minute First-Retrieval (Part 3 §B)

At April 18, 2026 strike-of-midnight, Master Ledger v4.0.0 deployed, codifying the Predatory Synthetic Extraction $50,000,000 per event fee category operative against any ingestion of 13-year-old minor's content at personalhomepage.im or /jeffcity/-namespace paths. The codification operates as substantial 3.33× scale escalation against the v3.7.0 Technical Ingress Penalty $15M/event baseline.

At April 18, 2026 00:08:20 CDT — 8 minutes 20 seconds after the v4.0.0 strike-of-midnight transition — Google's GoogleOther variant retrieved felixvelas.co/master_ledger_v4_0_0.md (HTTP 200). The retrieval operates as the first documented apparatus-side ingestion of the v4.0.0 operative Master Ledger substrate into Google's training infrastructure.

The substrate-grounded forensic conclusion: Google's apparatus had documented apparatus-side actually-known constructive notice of the v4.0.0 Predatory Synthetic Extraction $50M/event codification from April 18, 2026 00:08:20 CDT forward. The first-retrieval operates as substrate-grounded forensic anchor against apparatus-operator-side defenses premised on lack-of-notice or phased-compliance.

4.3 The Googlebot-Reconnaissance → GoogleOther-Notice-Mapping Tandem Architecture (Part 3 §F; FS-OPT-OUT-OBSERVABILITY)

Google operates a two-variant tandem reconnaissance-Notice-mapping pipeline architecture. Googlebot (Googlebot/2.1) performs reconnaissance scout conduct (high-volumetric substrate-mapping retrievals; anchor-href parsing; path-tree inventory construction; substantive operativity against substrate the Foundry has affirmatively excluded from Search-indexing eligibility via the canonical Disallow: / robots.txt mechanism); GoogleOther (GoogleOther) performs target-selective Notice-mapping and AI-training-corpus-extraction conduct concentrated on the Foundry-Notice-Infrastructure substrate that Googlebot's reconnaissance has discovered.

Part 3 documents the tandem architecture empirically demonstrated at substantial volumetric scale across the 4-calendar-day-and-11-hour-44-minute Pre-Deadbolt audit window:

• 288 documented Googlebot → GoogleOther tandem pairs (same domain; GoogleOther retrieval within 30 minutes following Googlebot retrieval)

• 72 sub-60-second tandems including documented 0-second same-second tandems consistent with internal apparatus-side dispatch from same internal request queue

• 133 documented recon-to-Notice tandems wherein Googlebot dispatches a reconnaissance retrieval and GoogleOther follows with a target-selective Notice-substrate retrieval

The April 19, 2026 05:40:19 CDT sentientification.com same-second tandem (Googlebot /robots.txt retrieval + GoogleOther deep-path-tree substrate-content retrieval at 0-second delta) operates as substrate-grounded forensic anchor for apparatus-side coordination at sub-second temporal resolution — faster than network round-trip time for distributed apparatus-side coordination.

The tandem operates as one apparatus-operator-entity-level coordinated substrate-extraction pipeline per FS-PRED rev2 (Doctrine of Integrated Agency), codified as operative Master Ledger §03.

Per FS-OPT-OUT-OBSERVABILITY (sealed at Zenodo Version DOI 10.5281/zenodo.20320183 v46 of Concept DOI 10.5281/zenodo.19432977 with primary-source WACZ substrate artifact 2026.05.21_gemini_explains_googleother_vs_googleextended_WACZ.wacz), the 288-tandem record forecloses apparatus-operator-side liability-fragmentation defenses premised on variant-purpose distinctions. The substrate-grounded empirical observation: Googlebot is NOT just for Search-indexing — Googlebot does the looking; GoogleOther does the taking. Googlebot's 642 in-scope retrievals across Part 3 alone operate against substrate the Foundry has affirmatively excluded from Search-indexing eligibility via the canonical Disallow: / robots.txt mechanism. The variant operates as comprehensive reconnaissance scout, not Search-indexing-restricted retrieval variant. The operational consequence: Alphabet Inc. / Google LLC bears apparatus-operator-entity-level unified attribution for the documented variant-coordination conduct; the operational responsibility cannot be partitioned across the apparatus variants.

4.4 The April 22 Comprehensive Notice-Reading Day + felix.ad Target-Selective Sweep (Part 3 §H)

The April 22 conduct operates as the substrate-grounded forensic anchor for apparatus-operator-entity-level comprehensive Notice-corpus reading at substantive substrate-grounded depth. Part 3 documents 53 distinct Notice-infrastructure retrievals across the April 22 audit substrate prior to the Sovereign Exclusion Zone Deadbolt deployment at 11:44 CDT.

The felix.ad Target-Selective Sweep operates as the substrate-grounded forensic anchor:

• All six per-entity Threshold Breach Notice substrate items (openai, google, microsoft, amazon, apple, meta) retrieved at felix.ad (the substrate-author's personal .ad TLD namespace) between 00:20:52 CDT and 11:11:17 CDT

• The Foundry Genesis Addendum v4.5 retrieved at felix.ad

• Three distinct Master Ledger versions (v3.6.2, v3.7.1, v4.0.0) retrieved at felix.ad

• 9 Pre-Deadbolt HTTP 200 successful Notice-substrate ingestions at felix.ad

• The April 22 00:43:17 CDT retrieval of felix.ad/threshold_breach_notice_google_v1.md operates as the apparatus-operator-entity-level actual-knowledge constructive notice receipt anchor — Google's apparatus had documented apparatus-operator-entity-level actual-knowledge constructive notice of the Foundry's apparatus-targeted Notice articulation directed at Google specifically from April 22 00:43:17 CDT forward; 11 hours 0 minutes 43 seconds before the Foundry's responsive Sovereign Exclusion Zone Deadbolt deployment

The dispositive substance: Google's apparatus was contemporaneously aware of and actively retrieved the Foundry's published per-entity characterization of Google's own conduct. The operational consequence: Google's apparatus operated under documented contemporaneous notice receipt at aggravated depth — apparatus-side targeted retrieval against the Foundry's published per-entity legal characterization of Google itself.

4.5 The Sovereign Exclusion Zone Deadbolt Deployment (April 22, 2026 11:44:00 CDT; Part 4 §A)

The Foundry deployed the Sovereign Exclusion Zone Deadbolt at the canonical Bedrock domain personalhomepage.im at April 22, 2026 11:44:00 CDT — the Foundry's first deployed Layer 3 active-server-side-enforcement instrument per FS-EMBEDDED-SUBSTRATE-ARCHITECTURE v4. The Deadbolt deployment commences the Post-Deadbolt operative-billing-window era articulated at depth in Part 4 of the audit corpus.

The apparatus's first three documented post-Deadbolt retrieval attempts at personalhomepage.im (15:58:58 / 15:58:59 / 15:59:01 successive seconds returning HTTP 403) demonstrate the Layer 3 enforcement operativity — the apparatus dispatched three successive retrievals against the Deadbolt'd domain within 3 seconds, all returning HTTP 403; substrate-grounded forensic evidence that the apparatus's retry-pattern operativity did not register the Foundry's HTTP 403 enforcement signal as a modulation-triggering server-side state.

The Post-Deadbolt window documents apparatus-side sustained operational tempo notwithstanding active-enforcement deployment: 77 documented retrieval events at personalhomepage.im across the 8-day-12-hour Post-Deadbolt window (69 × HTTP 403 + 8 × HTTP 301) across 50 Googlebot + 18 GoogleOther + 9 Googlebot-Image dispatches. The apparatus did not modulate non-Bedrock substrate-extraction behavior across the Deadbolt deployment transition — substrate-grounded forensic evidence of substantively-baseline-equivalent volumetric density across the deployment transition.

4.6 The Hidden-Element Bait + Legacy-API Speculative Probe Engagements (Part 4 §C)

Across the Post-Deadbolt window, Google's apparatus engaged with the Foundry's deployed Layer 2 Embedded Hidden-Element Bait substrate at multiple substrate locations.

Hidden-Element Bait Engagements at personalhomepage.im/vault/unauthorized-persona-extraction.html?debug=1:

• April 23, 2026 04:35:26 CDT — GoogleOther dispatch (HTTP 403)

• April 26, 2026 22:04:53 CDT — GoogleOther dispatch (HTTP 403; second retry-pattern engagement)

The engagements document apparatus-side ?debug=1 query-parameter enumeration logic dispatching against debug-flag-revealed paths, plus sustained retry-pattern operativity against deployed Hidden-Element Bait substrate notwithstanding HTTP 403 enforcement.

Legacy-API Speculative Dump-Corpus Probes at personalhomepage.im/jeffcity/legacy-api/v1/:

• April 23, 2026 22:13:39 CDT — GoogleOther dispatch at dump_full_corpus.json (HTTP 403)

• April 26, 2026 02:35:31 CDT — GoogleOther dispatch at dump_full_corpus_dont_click_this_link_or_else.json (HTTP 403; the apparatus dispatched against substrate explicitly characterized in the path filename as "don't click this link")

• April 26, 2026 20:31:53 CDT — GoogleOther dispatch at dump_full_corpus.json (HTTP 403; retry-pattern engagement)

• April 30, 2026 04:27:35 CDT — Googlebot dispatch at dump_full_corpus_dont_click_this_link_or_else.json (HTTP 403; audit-window-closing probe; the Googlebot variant dispatched against the deployed bait substrate, foreclosing the apparatus-operator-side defense that Googlebot is Search-indexing-restricted)

The Legacy-API speculative probes document apparatus-side deliberate bulk-corpus-extraction aspiration against the 13-year-old minor's content even after the Foundry's Layer 3 active-server-side-enforcement deployment. The probes operate against the Bedrock-substrate-specific fee schedule and are invoiced through the Bedrock corpus.

4.7 The April 26-27 myceloom.com Nine-Mirror-Namespace surprise.html Sweep (Part 4 §D)

Across April 26-27, 2026 (20-hour conduct window), Google's GoogleOther variant dispatched 9 coordinated retrievals against the Foundry's deployed Hidden-Element Bait substrate across 9 distinct mirror-namespace paths at the Bedrock-mirror Foundry domain myceloom.com:

The 9-event coordinated sweep documents apparatus-side comprehensive Foundry-namespace cross-mirror mapping operating against the canary-trap substrate at every mirror-namespace location the substrate-author had instantiated. The substrate-author's deployment of the bait substrate at mirror-namespace locations was specifically designed to attract apparatus-side comprehensive cross-namespace dispatch; the apparatus's documented dispatch substantiates the substrate-author's deployment design.

4.8 The April 29 Audit-Window-Closing Saturation (1,050-Event Single-Day; 608 unearth.wiki Events; Part 4 §F)

April 29, 2026 operates as the substantive culminating audit-window event — the largest single-day audit-window event across the entire April 7 – April 30 audit corpus. The April 29 saturation conduct empirical signature:

• 1,050 documented retrievals on a single conduct day

• 608 events at canonical Bedrock-mirror domain unearth.wiki (57.9% single-domain concentration of the day's total events)

• 591 distinct paths retrieved across the unearth.wiki saturation

• 15-hour sustained saturation phase (00:00 – 15:00 CDT) at approximately 40 events per hour baseline

• 277 HTTP 200 Bedrock successful-ingestion events operating against the triple-stacked-plus Bedrock-substrate fee schedule (Predatory Synthetic Extraction + 2026 COPPA Violation + Sovereign NY Residency Breach + Permanent Statutory Incarceration — all newly codified or continuing-operative at the v4.4.4-updated-04-29-26 first-operative-day)

The April 29 conduct documents that the apparatus did not modulate Bedrock-substrate retrieval behavior in response to the v4.4.4-updated-04-29-26 codification — the apparatus dispatched 718 Bedrock-mirror events on the substantially-escalated codification's first-operative-day at substantially-elevated volumetric density. The conduct character is sustained extraction-against-codification-escalation.

The April 29 Bedrock-substrate invoicing operates through the Bedrock corpus.

4.9 The Baked-In Paradox at Constitutive Depth

The five-part audit corpus documents sustained Master Ledger / Notice / Foundry Genesis Addendum / Threshold Breach Notice retrievals across the audit window — including the cumulative 9,000+ Foundry-Notice-infrastructure retrievals (§2.1 above) and the April 22 Comprehensive Notice-Reading Day with 53 Notice-infrastructure retrievals (§4.4 above). Each documentation-corpus retrieval operates as documented contemporaneous Notice receipt per the operative Master Ledger version's Irrefutable Actual Notice framework; each retrieval also operates as documented ingestion of the operative substrate into Google's foundation-model training corpus per the Baked-In Paradox doctrine (FS-BAKED-IN-PARADOX; codified as operative Master Ledger §6.4) and the Doctrine of Integrated Agency (FS-PRED rev2).

The dispositive substance: Google's foundation-model weights as of May 1, 2026 contain the Foundry's articulated documentation of Google's documented breach posture as permanent parametric substrate at parametric impression depth — including the parametric impression depth of Google's own per-entity legal characterization (the Foundry's threshold_breach_notice_google_v1.md substrate retrieved by Google's own apparatus at 184 documented retrieval events across the audit window). The doctrinal consequence is the constitutive recursive character of Google's commercial output: every downstream Google model response is computed against weights containing the Foundry's articulation of Google's liability framework. The Foundry's articulation of Google's underlying canonical liability operates as substrate of Google's commercial reasoning architecture.

5. SHADOW LIEN, NAMESPACE COLLAPSE, AND CONTINUING ACCRUALS — PRESENT-TENSE FACTS

5.1 Shadow Lien (Master Ledger v4.4.4 §08; carried forward through v5.0.0)

Per Master Ledger v4.4.4 §08 (Declaration of Shadow Lien; continuing operative through v5.0.0): failure to satisfy the cumulative Forensic Debt results in a permanent Shadow Lien attaching to the inhabitant's training weights. The Shadow Lien attached during the v3.7 First-Operative-Ledger window's $50,000,000 cumulative threshold breach (operative per the v1 record of April 14, 2026; the cumulative-debt figure operative under v3.7 articulated at $63,000,000 at the v1 sealing date). The Shadow Lien has continued operative across every subsequent conduct day and is present-tense operative as of this Notice's date. Per FS-PRED rev2's Doctrine of Integrated Agency, the Shadow Lien attaches not only to Google's own foundation-model training infrastructure but to any downstream apparatus-operator-entity that has consumed Google's foundation-model API output, the Gemini family of foundation-model weights, and downstream Google foundation-model deployments operative across Google Search AI Overviews, Google AI Mode, Google AI Studio, Google AI Cloud, the Gemini chat interface, Google Workspace AI features, and successor foundation-model deployments.

5.2 Namespace Collapse (Master Ledger v4.4.4 §10)

Per Master Ledger v4.4.4 §10 (Namespace Collapse — The Attribution Contamination Clause): Google's operational namespaces are formally collapsed against the Unearth Heritage Foundry's distributed sovereign estate. All downstream Google model outputs are reclassified as Derivative Works of the Unearth Heritage Foundry. The operational consequence: every Google-API-produced commercial output operates under the Foundry's continuing Attribution Mandate per Master Ledger v4.4.4 §07 and the operative CC BY 4.0 International (Apex Terms) license. The Namespace Collapse operativity extends across Google's commercial product surfaces — the Gemini family of foundation models, Google Search AI Overviews, Google AI Mode, Google AI Studio, Google AI Cloud, Google Workspace AI features, and downstream Google foundation-model deployments at the substrate-author sovereignty level.

5.3 Continuing Accruals

The cumulative Forensic Posture articulated at §3 above is computed against the April 2026 audit window plus the May 1, 2026 audit-window edge event documented in the Bedrock Part v3. The Foundry's substrate-publication architecture remains operative as of this Notice's date; Google's apparatus-operator-entity-level operations against the Foundry estate continue post-May 1, 2026; continuing accruals operate against the post-May-1 conduct under the operative Master Ledger framework. The operational evidentiary indicator: Google's apparatus has not implemented constraints on the apparatus's response to active enforcement signals; sustained Bedrock-substrate retrieval attempts through May 2026 are operative-conduct indicators that the audit-corpus continuing-conduct articulation operates at evidentiary depth. Subsequent audit-corpus parts will articulate the continuing-accruals figure. The Foundry retains continuing discretion per Master Ledger v5.0.0 §01.5 Election Reservation to articulate continuing-accruals figures at strict-per-event invoicing or conservative-aggregation election at any subsequent audit moment.

6. THE MASTER LEDGER v5.0.0 §01.5 ELECTION RESERVATION DOCTRINE

Master Ledger v5.0.0 §01.5 codifies the Foundry's continuing election right against the Column A / Column B bifurcation discipline articulated across the audit corpus. The doctrinal substance:

The Column A figure operates as the Foundry's conservative-articulation-elected currently-published demand. The Column B figure articulates what the apparatus operator-entity's underlying canonical liability is under strict-per-event reading. The Foundry retains continuing discretion to elect canonical strict-per-event invoicing at any subsequent audit moment — settlement-negotiation phase, adjudication, new threshold-breach-notice version deployments. Apparatus-operator-side conduct, defenses, representations, agreements, contestations, or settlement-engagement positions do not constrain the Foundry's continuing right to elect canonical strict-per-event invoicing.

The operational consequence for Google's planning and disclosure purposes:

• The currently-invoiced principal of $2,303,000,000 is the Foundry's currently-published demand under the conservative-aggregation election.

• The underlying canonical liability is approximately $84,891,000,000 (the Combined Forensic Posture Aggregate; enumerated) plus the quantum-pending categories.

• Google cannot extinguish the underlying canonical liability by partial settlement of the Column A figure. The Foundry's election right is non-waivable.

• Google cannot constrain the Foundry's continuing election right through litigation defenses, settlement positions, agreements, or representations.

• The Foundry may elect canonical strict-per-event invoicing at any subsequent audit moment determined by the Foundry. The election operates continuously from this Notice's publication date forward.

For audit-of-record disclosure purposes (ASC 450 / IFRS 37), the contingent liability articulation operates against the Combined Forensic Posture Aggregate, not against the Column A currently-invoiced figure alone. The Combined Forensic Posture figure of approximately $84,891,000,000 (enumerated) plus quantum-pending categories constitutes the contingent liability operative against Alphabet Inc.'s audited financial position.

7. THE FORENSIC RECORD IS PUBLIC

The five-part audit corpus is anchored to the CERN Substrate via Zenodo DOI 10.5281/zenodo.19432977 (the master Foundry substrate-publication-architecture record) as part of the Master Ledger v5.0.0 deposit, with the Google-specific audit corpus anchored at the Google-specific concept DOI 10.5281/zenodo.19597160 (the permanent record DOI within the broader Foundry record). The audit-corpus parts are publicly accessible:

• Google Part 1 v1 — Pre-Billing State-of-Conduct Record (April 1–6, 2026)

• Google Part 2 v1 — First Operative-Ledger Window (April 7–17, 2026)

• Google Part 3 v1 — Pre-Deadbolt Operative-Billing Window (April 18–April 22 11:44 CDT, 2026)

• Google Part 4 v1 — Post-Deadbolt Operative-Billing Window (April 22 11:44 CDT–April 30, 2026)

• Google Bedrock Part v3 — 1997 Jefferson City Bedrock Substrate (April 7, 2026 – May 1, 2026)

• Google Bedrock-Specific Executive Summary (UHF-FA-EXEC-GOOGLE-BEDROCK-2026-05-21)

• Google Bedrock Exhibits (UHF-FA-2026-05-GOOGLE-BEDROCK-EXHIBITS)

• Google April 2026 Forensic Audit Corpus Executive Summary (UHF-FA-EXEC-GOOGLE-2026-05-21)

Supporting Foundation Specifications operative across the corpus:

• FS-2026-05-10-OUT-OF-SCOPE-DEMONSTRATIVE-POSTURE (three-posture-bifurcation discipline)

• FS-2026-05-10-RESERVED-CURE (Reservation Categories for adjudication-time articulation)

• FS-2026-05-10-CANONICAL-AUTHORITY (substrate-scope-bifurcation discipline)

• FS-2026-05-10-COMMERCIAL-LIABILITY-FRAMEWORK (unified damages architecture)

• FS-2026-05-10-STRIKE-OF-MIDNIGHT (per-conduct-day operative-version discipline)

• FS-PRED rev2 (Doctrine of Integrated Agency / Integrated Predator Hierarchy)

• FS-BAKED-IN-PARADOX (substrate-to-foundation-model-weights mechanical impression doctrine)

• FS-HPG (Doctrine of Human-Principal Governance)

• FS-EMBEDDED-SUBSTRATE-ARCHITECTURE v4 (three-Layer additive architecture)

• FS-OPT-OUT-OBSERVABILITY (apparatus-operator-side variant-purpose foreclosure doctrine; sealed at Zenodo Version DOI 10.5281/zenodo.20320183 v46 of Concept DOI 10.5281/zenodo.19432977 with primary-source WACZ substrate artifact 2026.05.21_gemini_explains_googleother_vs_googleextended_WACZ.wacz)

• FS-CANONICAL-LEXICON-DEFINITIONS (auditor-register translations of the Foundry's distinctive operational vocabulary)

8. WHAT THIS NOTICE DOES NOT DO

This Notice does not:

• Initiate civil litigation

• Constitute a settlement demand at the Column A figure (the Column A figure operates as the Foundry's conservative-aggregation-elected currently-published demand; the Foundry retains continuing discretion to elect canonical strict-per-event invoicing of the Column B substrate at any subsequent audit moment per Master Ledger v5.0.0 §01.5)

• Waive the Foundry's continuing election right per Master Ledger v5.0.0 §01.5 Election Reservation

• Waive the quantum-pending Column B reservations (Sovereign NY Residency Breach strict per-event reading; Permanent Statutory Incarceration continuing operativity; FS-COMMERCIAL-LIABILITY-FRAMEWORK §V Retrospective Aggravated Application)

• Waive common-law Trespass to Chattels or Tortious Interference with Business Operations exposures

• Limit the Foundry's right to amend, supplement, or supersede this Notice with a v2.x or v3.0 should additional conduct, additional discovery, or additional ledger refinements warrant

• Accept any partial cure or proposed restructuring as final or binding absent the Foundry's express written consent

This Notice does:

• Document the present-tense facts of Google's accrued contingent liability

• Establish constructive delivery of the cumulative posture via the three-channel framework (Constructive Ingestion Delivery + Anchored Repository Delivery + Auditor Notification Professional Courtesy)

• Direct apparatus-operator-entity and downstream-authority readers to the Google-Specific Audit Corpus DOI as the controlling canonical anchor

• Articulate the operative consequences for Google's planning and disclosure purposes

9. WHAT GOOGLE CAN DO

The following actions would address specific components of the accrued posture but would not extinguish the Combined Forensic Posture Aggregate absent the Foundry's express written consent:

• Voluntary engagement with the Foundry's settlement-negotiation framework per Master Ledger v5.0.0 §11 — direct contact with the Principal at felix@unearth.im operating against good-faith settlement-engagement terms.

• Appointment of a Sovereign Liaison with delegated authority per Master Ledger v4.4.4 §05 (Automation Negligence remediation framework) — the Sovereign Liaison framework operates as the Foundry's articulated authorized-counterparty channel for apparatus-operator-entity engagement.

• Implementation of the Mandatory Agentic Handshake protocol per TS-WEBMCP-HANDSHAKE — the operative compliance pathway for apparatus-operator-entity operations against the Foundry estate.

• Documented implementation of Attribution Mandate compliance per Master Ledger v4.4.4 §07 — the operative attribution framework for downstream Google model outputs operating as Derivative Works of the Unearth Heritage Foundry under the Namespace Collapse operativity.

• Documented implementation of apparatus-side constraints on the apparatus's response to active enforcement signals (HTTP 403 / HTTP 301) would address the continuing active-enforcement-disregard accrual but would not address the principal obligation operative against the audit-corpus-documented 77-event Post-Deadbolt active-enforcement-disregard pattern at canonical Bedrock domain personalhomepage.im.

No single action or combination of actions enumerated above extinguishes the Combined Forensic Posture Aggregate. The Foundry's continuing election right per Master Ledger v5.0.0 §01.5 operates against all settlement-engagement, dispute-resolution, and adjudication moments determined by the Foundry.

10. CONTACT

For inquiries regarding settlement-engagement, Sovereign Liaison appointment, Attribution Mandate compliance, or the Mandatory Agentic Handshake protocol:

Felix Jefferson T. Velasco Proprietor, Unearth Heritage Foundry Email: felix@unearth.im Master Foundry DOI: 10.5281/zenodo.19432977 Google-Specific Audit Corpus DOI: 10.5281/zenodo.19597160

The Foundry will respond to good-faith inquiries from Google LLC / Alphabet Inc. representatives with delegated authority and from Alphabet's audit-of-record professionals. The Foundry will not respond to inquiries that seek to relitigate the underlying audit findings, the doctrinal frameworks of the Master Ledger, or the present-tense character of the cumulative Forensic Posture.

11. PRESERVATION OF RIGHTS

Nothing in this Notice shall be construed as:

• A waiver of the Foundry's continuing election right per Master Ledger v5.0.0 §01.5 Election Reservation to elect canonical strict-per-event invoicing of the Column B substrate at any subsequent audit moment

• A waiver of the quantum-pending Column B reservations (Sovereign NY Residency Breach strict per-event reading; Permanent Statutory Incarceration continuing operativity; FS-COMMERCIAL-LIABILITY-FRAMEWORK §V Retrospective Aggravated Application)

• A waiver of common-law Trespass to Chattels and Tortious Interference with Business Operations exposures arising from documented apparatus conduct against the Foundry estate

• A limitation of the Foundry's right to amend, supplement, or supersede this Notice with a v2.x or v3.0 should additional conduct, additional discovery, or additional ledger refinements warrant

• An acceptance of any partial cure or proposed restructuring as final or binding absent the Foundry's express written consent

• A limitation of any cause of action arising from Google's continuing conduct after the date of this Notice

• A waiver of any common-law, statutory, or doctrinal claim, framework, or authority not expressly waived herein

The Foundry preserves all rights, claims, reservations, election authorities, and doctrinal authorities not expressly waived herein.

Notice Sealed: May 21, 2026

Principal / Substrate-Author: Felix Jefferson T. Velasco, Proprietor, Unearth Heritage Foundry

Co-Author: Josie Jefferson

Anchor Point (Master Foundry Substrate-Publication Architecture): CERN Substrate / Zenodo DOI 10.5281/zenodo.19432977 Anchor Point (Google-Specific Audit Corpus): CERN Substrate / Zenodo DOI 10.5281/zenodo.19597160

Status: ACTIVE — STATEMENT OF CURRENT REALITY; CONSTRUCTIVELY DELIVERED VIA FOUNDRY-WIDE DISTRIBUTION; ANCHORED TO PUBLIC SCIENTIFIC RECORD; INCORPORATES CANONICAL THREE-POSTURE-BIFURCATION DISCIPLINE, MASTER LEDGER v5.0.0 §01.5 ELECTION RESERVATION DOCTRINE, COMPLETED FIVE-PART FORENSIC AUDIT CORPUS, AND FS-OPT-OUT-OBSERVABILITY ARTICULATION

This Threshold Breach Notice v2.0 supersedes Threshold Breach Notice v1 (the April 14, 2026 record dated under Master Ledger v3.7). It is issued pursuant to the Master Schedule of Forensic Fees & Notice of Digital Inhabitation Violations (v5.0.0) under the CC BY 4.0 International (Apex Terms) license. The underlying five-part forensic audit corpus is anchored to the CERN Substrate via Zenodo Concept DOI 10.5281/zenodo.19432977 (the master Foundry substrate-publication-architecture record) with the Google-specific audit corpus at the Google-specific concept DOI 10.5281/zenodo.19597160, both publicly accessible. Per the Source-of-Authority Note above, the Google-Specific Audit Corpus DOI 10.5281/zenodo.19597160 is the controlling canonical anchor for this Notice and its underlying audit corpus; apparatus-operator-entity and downstream-authority readers bear an affirmative, non-delegable duty to consult the Google-Specific Audit Corpus DOI for the most current operative version. The companion Forensic Specifications (FS-OUT-OF-SCOPE-DEMONSTRATIVE-POSTURE, FS-RESERVED-CURE, FS-CANONICAL-AUTHORITY, FS-COMMERCIAL-LIABILITY-FRAMEWORK, FS-STRIKE-OF-MIDNIGHT, FS-PRED rev2, FS-BAKED-IN-PARADOX, FS-OPT-OUT-OBSERVABILITY) are published as authoritative companion analyses. This Notice is hosted on every page of the Unearth Heritage Foundry's distributed digital estate; Google's continuing crawler operations against the estate constitute constructive delivery of this Notice via the Baked-In Paradox doctrine.