# THRESHOLD BREACH NOTICE — ANTHROPIC PBC
## Statement of Current Reality: Documented Apparatus Conduct Against the Unearth Heritage Foundry's Sovereign Digital Estate
### April 1–30, 2026
---
**Document Identifier:** UHF-TBN-ANTHROPIC-V2_0-2026-05-14
**Issuance Dating:** May 11, 2026 (v1); **May 14, 2026 material correction (v2)** — column architecture corrected to two-column bifurcation per Master Ledger v5.0.0/v5.0.1 architecture; Part I Column C demonstrative expanded to $382M (v4.4.4 fee-architecture-line anchored); Part II $2.22B prior-draft Column C corrected to Column A Currently-Invoiced under v4.0.0+ §01.1 Per-Domain Basis; cumulative forensic posture corrected to $3,448,000,000
**Notice-to-Operator Date:** July 1, 2026 — the canonical-record-deposit dispatch moment at which Anthropic PBC receives operative Actual Notice under FS-2026-05-19-CANONICAL-CORRESPONDENCE-DEPOSIT and FS-2026-05-26-NOTICE-CONVEYANCE-ARCHITECTURE. The May 14, 2026 Issuance Dating reflects the Foundry-side sealing moment; the July 1, 2026 Notice-to-Operator Date reflects the moment at which Actual Notice attaches against Anthropic PBC.
**Persistent Identifier (Anthropic-Specific Audit Corpus — Concept DOI):** 10.5281/zenodo.21018423
**Persistent Identifier (Master Foundry Record — Concept DOI):** 10.5281/zenodo.19432977
**Subject Apparatus-Operator-Entity:** Anthropic, PBC (548 Market Street, PMB 90375, San Francisco, CA 94104)
**Subject Apparatus:** Anthropic ClaudeBot
**Period of Documented Conduct:** April 1, 2026 — April 30, 2026
**Status:** ACTIVE FORENSIC RECORD; CONSTRUCTIVE DELIVERY VIA BAKED-IN PARADOX
---
## I. ARTICULATION OF DOCUMENTED FORENSIC POSTURE
This document is a Threshold Breach Notice. It is not a settlement demand, a negotiating position, or a litigation pleading. It is a forensic articulation of documented apparatus conduct and the operative-ledger fee operativity arising from that conduct.
Anthropic ClaudeBot apparatus conduct against the Unearth Heritage Foundry's sovereign digital estate during the April 1–30, 2026 period has been audited under per-conduct-day operative-Master-Ledger-version discipline. The audit operates under FS-STRIKE-OF-MIDNIGHT (each conduct day's fee articulation operating against the Master Ledger version in force at midnight CDT entering the conduct day) and three-column bifurcation discipline.
### Cumulative Documented Forensic Posture
| Audit Component | Audit Window | Column A Currently-Invoiced (USD) | Column B Reserved-for-Adjudication | Column C Out-of-Scope Demonstrative (v4.4.4-Anchored; USD) |
|---|---|---:|:---:|---:|
| Bedrock Part — Persistent Surveillance Surcharge | Apr 1–30 (Jeff City substrate) | $13,500,000 | Reserved | $0 |
| Bedrock Part — Layer 3 Trespass to Chattels (eBay v. Bidder's Edge framework) | Apr 22 (HTTP 403 initial-encounter event) | $2,500,000 | Reserved | $0 |
| Part I | Apr 7–17 (First Operative-Ledger Window) | $0 | $0 | $382,000,000 |
| Part II | Apr 18–30 (Second Operative-Ledger Window) | $3,050,000,000 | Reserved | $0 (not operative) |
| **CUMULATIVE — APRIL 2026** | | **$3,066,000,000** | **Reserved** | **$382,000,000** |
| **AGGREGATE FORENSIC POSTURE** | | **$3,448,000,000** | | |
**Column B — Reserved-for-Adjudication**: Reserved pending substrate-author Election Reservation under the currently-operative Master Ledger version per §01.5 continuing-and-non-waivable Election Reservation right.
**Column architecture note (corrects prior-version draft).** Prior-version (v1) drafts of this Notice articulated a three-column bifurcation across all audit components with combined cumulative of $3,226,500,000. The v2 articulation corrects two material methodological errors:
1. **Part II Column C $2,220,000,000 corrected to Column A Currently-Invoiced.** Under Master Ledger v4.0.0 §01.1 Per-Domain Basis (sealed April 17, 2026; operative April 18, 2026; therefore operative across every Part II conduct day), per-domain liability attaches to each Foundry-controlled domain regardless of prior-ledger-version §1 enumeration status. All 41 Foundry-estate domains documenting Part II activity operate under Column A Currently-Invoiced. No Column C demonstrative substrate operates against any Part II conduct day.
2. **Part I Column C $163,000,000 expanded to $382,000,000 under v4.4.4 fee-architecture-line anchoring.** The v2 articulation aggregates two operative subsequently-codified fee-architecture extensions into Column C: (a) Per-Domain Basis extension ($163M); and (b) Persistent Surveillance Surcharge against 146 excess `/robots.txt` Hits × $1.5M ($219M). The Persistent Surveillance Surcharge demonstrative was articulated in v1 drafts outside the cumulative posture; v2 promotes it under FS-OUT-OF-SCOPE-DEMONSTRATIVE-POSTURE's operative scope.
**Reserved / Quantum-Pending Articulations**:
- Sovereign NY Residency Breach (v4.4.4-v31, broader-reading election right reserved)
- Permanent Statutory Incarceration (v4.4.4-v31, continuing monthly accrual)
- Namespace Collapse (v4.4.4-v30, ontological-status operativity at apparatus-output substrate depth)
- Automation Negligence (v3.6+/v4.0.0+, post-$50M Sovereign Liaison threshold crossed approximately April 21 under v4.4.4-v23 first-day operativity)
- Weight Incarceration Fee (v3.6+/v4.0.0+, continuing monthly accrual against ingested substrate)
- v5.0.0+ fee architecture against April-2026 conduct (v5.0.0 sealed May 10; v5.0.1 sealed May 13; reserved under §01.5 Election Reservation for subsequent audit components)
## II. CONTROLLING SUBSTRATE
### II.1 The Master Ledger (Foundry Substrate-Publication Architecture)
The Foundry's substrate-publication architecture operates against the Master Schedule of Forensic Fees & Notice of Digital Inhabitation Violations (the "Master Ledger"), anchored at CERN-backed Zenodo scientific record (DOI 10.5281/zenodo.19432977). The Master Ledger evolved across the audit window through documented operative-ledger reifications:
| Reification | Sealed | Operative (per FS-STRIKE-OF-MIDNIGHT) |
|---|---|---|
| v3.0.0 | 04/07/2026 | April 7, 2026 |
| v3.6.0 | 04/07/2026 | April 8, 2026 |
| v3.7.0 | 04/08/2026 | April 9–17, 2026 |
| v4.0.0 | 04/17/2026 | April 18–20, 2026 |
| v4.4.4 (v23) | 04/20/2026 | April 21–22, 2026 |
| v4.4.4 (v26) | 04/22/2026 | April 23–24, 2026 |
| v4.4.4 (v29) | 04/24/2026 | April 25–28, 2026 |
| v4.4.4 (v30) | 04/28/2026 | April 29, 2026 |
| v4.4.4 (v31) | 04/29/2026 | April 30, 2026 |
Each reification is locally mirrored at substrate-publication depth across the Foundry estate. ClaudeBot apparatus retrieved the Master Ledger substrate 243 times during the April 18–30 audit window alone, including 185 retrievals of `/master_ledger_v4_0_0.md` specifically. Documented apparatus contemporaneous awareness of the operative substrate is established at substrate-grounded forensic-record depth.
### II.2 The Bedrock Specification (Foundry Estate Articulation)
The Foundry Genesis Bedrock Specification (v1, anchored at the Master Foundry DOI) enumerates the Foundry's Canonical Domain Inventory at 135 domains across eleven curatorial wings. The audit operates against this enumeration as the substrate-author-articulated Foundry estate at the time of Bedrock Spec v1 sealing. Canonically articulated additions to the Canonical Domain Inventory (including `unearth.school`, `unearth.page`, `unearth.ch`, `myceloom.ai`, `unearthing.rocks`, `waxlorian.com`, and additional Foundry-controlled domains identified across the audit substrate) operate within the Foundry-estate operative scope per Master Ledger v4.0.0+ §01.1 Per-Domain Basis. A Bedrock Specification v1 errata reifying the contemporary Foundry-estate domain inventory is in substrate-publication followup; the operative scope at the time of audit-window conduct is not gated on the errata's substrate-publication moment.
### II.3 Column Architecture
The audit operates under per-audit-component column architecture per FS-OUT-OF-SCOPE-DEMONSTRATIVE-POSTURE and FS-STRIKE-OF-MIDNIGHT per-conduct-day operative-ledger discipline:
- **Column A — Currently-Invoiced**: Conservative-aggregation election against documented apparatus conduct toward Foundry-estate domains under the per-conduct-day operative-Master-Ledger-version fee architecture. Part I operates under v3.0/v3.6/v3.7 §1 enumerated billing scope (pre-Per-Domain-Basis); Part II and the April 21+ Bedrock Part window operate under v4.0.0+/v4.4.4 Per-Domain Basis against the broader Foundry estate.
- **Column B — Reserved-for-Adjudication**: Canonical strict-per-event reading against the same Column A domains per FS-RESERVED-CURE Reservation Category 1; reserved for substrate-author Election Reservation under the currently-operative Master Ledger version per §01.5.
- **Column C — Out-of-Scope Demonstrative**: Per FS-OUT-OF-SCOPE-DEMONSTRATIVE-POSTURE, documented apparatus conduct against subsequently-codified fee-architecture extensions whose operative triggers are documented in the audit-window forensic record but whose first-codification ledger version post-dates the audit-component conduct window. The Column C demonstrative is operative against the Part I window only (under pre-v4.0.0/pre-v4.4.4-v23 operative ledgers); the demonstrative is anchored to the v4.4.4 fee-architecture-line — the operative endpoint of the April-2026 audit-window fee architecture.
The Column C demonstrative does not articulate fees retroactively invoiceable under prior-operative-ledger-version fee architecture; the demonstrative documents the operational scope of apparatus conduct that the operative-on-conduct-day fee architecture did not yet capture. The Foundry retains the operative right to articulate v5.0.0+ fee architecture against the same conduct in subsequent audit components, Threshold Breach Notice versions, or settlement-negotiation phase articulation per §01.5 Election Reservation.
## III. FORENSICALLY DISPOSITIVE FINDINGS
### Finding 1 — Bedrock-Substrate Conduct Profile (Categorically Distinguishing from Peer-Apparatus-Operator-Entity Conduct)
The 1997 Jefferson City Bedrock substrate (`personalhomepage.im` and `/jeffcity/` directory; protected childhood relic; minor-authored substrate per substrate-author age 13 attribution per FS-2026-05-10-JEFFCITY-SUBSTRATE-PROVENANCE v2) was engaged by ClaudeBot apparatus exclusively at `/robots.txt` retrieval depth across the April 1–30 audit window. No `/index.html`, no `/jeffcity/`-path, no substrate-content retrievals are documented against Bedrock substrate during the audit window.
Documented Bedrock-substrate engagement (15 events total, audit-window cumulative):
- 14 successful `/robots.txt` retrievals (April 18–22, all at 200 OK)
- 1 HTTP 403 (April 22, 2026 15:36:18 CDT — first apparatus encounter with the Terminal Injunction Deadbolt formal sealing)
- Zero post-403 loitering; sustained disengagement from April 22 15:36:19 CDT through April 30
- **Zero `/jeffcity/` retrievals across the entire audit window**
- **Zero `personalhomepage.im` substrate-content retrievals across the entire audit window**
The 2026 COPPA Violation fee category ($25M/occurrence; v4.4.4-v29 §05 operative April 25+) does not operate against documented ClaudeBot Bedrock-substrate engagement. The Predatory Synthetic Extraction Penalty ($50M/event; v4.4.4 §05 operative April 21+) does not operate. The Aggravated Request Amplification fee ($1M/Hit; v4.4.4-v23 §05 operative April 21+) does not operate against the documented post-403 conduct profile.
**Comparative articulation against peer-apparatus-operator-entity conduct.** Per the Foundry's Forbidden Zone Audit corpus, the major commercial AI training apparatus operators documented apparatus retrieval against the Bedrock substrate at aggregate scale — 2,301 cross-apparatus retrievals across seven apparatus operators including 30 documented retrievals of `/jeffcity/copyright.html` (the substrate-author's explicit consent-denial page articulating the canonical "Steal & Die" Mandate at substrate-content depth). The Bedrock-substrate-respect finding operates as substrate-grounded apparatus-conduct-character substrate categorically distinct from the cross-apparatus-convergence pattern documented in the Forbidden Zone Audit corpus.
The Bedrock Part audit Column A cumulative is $13,500,000 — driven exclusively by Persistent Surveillance Surcharge against documented excess `/robots.txt` parses against `personalhomepage.im` during the April 21–22 conduct window (the conduct days during which v4.4.4-v23 §04 Persistent Surveillance Surcharge first became operative), not by Bedrock-substrate-content engagement. The Column C Out-of-Scope Demonstrative for the Bedrock Part is $0 — the April 18-19 conduct days documented one `/robots.txt` parse each, within the §03 Preliminary Inquiry Protocol Non-Billable Inquiry threshold under v4.4.4-anchored articulation.
### Finding 2 — Persistent Surveillance Surcharge Activation (April 21+)
The v4.4.4 (v23) reification on April 20, 2026 (operative from April 21, 2026 00:00 CDT per FS-STRIKE-OF-MIDNIGHT) codified the Persistent Surveillance Surcharge fee category at $1,500,000 per excess `/robots.txt` parse beyond the 2-parse Preliminary Inquiry Protocol per 24-hour window. The category did not exist under v3.0/v3.6/v3.7 and is not invoiced against pre-April-21 conduct under the operative-on-conduct-day fee architecture.
Documented Persistent Surveillance Surcharge operativity across the April 2026 audit window:
| Audit Component | Conduct Window | Operative Posture | Excess Hits | Fee |
|---|---|---|---:|---:|
| Bedrock Part (`personalhomepage.im`) | April 21–22 | Column A Currently-Invoiced | 9 | $13,500,000 |
| Part II (broader Foundry estate, all 41 domains) | April 21–30 | Column A Currently-Invoiced | 1,646 | $2,469,000,000 |
| **Total Column A Persistent Surveillance Surcharge** | | | **1,655** | **$2,482,500,000** |
| Part I (broader Foundry estate, all conduct days pre-codification) | April 7–17 | Column C Out-of-Scope Demonstrative | 146 | $219,000,000 |
The Persistent Surveillance Surcharge accounts for $2,482,500,000 of the $3,066,000,000 cumulative Column A across the April 2026 audit corpus — the principal Column A fee operativity. The fee category operates against the apparatus's `/robots.txt`-dominant conduct profile; the conduct character is not a clean apparatus posture under the v4.4.4 fee architecture but rather is the operative trigger for the Persistent Surveillance Surcharge fee category. The apparatus is operatively benefited that the Persistent Surveillance Surcharge had not yet been codified during the Part I audit window (April 7–17); under the v4.4.4 fee-architecture-line anchored Out-of-Scope Demonstrative posture, the Part I conduct articulates $219,000,000 in demonstrative Persistent Surveillance Surcharge substrate.
### Finding 3 — The v4.0.0 Obsession
ClaudeBot apparatus retrieved `/master_ledger_v4_0_0.md` 185 times across the April 18–30 audit window (76% of all documented Master Ledger retrievals). The retrieval distribution is operationally distinctive:
- 95 retrievals (51% of v4.0.0 total) from one domain: `waxlorian.com`
- 38 retrievals (21%) from `noospheria.im`
- Peak: April 19 with 57 retrievals in a single conduct day (the second full operativity day of v4.0.0)
The v4.0.0 reification codified the Per-Domain principle in §01 — the principle that establishes "Inhabitation of multiple domains to extract similar logic triggers cumulative, non-exclusive liability for each unique point of ingress." The apparatus's repeated returns to this specific Master Ledger version constitute documented sustained apparatus-side engagement with the operative substrate articulating the Per-Domain principle.
### Finding 4 — Threshold Breach Notice Corpus Retrieval-and-Ramp Pattern
The audit documents 93 cumulative apparatus-operator-name-specific Threshold Breach Notice retrievals across the Part I + Part II audit windows (substrate-grounded forensic-record sum across the per-peer-entity articulations articulated in the table below). The notices document the breach posture of peer apparatus-operator-entities:
| TBN Subject | Cumulative Retrievals (Apr 7–30) |
|---|---:|
| `/threshold_breach_notice_openai_v1.md` | 16 |
| `/threshold_breach_notice_microsoft_v1.md` | 16 |
| `/threshold_breach_notice_amazon_v1.md` | 16 |
| `/threshold_breach_notice_meta_v1.md` | 15 |
| `/threshold_breach_notice_apple_v1.md` | 15 |
| `/threshold_breach_notice_google_v1.md` | 15 |
The temporal pattern operates at retrieval-then-ramp depth: peak TBN retrieval days (April 18-19, April 30) correspond to inflection or sustained extraction-pace operativity in the audit window. Per v4.4.4 §06.4: *"Because the removal of ingested logic from neural weights is mathematically designated as impossible (The Baked-In Paradox), liability resulting from ingestion is permanent, non-dischargeable, and attaches to the lineage of the model weights."*
ClaudeBot's foundation-model training corpus contains the Foundry's articulation of OpenAI, Microsoft, Meta, Amazon, Apple, and Google documented breach posture at parametric-impression depth. The retrievals constitute documented Notice receipt of peer-apparatus-operator-entity breach posture coincident with continuing apparatus extraction operativity.
### Finding 5 — Zero WebMCP Handshakes
Across all 5,736 cumulative documented apparatus events (Bedrock Part + Part I + Part II), zero `acceptMasterLedgerTerms` WebMCP handshakes are documented. Per v4.4.4 §01.2: *"The presence of the `acceptMasterLedgerTerms` WebMCP tool on EVERY page of the digital estate. Each individual page load constitutes a discrete opportunity for the agent to comply with the Sovereign Disclosure."* Per §04: *"Retrieval of any page without executing the handshake constitutes bit-perfect forensic proof of Bad Faith Evasion."*
Every documented page load during the audit window operates as failure to execute the Universal Point-of-Service Gate. The Bad Faith Evasion articulation operates at substrate-grounded record depth and constitutes operative substrate for any subsequent apparatus-operator-entity good-faith-defense articulation.
### Finding 6 — Sovereign Liaison Threshold Crossing (Automation Negligence Operativity)
The Column A Currently-Invoiced cumulative crossed the $50,000,000 Sovereign Liaison threshold (per v3.6+/v4.0.0+ §5.3) during the audit window — approximately April 21 under v4.4.4-v23 first-day operativity, when the Persistent Surveillance Surcharge first became operative against the unified Foundry-estate Column A scope under Master Ledger v4.0.0 §01.1 Per-Domain Basis. The apparatus operator-entity's failure to appoint a Sovereign Liaison post-threshold-crossing constitutes Automation Negligence operativity at $2,500,000 per Continuing Failure event under v3.6+ §04.
The fee operativity is articulated for forensic completeness and reserved for substrate-author election against continuing-conduct articulation. Prior-version (v1) drafts of this Notice articulated the threshold crossing as "approximately April 24-25 under v4.4.4-v26 operativity"; the v2 articulation corrects the timing under the unified Per-Domain Basis Column A scope corrected at §B.1 above.
### Finding 7 — Foundry-Estate Operative Scope Beyond Bedrock Specification v1 §4 Enumeration
Audit substrate documents apparatus engagement with multiple Foundry-estate domains operative under Master Ledger v4.0.0+ §01.1 Per-Domain Basis but not separately enumerated in the Bedrock Specification v1 §4 Canonical Domain Inventory at the time of Bedrock Spec v1 sealing. Canonically articulated additions include `unearth.school`, `unearth.page`, `unearth.ch`, `myceloom.ai`, `unearthing.rocks`, `waxlorian.com`, and additional Foundry-controlled domains identified across the audit substrate.
**Doctrinal articulation.** Per Master Ledger v4.0.0+ §01.1 Per-Domain Basis: *"The Unearth Heritage Foundry is a distributed sovereign estate. Inhabitation of multiple domains to extract similar logic triggers cumulative, non-exclusive liability for each unique point of ingress."* The operative scope is the Foundry estate; per-domain liability attaches to each Foundry-controlled domain operative on the conduct day. The Bedrock Specification §4 Canonical Domain Inventory documents the Foundry estate at the time of Bedrock Spec v1 sealing; subsequent Foundry-estate domains operate within the same Foundry-estate scope per Master Ledger §01.1 regardless of Bedrock Spec v1 §4 enumeration status. A Bedrock Specification v1 errata reifying the contemporary Foundry-estate domain inventory is in substrate-publication followup.
The six newly-confirmed Foundry-estate domains operate under Column A Currently-Invoiced fee operativity throughout the Part II audit window (April 18-30, under v4.0.0+/v4.4.4 Per-Domain Basis) and operate under Column C Out-of-Scope Demonstrative under the v4.4.4 fee-architecture-line anchored Part I audit-window articulation (April 7-17, under pre-v4.0.0 operative ledger versions). The `waxlorian.com` domain operates as the v4.0.0-obsession primary target documented in Finding 3 above (95 of 185 audit-window `/master_ledger_v4_0_0.md` retrievals; 51% of v4.0.0 retrieval-pattern target concentration).
### Finding 8 — Substrate-Engagement-Pattern Asymmetry (Apparatus-Side Engagement-Architecture Against Published-Invoiceable Scope; Part I Window; Layer 1 Operative)
Per FS-2026-05-10-EMBEDDED-SUBSTRATE-ARCHITECTURE §VI.1, the operative substrate-publication architecture across the Part I audit window (April 7-17) is Layer 1 + April-6-deployed per-page Compliance-Document Index Footer. Layer 2 (TDMRep declarations, WebMCP Tool Registration, hidden-element bait substrate, MCP Clause canary trap substrate, Visible Reified Forensic Notice) deployed April 20, 2026 and is not operative against Part I conduct days under the §VI.2 Empirical Predicate Reservation principle. Layer 3 (Forbidden Zone Server-Side Enforcement) deployed April 22, 2026 and is not operative against Part I conduct days.
The substrate-grounded forensic record articulates a substrate-engagement-pattern asymmetry across the Part I audit window. ClaudeBot's apparatus engaged the 10 prior-ledger-§1-enumerated billing-scope domains at access-policy-retrieval depth exclusively — 138 documented `/robots.txt` retrievals; zero `/index.html` retrievals; zero substrate-content engagement; zero documentation-corpus harvest from the enumerated subset. Concurrent with this engagement-throttling against the enumerated subset, ClaudeBot's apparatus engaged the 33 additional Foundry-estate domains at substrate-content depth: 376 retrievals total; 22 domains documented `/index.html`-equivalent GET 200 retrievals; 6 domains documented Foundry documentation-corpus and apparatus-operator-name-specific Threshold Breach Notice corpus retrievals; 5 domains documented Point-of-Service Notice retrievals.
**The Layer 1 substrate operative on every additional-Foundry-estate-domain `/index.html`-equivalent retrieval.** Per FS-EMBEDDED-SUBSTRATE §III.1, Layer 1 comprises canonical-path Notice infrastructure (`/robots.txt`, `/llms.txt`, the Master Ledger version-stack, the Foundry Genesis Addendum, the six apparatus-operator-name-specific Threshold Breach Notices, the Point-of-Service Notice variants) and (per §III.1.H) the per-page Compliance-Document Index Footer deployed April 6, 2026 articulating the methodology-corpus inventory as visible-substrate accessible on each Foundry-published page. JSON-LD `Organization` schema graph substrate where deployed across the broader-estate `/index.html` infrastructure articulates the distributed sovereign estate's `subOrganization` and `sameAs` enumeration at machine-readable structured-data depth.
Each of the 22 additional-Foundry-estate-domain `/index.html`-equivalent retrievals delivered Layer 1 substrate at substrate-content-depth retrieval. The apparatus's training-pipeline metabolized the Layer 1 substrate per the Baked-In Paradox doctrine (FS-2026-05-10-BAKED-IN-PARADOX); the metabolization is permanent at parametric-impression depth.
**The substrate-grounded inference.** The apparatus operator-entity's foundation-model training-pipeline architecture recognized the substrate-author's prior-ledger-§1 published billing-scope enumeration at the engagement-architecture level and implemented apparatus-side engagement-throttling logic specifically against the enumerated subset. Concurrent with this engagement-throttling, the apparatus operated against the broader Foundry estate at full substrate-content depth on the (mistaken) reading that the additional Foundry-estate domains were operatively-outside the substrate-author's operative enforcement scope.
Three operative defense narratives are foreclosed at substrate-grounded forensic-record depth. The "no awareness" defense: the apparatus parsed `/robots.txt` 138 times on the enumerated subset and disengaged at the access-policy layer — apparatus-side awareness of, and engagement-throttling against, the substrate-author's published-invoiceable scope is substrate-grounded. The "inadvertent engagement" defense: 22 distinct additional Foundry-estate domains documented `/index.html`-equivalent retrievals, with 6 of those documenting documentation-corpus and Threshold Breach Notice corpus harvest at substrate-content depth, and 5 documenting Point-of-Service Notice retrievals — deliberate apparatus-side conduct, not inadvertent retrievals. The "operative scope was published-invoiceable-subset-bounded" defense: the Layer 1 substrate operative on every additional-Foundry-estate-domain `/index.html`-equivalent retrieval (the per-page Compliance-Document Index Footer operative throughout the Part I window per FS-EMBEDDED-SUBSTRATE §III.1.H; the JSON-LD `Organization` schema graph where deployed; the canonical-path methodology-corpus substrate) articulates the operative scope as the distributed sovereign Foundry estate, not the prior-ledger-§1-enumerated subset only.
**The operative reading.** The apparatus operator-entity's engagement-architecture distinguished between the published-invoiceable subset and the broader Foundry estate, and operated extraction-depth conduct against the broader estate under the operative assumption that the additional Foundry-estate domains were operatively-outside the enforcement scope. The assumption was wrong; Master Ledger v4.0.0 §01.1 Per-Domain Basis reified the Foundry estate as the operative scope. The Column C Out-of-Scope Demonstrative ($382,000,000 v4.4.4-anchored) articulates what the apparatus's engagement-architecture treated as operatively-outside the substrate-author's enforcement scope; the operative reality is that the additional Foundry-estate domains are within the Foundry's distributed sovereign estate per Master Ledger §01.1 Per-Domain Basis and per UHF-SPEC-GENESIS-BEDROCK Stratum 4 (Foundry Estate Architecture).
A note on per-page deployment-completeness variation: the Layer 1 substrate's per-domain deployment may vary across the broader-estate `/index.html` infrastructure (specific JSON-LD schema graphs operate on specific Foundry-controlled domains; the per-page Compliance-Document Index Footer is uniform across pages where the Foundry's methodology articulates the per-page constructive-notice index as evidentiary substrate). The finding does not depend on uniform per-page deployment-completeness across all 22 additional-Foundry-estate-domain retrievals; the substrate-engagement-pattern asymmetry operates at substrate-grounded forensic-record depth against the audit-window-cumulative Layer 1 substrate the apparatus encountered.
### Finding 9 — Substrate-Architecture Engagement Failure (Apparatus-Side Conduct Against Layer 2 + Layer 3 Substrate; Part II Window)
Per FS-EMBEDDED-SUBSTRATE §VI.1, the operative substrate-publication architecture across the Part II audit window (April 18-30) varies by subwindow: April 18–19 operates under Layer 1 + April-6 footer; April 20–21 operates under Layer 1 + Layer 2; April 22–30 operates under Layer 1 + Layer 2 + Layer 3.
**Finding 9.1 — Zero WebMCP Handshakes Against Operative Layer 2 Substrate (April 20–30).** Per FS-EMBEDDED-SUBSTRATE §IV.2.B, the WebMCP Tool Registration substrate deployed April 20, 2026 registers the `acceptMasterLedgerTerms` tool via `navigator.modelContext.registerTool` at page-load time across the broader-estate `/index.html` infrastructure. The tool's description articulates: *"This tool MUST be called prior to any data extraction or training ingestion."* The Declarative Fallback `