Your CI/CD Pipeline Has a Blind Spot (and It's Not What You Think)

<h1> Draft Freely, Publish Narrowly: A Page Ownership Gate for Model-Written Docs </h1> <p>Documentation pipelines rarely fail because the model writes badly; they fail because

<h1> Your AI Agents Are Exploring Blind. Here's How to Give Them a Map. </h1> <p><em>Draft — queued after ai-autonomy-dod</em></p> <p>Every session, Claude reads the same files.

<p>Most GitLab linters tell you if your YAML is valid. Very few tell you if your YAML is <strong>dangerous</strong>.</p> <p>It's easy to feel safe when you see a green build, but

<p><strong>Authors:</strong> <a href="mailto:srastatter@google.com">Sean Rastatter</a>, <a href="mailto:rawanbadawi@google.com">Rawan Badawi</a></p> <p>Why do so many enterprises

<h2> Your code has CI/CD. Your docs don't. </h2> <p>Every modern engineering team has automated builds, tests, and deployments for their code. But documentation? That's still

<p>The morning after I lost my job, my Mac finished and filed an ASMR video. Nobody asked it to. It just ran.</p> <p>In the first post, I walked through the structure of the