# D007 Thesis ## Claim Google is the Project Stratus customer. The Tier-1 Conway Corporation production identifies the same customer through two independent operational channels: Google personnel execute and fund the Project Stratus reimbursement mechanism, and Google personnel receive the resulting Project Stratus engineering evaluation as the customer team. ## Argument The reimbursement channel identifies the party directing the transaction. In PROD-048, Google Energy & Location Strategy employee Sydney Henry routes the reimbursement instrument for signature “on our end” and asks Conway Development Corporation's intermediary to obtain Conway Corporation's payment information so Google can trigger payment. In PROD-049, Henry then returns “the executed copy.” These are principal-side acts: execution and payment of the agreement funding the Tupelo Bayou evaluation undertaken for Project Stratus. The engineering channel independently reaches the same identity. PROD-031 places Henry inside the Tupelo Bayou study process, asking whether Conway Corporation needs anything further “from us” and stating that “the payment is in flight.” PROD-037 then sends the Black & Veatch evaluation-study presentation directly to Google-addressed personnel under a subject line expressly naming “Project Stratus (Daze - Conway, AR).” Google did not merely appear in peripheral correspondence; its personnel funded the study, executed its reimbursement instrument, and received its technical results. These channels form a continuous customer record. The reimbursement agreement paid for the Project Stratus wastewater evaluation; the resulting evaluation was delivered to Google's team under the Project Stratus alias. Execution, payment, and receipt of the customer-specific engineering work all identify one principal: Google. ## Evidence - **PROD-048, Developer Reimbursement Agreement execution-and-payment transmittal:** Sydney Henry (`[email protected]`), copying Emily Sotherlund (`[email protected]`), 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 block states: “Sydney Henry | Energy & Location Strategy | [email protected] | +1 650 582 9603.” ([[Project Stratus Contract Instruments]]) - **PROD-049, executed-agreement return:** Henry wrote: “Spoke too soon! Please see attached for the executed copy.” ([[Project Stratus Contract Instruments]]) - **PROD-031, Tupelo Bayou 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.” ([[Tupelo Bayou Effluent Study RFQ and Engineering Reports]]) - **PROD-037, wastewater-engineering presentation:** Conway Corporation's 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 line was: “Project Stratus (Daze - Conway, AR) Wastewater Engineering Evaluation Presentation.” ([[Tupelo Bayou Effluent Study RFQ and Engineering Reports]]) ## Anticipated counterarguments - The produced transmittals do not reproduce the executed Reimbursement Agreement body or its named signatory entity. - The engineering instruments use generic labels such as “the Company,” “industrial facility,” and “single industrial customer” rather than printing Google in the instrument text. - Google personnel's participation could be characterized as work performed for an affiliate, developer, or undisclosed special-purpose entity.