<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>GB/T on AutoZYX Blog</title><link>https://blog.autozyx.com/en/tags/gb/t/</link><description>Recent content in GB/T on AutoZYX Blog</description><generator>Hugo</generator><language>en</language><lastBuildDate>Mon, 04 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://blog.autozyx.com/en/tags/gb/t/index.xml" rel="self" type="application/rss+xml"/><item><title>When the Robotaxi Fails, Who Catches It?</title><link>https://blog.autozyx.com/en/posts/roam-l4-remote-ops-governance/</link><pubDate>Mon, 04 May 2026 00:00:00 +0000</pubDate><guid>https://blog.autozyx.com/en/posts/roam-l4-remote-ops-governance/</guid><description>From Cruise dragging a pedestrian in 2023, to the Waymo grid-outage stranding in late 2025, to nearly a hundred Apollo Go robotaxis going dead simultaneously on a Wuhan elevated road on March 31, 2026 — three incidents on three continents, three companies, three technology stacks, and the same exposed gap: when systemic failure hits, no one has a playbook. This post surveys the standards vacuum across ISO/SAE/IEC/China, traces the regulatory pivot after Wuhan, and introduces ROAM — an open-source reference architecture I built to start filling that gap.</description></item></channel></rss>