<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>AI-Native on Notes from the Rabbit Hole</title><link>https://magnus919.com/tags/ai-native/</link><description>Recent content in AI-Native on Notes from the Rabbit Hole</description><generator>Hugo</generator><language>en</language><copyright>© [Magnus Hedemark](https://github.com/magnus919)</copyright><lastBuildDate>Sun, 07 Jun 2026 15:00:00 -0400</lastBuildDate><atom:link href="https://magnus919.com/tags/ai-native/index.xml" rel="self" type="application/rss+xml"/><item><title>The Incidents Are the Training Data</title><link>https://magnus919.com/2026/06/the-incidents-are-the-training-data/</link><pubDate>Sun, 07 Jun 2026 15:00:00 -0400</pubDate><guid>https://magnus919.com/2026/06/the-incidents-are-the-training-data/</guid><description>&lt;p>There is a structural transformation happening in how software organizations operate. It has been described from different angles: as the software factory (repeatable delivery pipelines as industrial processes), as the AI flywheel (operational data as a continuous training signal), and as the AI-native startup playbook (eval suites as governance, tokens as headcount). But these are not three separate schools of thought. They are the same phenomenon viewed from process, learning, and organizational perspectives. The shift they all describe is: operations produce structured data, that data trains AI systems, those AI systems run operations.&lt;/p></description></item></channel></rss>