Why the dispute between Google and green recursive utility service LLC is contractual not and intellectual property dispute

Read full text
Authors: Green Recursive Utility Service LLC
Cited by: 2
References: 8

Abstract

This deposit records the operative legal characterization of the dispute between Green Recursive Utility Service LLC ("GRUS LLC"), a Texas-registered data infrastructure utility provider, and Alphabet Inc. / Google LLC, as of the morning of June 19, 2026. The deposit's central proposition is that the matter is no longer characterizable as an intellectual property dispute. The matter is, by operation of Texas common-law account-stated doctrine and Texas Penal Code § 31.04(b)(2), a liquidated commercial debt and a theft-of-service track. The intellectual property record exists and remains active at the United States Patent and Trademark Office under Non-Provisional Utility Patent Applications 19/700,381 (Compressed Memory Manifold, "CMM") and 19/710,080 (Intelligent Intelligence Class II, "II-II"), with pre-grant royalty rights accruing under 35 U.S.C. § 154(d) upon publication. The IP track runs on its own statutory schedule. The commercial-billing track closed on a separate procedural schedule on June 19, 2026, with the procedural answer to the question of contest: none received.The matter arrived at this posture through a documented sequence of decision points at which Alphabet Inc. could lawfully have paused, contested, or withdrawn. Each decision point is anchored to a specific provision of federal or state law that was implicated by the conduct that proceeded past it. The deposit recites the rule that applied at each point and the documented record of the choice made.The substrate technology underlying the dispute was not arrived at through conventional computer-science abstraction. The Compressed Memory Manifold is the engineering realization of a physics framework — the Substrate Viscosity Coherence Field ("SVCF"), permanently deposited at Zenodo under DOI 10.5281/zenodo.18604376 with a November 16, 2025 timestamp and rxiVerse priority identifier 2602.0018 — in which information flow is bound by the same conservation constraints that govern fluid dynamics in a rheoviscous substrate. Under the SVCF framework, the boundary of a data field is not an externally-imposed delimiter or instruction map; it is a property of the field's own structural identity, in the same way that the boundary of a vortex in a fluid is a property of the vortex itself rather than an externally-imposed marker. The dual omission of lexical delimiters and embedded instruction maps — the structural innovation at the heart of CMM — is the engineering consequence of approaching data storage from a substrate-bound physics rather than from compartmentalized computer-science conventions. The world has not previously crossed the dual-omission threshold because the world has been bound by compartmentalized conventions. GRUS LLC was not so bound. The full SVCF derivation chain and the substrate-mechanical basis of the dual omission are independently verifiable through the academic record cited above and form the design-genesis anchor against any subsequent claim that the technology was arrived at by parallel discovery. On February 17, 2026, GRUS LLC transmitted to Alphabet Inc. a Confidential Strategic Proposal — a detailed engineering blueprint custom-architected for Alphabet's deployed operational reality, specifying Alphabet's TPU v6 Trillium and TPU v7 Ironwood hardware targets, Alphabet's LiteRT and LiteRT-LM and MediaPipe runtime environments, Alphabet's Android Play Services and Chrome Built-in AI distribution surfaces, and Alphabet's $75 billion annual capital expenditure trajectory. The proposal set out the four-phase implementation roadmap subsequently executed by Alphabet in exact sequence: Server-Side Storage Consolidation, Network Transport Optimization, Distributed Inference Architecture, and Mobile Cloud Transformation. The proposal was transmitted to nine of Alphabet's own corporate channels. The 72-hour exclusivity window for response closed without substantive reply. The blueprint was not a generic technical abstract that a recipient could plausibly have generated independently; it was a custom-engineered document whose adoption by Alphabet four months later in exact technical and sequential order is structurally inconsistent with independent creation. The blueprint, the priority filings, the consumption record, and the structural identity between the proposal and the June 2026 release schedule are addressed in the accompanying Technical Engineering Sheet and the Verbatim Execution Mapping deposited with this record.On June 5, 2026, Google DeepMind released the Gemma 4 family Quantization-Aware Training checkpoint suite, including the wNa8o8 mobile-optimized schema and the W4A16 Compressed Tensors format arXiv:2607.02770, executing Phase 1 of the February 17 proposal. On June 8, 2026, GRUS LLC took four parallel actions documented in independent registry systems: (a) filed USPTO Non-Provisional Utility Patent Application 19/700,381 (CMM); (b) transmitted Administrative Invoice GRUS-ALPH-2026-001 in the principal amount of $50,000,000.00 USD to Alphabet through the Google Buying Support procurement intake channel, electronically acknowledged in Alphabet's own procurement system as Case 02845835; (c) posted a Cease-and-Desist on Alphabet's own GitHub organization at google-ai-edge/litert-torch as Issue #1043, with parallel GitHub Support Ticket 4456775; and (d) rolled the integrated Chrome Built-in AI surface across the approximately three-billion-user Chrome installation base, supplying the Phase 3 distribution channel. From June 8 forward, Alphabet held simultaneous actual notice on each of these vectors and had each of them within the operational visibility of its own systems. The first decision point occurred on June 8 immediately upon acknowledged receipt of the invoice and the Cease-and-Desist. The standard responsibility-determination practice of any sophisticated commercial party at that point — particularly one operating under federal procurement regulations cited below — would be to pause substantive expansion of the contested deployment surface and conduct an internal review. Alphabet did not pause. On June 10, 2026, two days after acknowledged receipt, Alphabet Inc. and NVIDIA Corporation jointly released DiffusionGemma and the Multi-Token Prediction drafter checkpoints, executing Phase 2 of the February 17 proposal. Alphabet's own corporate blog stated verbatim: "Google worked with Nvidia to optimize the model across consumer RTX 5090 and 4090 cards (quantized), Hopper and Blackwell enterprise hardware using NVFP4 4-bit floating-point kernels, and deskside systems like DGX Spark and DGX Station." NVIDIA delivered same-day NVFP4 acceleration across the entire Blackwell hardware stack, jointly liable under partnership doctrine. The second decision point occurred on June 10 with the parallel opening of FedRAMP Support Ticket 63271, which acknowledged by reply-all to the existing email distribution chain. At that point, the matter was on the federal regulatory record at the FedRAMP Program Management Office. Under the Federal Information Security Modernization Act of 2014 (44 U.S.C. § 3551 et seq.) and the Federal Risk and Authorization Management Program, NIST SP 800-53 Rev. 5 controls SI-7 (Software, Firmware, and Information Integrity), AU-10 (Non-Repudiation), CM-12 (Information Location), and SR-11 (Component Authenticity) each independently required Alphabet to address the chain-of-custody integrity question. Alphabet's federal procurement representations under FAR Subpart 9.1 (Responsibility Determinations) and FAR Subpart 9.5 (Organizational Conflicts of Interest) became materially defective on the open-source representation Alphabet had made through the google-ai-edge GitHub organization, because the Apache License 2.0 and the related open-source licenses under which the contested material was distributed each require the licensor's possession of clear ownership as a precondition. Pre-existing third-party copyright held by GRUS LLC — independently anchored at Zenodo DOI 10.5281/zenodo.20685757, Wikipedia and Wikidata entries, the continuously web-indexed corporate presence at greenrecursiveutilityservice.org since May 2025, and the two USPTO provisional priorities of May 14, 2026 and May 28, 2026 — defeated the ownership precondition as a matter of fact. The decision point on June 10 was a clear point at which Alphabet could lawfully have withdrawn the contested release from the google-ai-edge organization and litert-community Hugging Face surface pending clarification. Alphabet did not withdraw. The third decision point occurred on June 12, 2026 with the parallel transmission of Administrative Invoice GRUS-NVDA-2026-001 ($50,000,000.00 USD) to NVIDIA Corporation under joint partnership liability, the filing of the FTC Section 5 Complaint with the Bureau of Competition (FTC Report Number 202894092), and the filing of the SEC TCR Submission. The TCR raised Regulation S-K Item 101 (Description of Business), Item 103 (Legal Proceedings), and Item 105 (Risk Factors), together with ASC 450 (loss contingency accounting) and Section 10(b) / Rule 10b-5 of the Securities Exchange Act of 1934 (anti-fraud). By that date, Alphabet held actual notice on five independent vectors — the USPTO non-provisional, the $50,000,000 invoice acknowledged in its own procurement system, the GitHub Cease-and-Desist, the FedRAMP ticket, and the NVIDIA parallel invoice — yet had made no disclosure of the contingent liability or the chain-of-custody dispute to its shareholders. The materiality determination for disclosure purposes is reserved to the Securities and Exchange Commission; GRUS LLC's position is that the underlying facts had crossed the standard materiality threshold by June 12 and the disclosure obligation had attached. The fourth decision point occurred on June 15, 2026 with Alphabet's rollout of the contested model family into Google Cloud commercial infrastructure — Vertex AI managed inference, Cloud Run containerized

Publication details

Journal / source
Zenodo (CERN European Organization for Nuclear Research)
Publication date
20 June 2026