Layer 1 Intake: Why Google's COSMO Leak Validates The Compliance Gate

By Michael Leslie Atkinson · Founder, 905WOOD.COM SALES · May 7, 2026 · 7 min read

---

What COSMO actually contained

On May 1, a Google package identified as com.google.research.air.cosmo was pulled within hours of an accidental release. It was 1.13 gigabytes. Inside it sat a Nano-plus-Personal-Intelligence hybrid stack, fourteen distinct on-device skills wired into a multimodal runtime, and integration with the Mariner agent framework. The hardware floor was Pixel 10, twelve gigabytes of RAM, and an NPU. The implications for the Digital Refinery are that the architecture choices made in V13.0 and V14.0 of the Intelligence Engine — Pixel 10 Pro as the field unit, Tensor G5 as the silicon target, LiteRT-LM as the runtime, Gemma Nano as the local model class — were not bets on direction. They were bets on the floor that Google itself was building toward. A full deep-dive lives in CORE under COSMO_Deep_Dive_2026_05_04.md.

Why hardware choice is the audit defense

The Layer 1 stack has been specified in the Intelligence Engine V14.0 (the Commerce Bridge edition) and V15.0 (the Operational Bridge edition) at a level of detail that operator audits demand. The field unit is the Google Pixel 10 Pro. The silicon is the Tensor G5, fabricated on TSMC's three-nanometer N3E process and packaged in InFO-POP for thermal headroom across an eight-hour duty cycle. The CPU configuration is one Cortex-X4 plus five Cortex-A725 plus two Cortex-A520. The graphics block is the IMG DXT with hardware ray tracing. The AI engine is the next-generation EdgeTPU with a forty percent throughput increase over the prior generation. The runtime is LiteRT-LM v0.10.1 with speculative decoding and NPU acceleration. The vision model is Gemma 4 E2B at 2.3 billion parameters delivering binary classification under five hundred milliseconds end-to-end. The Visual Fallacy guard is Gemma 4 E4B at 4.5 billion parameters, called only when E2B confidence falls inside the AMBER band of seventy to eighty-five percent.

The dr.905wood.com Firebase deployment

On May 4 at 20:36 EDT, the Digital Refinery application went live on Firebase Hosting at gen-lang-client-0868935429.web.app. The custom domain dr.905wood.com cut over once Fastly cache propagation completed, roughly fifteen to sixty minutes later. The deployment pattern was codified as the AI Studio to Firebase Hosting Pattern V2.0 and saved into CORE for reuse across the rest of the layer-aligned subdomain set — vision.905wood.com, driver.905wood.com, ai.905wood.com, and the lab.905wood.com release that will host Operon Scientific Workspace.

The pattern matters because Firebase Hosting changed in late 2024. The historical pattern of CNAME pointing at ghs.googlehosted.com no longer works. Custom domains require a site-specific CNAME issued by the Firebase project. Anyone deploying an AI Studio application against a custom domain in 2026 needs the V2.0 pattern, not the documentation that Firebase still surfaces in older guides. The pattern is now ours and reusable.

The Visual Fallacy doctrine, in one paragraph

The Compliance Gate distrusts the visible image. Weathered chromated copper arsenate (CCA) wood appears identical to clean gray pine after a season outdoors. The fingertip green tint that operators learn to spot in fresh CCA fades within ninety days of weather exposure. The doctrine is "guilty until proven innocent" — audio overrides visual, origin overrides visual, hub-side XRF overrides edge classification. If the driver voice note contains "deck" or "demolition" or "renovation" or "painted" or "railway tie" or "pressure treated", the AMBER-band path triggers regardless of how confident E2B sounded. If the dropdown reads "Demolition", the load is high-risk subject waste regardless of visual confidence. The single audit-defensible verdict is the consensus verdict.

Hold-to-Seal — what the bin actually outputs

The Compliance Gate output is not a number. It is a sealed record. The driver holds the device for two seconds. The Titan M2 hardware root of trust signs a bundle that contains GPS coordinates within one metre, the timestamp, the AI model version (E2B or E4B with the version hash), the classification, and a kernel hash. That bundle is what regulators receive. That bundle is what survives a CBP officer pulling the load aside at the Ontario-Michigan crossing. That bundle is what the lineage hash chain stitches together so that two months later the verdict can be reproduced exactly — same model, same dataset, same regulatory text, same answer. The "Time Machine" is not metaphor. It is Vertex ML Metadata pinning the static graph at the millisecond of validation.

What the operator sees in the field

The driver opens the application. The Pixel 10 Pro's six-point-three inch LTPO OLED display switches into Laguna Outdoor Mode for high-sunlight visibility. The camera frames the load. The classification returns under two seconds with a confidence band — green for clean, yellow for AMBER consensus required, red for high-risk subject waste. If yellow, the second model runs. If still ambiguous, the load is held for hub-side XRF. If clean, Hold-to-Seal becomes available. Two seconds of haptic. The load gets a sealed verdict. The 9-Point Certificate of Origin queues for generation when the load reaches the border. None of this is theoretical. The architecture is one that Google itself has been quietly building toward, as COSMO confirmed.

Why this layer carries everything else

The CIRCIL Levy verdict at Layer 4 is only as defensible as the Layer 1 classification that fed it. The 9-Point Certificate of Origin at Layer 5 is only as defensible as the GPS attestation and Visual Fallacy guard that signed it. The CORC math at Layer 4 plus Layer 5 only counts if the wood was actually clean. The customs broker filing under HS 3825.0 only survives audit if the Wholly Obtained Good attestation traces back to a Layer 1 verdict that cited its grounding. Layer 1 is not the Compliance Gate. Layer 1 is the only Compliance Gate. Every other layer carries a copy of its verdict downstream.

Three things to do in 2026

• Request a Compliance Gate baseline assessment for your active wood-waste streams. The on-site walkthrough takes about ninety minutes and produces a documented current-state classification distribution.
• Review your driver-side documentation procedure. The audio note is not optional. The origin dropdown is not optional. The Visual Fallacy doctrine assumes the metadata layer arrives intact.
• Map your Mothership routes against the Pixel 10 Pro's eight-hour continuous NPU duty cycle. There is no thermal throttling at that envelope. Above it, model fall-back occurs.

The reframe

The hardware floor is no longer a research bet. COSMO confirmed it. The Compliance Gate is no longer a slide. dr.905wood.com is on production. The classification is no longer aspirational. The Titan M2 signs the bundle in two seconds at the bin. Layer 1 carries the rest of the platform.

---