Blog: Learn Machine Learning from a Google AI Engineer
Reimagining the Supply Chain: Why Vector RAG Fails in Physical Operations (And How Agentic Knowledge Graphs Fix It)
Picture this: it’s 2:00 AM at a global ocean shipping division, and a critical support alert escalates to the night desk. A customer support coordinator opens a newly deployed Gemini AI assistant and types a simple question: “Why is container SHP-10005 delayed?”
“The container is blocked at the terminal due to a severe weight discrepancy,” the assistant replies. “Local documentation shows a gross weight of 45,000, whereas the verified tare weight is 20,000.”
The customer panics and files a cargo-tampering claim. Down at the port, the terminal system flags the box and halts loading before the crane can touch it.
When the on-call engineering team digs through the execution logs at dawn, they uncover a costly data mismatch. The steel seal on the container stayed intact, and the cargo weight matched the manifest to the pound. The AI agent had pulled a raw number from a legacy database column named gross_weight_lbs (measured in pounds) and compared it against a standardized column named tare_weight_kg (measured in kilograms). Because the vector embeddings for “weight” cluster tightly in logistics documentation, cosine similarity projected gross_weight_lbs right next to tare_weight_kg in vector space. The probabilistic Retrieval-Augmented Generation (RAG) pipeline matched the two fields, treated pounds and kilograms as identical units, calculated a phantom discrepancy, and froze a live shipment.
By the time engineers clear the false flag, container SHP-10005 has missed its flatbed truck pickup. The box sits on the pier concrete for five days, racking up $15,000 in terminal demurrage fees.
In the Google Cloud Office of the CTO (OCTO), I spend my time working shoulder-to-shoulder with engineering teams at the world’s largest logistics and enterprise organizations to co-build proofs for problems like this. When you work with global carriers moving millions of containers across oceans, you learn fast that enterprise AI requires more than a clever prompt and a vector index. Relying on vector math to bridge structured physical operations is a fast way to gamble with your supply chain.
Blaming the Developer for the AI Bill? You’re Managing Software Like It’s 1996.
Vector Embeddings vs. the DSM-5: The Mathematical Flaw in Mental Health AI
Learning the Hard Way: When Agents Build Agents (And the Culture Changes It Requires)