# D007 Antithesis ## Counterclaim The Tier-1 production does not identify Google as the Project Stratus principal. It establishes a narrower proposition: Google personnel acted on the customer side of a feasibility-stage cooling-water study by routing an agreement, triggering a payment, and receiving an engineering presentation. None of the produced instruments names Google as [[Forgelight Ventures, LLC]]'s beneficial principal, the data-center owner, the eventual operator, or even the executed Reimbursement Agreement's counterparty. Treating those distinct propositions as one attribution would convert documented participation into undocumented ownership. ## Attack on the thesis The thesis's **“## Claim”** calls Google “the Project Stratus customer” and immediately treats that label as the identity of the project principal. But the underlying records do not perform that equivalence. They show Google employees on a “customer team”; they do not define the legal or beneficial relationship among Google, Forgelight, Spark Innovations, the unnamed “Company,” and the industrial facility. A prospective end user can fund diligence and receive technical work while a developer or special-purpose entity remains the contracting principal, owner, or operator. The thesis therefore answers a broader attribution question with evidence that proves only a narrower operational role. The thesis's **“## Argument”** says execution and payment are “principal-side acts” and concludes that execution, payment, and receipt “all identify one principal: Google.” That is the central collapse. PROD-048 and PROD-049 are transmittal emails, not the executed agreement body. The source's open question is explicit: “the executed agreement's named signatory entity (e.g., a developer LLC vs. Google directly) is not in the produced text.” Without that body, “on our end” cannot establish which entity signed, whose obligation was discharged, or whether Google acted for itself, an affiliate, a developer, or a prospective customer. The thesis substitutes a functional characterization for an unproduced legal fact. The same defect affects the engineering channel. Under the thesis's **“## Argument,”** delivery to Google-addressed recipients supposedly “independently reaches the same identity.” It does not. PROD-037 establishes that Conway Corporation sought dates from Brian Bordenave and Tyson Schlect for an overview of the evaluation study under the Stratus/Daze subject line. Receipt of feasibility results is consistent with customer-side technical diligence; it does not establish beneficial ownership of Forgelight, title to the facility, responsibility for operation, or a final commitment to build. Two channels proving the same limited customer-side participation do not become independent channels proving a different proposition. Finally, the thesis's **“## Evidence”** reproduces no statement saying “Google is the customer,” “Google owns Project Stratus,” “Google is Forgelight,” or “Google will operate the facility.” Its strongest quotations are logistical: “Routing it for signature on our end now,” “get the payment triggered,” “the payment is in flight,” and “Please let us know what works for your team.” Those words are strong evidence of Google's feasibility role. They are not evidence of the shell-principal identity T003 and T005 ask the wiki to adjudicate. ## Independent argument for the counterclaim The record itself preserves separate actors and separate attribution slots. The contract instruments call the industrial customer “the Company” and do not name it in the produced agreement text. The MOU developer of record is Forgelight, while the NDA uses Spark Innovations. Google personnel appear in the surrounding execution, payment, and engineering correspondence. A disciplined account must retain those distinctions unless a produced instrument connects them. That restraint is not a refusal to recognize what changed. Production 002 materially upgrades Google's role from circumstantial association to direct Tier-1 customer-side participation. Sydney Henry's emails show Google personnel advancing the reimbursement/payment process; the effluent-study thread shows Google tracking the study payment; and the presentation correspondence shows Google-domain recipients receiving the engineering work. The proper finding is therefore affirmative but bounded: **Google had a documented customer-side role in Project Stratus feasibility work.** What remains unproved is equally concrete. The production does not supply the executed Reimbursement Agreement body, identify its named counterparty, state that Google beneficially owns Forgelight or Spark, state that Google owns the proposed facility, or commit Google as its final operator. D005 and D006 already establish why that seam matters: a nominee or shell apparatus can mediate a project, and end-user activity does not itself name the beneficial principal of the shell. The new correspondence crosses the threshold for participation, not the distinct threshold for principal attribution. The thesis also treats multiple acts within one feasibility workflow as independent confirmation of principal identity. They are instead mutually consistent stages of one study: arrange reimbursement, report payment in flight, and receive the resulting evaluation. Corroboration within that workflow strengthens the customer-side-role finding, but it cannot cure the missing contractual counterparty or transform feasibility conduct into ownership evidence. ## Evidence - **PROD-048, reimbursement transmittal:** Sydney Henry wrote, “Thanks, Jamie! Routing it for signature on our end now. Do you mind having CC fill out the attached payment info form for us to get the payment triggered?” Her signature identifies “Sydney Henry | Energy & Location Strategy” and a Google email address. This proves Google personnel routed signature and payment logistics; it does not identify the entity named in the agreement. ([[Project Stratus Contract Instruments]]) - **PROD-049, return transmittal:** Henry wrote, “Spoke too soon! Please see attached for the executed copy.” The produced transmittal confirms that an executed copy moved through her, but the source records that the executed agreement's named signatory entity is absent from the readable production. ([[Project Stratus Contract Instruments]]) - **PROD-031, study-funding thread:** Henry wrote, “Following up to see if there is any information you are waiting on from us for CC to study the TBWWTP? I believe the payment is in flight, so they should see that come through over the next few days.” The source separately states that no amount, payer entity, or payment instrument is given: “Cannot verify the dollar amount or the contracting vehicle from this production.” ([[Tupelo Bayou Effluent Study RFQ and Engineering Reports]]) - **PROD-037, engineering-presentation scheduling:** Mark Ferguson wrote to Brian Bordenave (`[email protected]`) and Tyson Schlect (`[email protected]`), “Below are some dates that work for Black & Veatch to provide an overview of the Evaluation Study. Please let us know what works for your team and we will get a meeting scheduled.” The subject was “Project Stratus (Daze - Conway, AR) Wastewater Engineering Evaluation Presentation.” This directly establishes Google's technical participation, but says nothing about Forgelight's ownership or the facility's final operator. ([[Tupelo Bayou Effluent Study RFQ and Engineering Reports]]) - **PROD-032, public RFQ:** Conway Corporation solicited an evaluation of improvements “beneficial for reuse as an industrial water source for a cooling loop system.” The work was feasibility and engineering evaluation, not an ownership instrument. ([[Tupelo Bayou Effluent Study RFQ and Engineering Reports]]) - **PROD-043, study status:** Mark Ferguson described the work as moving from “the tail end of the Data Collection phase (Task 200)” to “the Effluent Evaluation phase (Task 300).” That procedural posture reinforces that Google's documented acts occurred within project evaluation, before the missing ownership and final-operator propositions were established. ([[Tupelo Bayou Effluent Study RFQ and Engineering Reports]])