<?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 Engineering on 67AI Lab</title>
    <link>https://67ailab.com/tags/ai-native-engineering/</link>
    <description>Recent content in AI-Native Engineering on 67AI Lab</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 15 Sep 2026 12:30:00 +0000</lastBuildDate>
    <atom:link href="https://67ailab.com/tags/ai-native-engineering/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>AI-Native Engineering Is About What You Accept, Not What You Generate</title>
      <link>https://67ailab.com/posts/ai-native-engineering-acceptance-not-generation/</link>
      <pubDate>Tue, 15 Sep 2026 12:30:00 +0000</pubDate>
      <guid>https://67ailab.com/posts/ai-native-engineering-acceptance-not-generation/</guid>
      <description>&lt;p&gt;&amp;ldquo;AI-native&amp;rdquo; has become one of those terms that sounds precise until you ask two people to define it.&lt;/p&gt;&#xA;&lt;p&gt;Sometimes it describes an &lt;strong&gt;AI-native product&lt;/strong&gt;: software whose core behaviour depends on AI models. Sometimes it describes an &lt;strong&gt;AI-native software lifecycle&lt;/strong&gt;: a development process reorganised around agents. And sometimes it describes an &lt;strong&gt;AI-native organisation&lt;/strong&gt;: teams, processes, and governance redesigned around AI.&lt;/p&gt;&#xA;&lt;p&gt;These are different things.&lt;/p&gt;&#xA;&lt;p&gt;A team can build a product with no AI in it and still engineer it in an AI-native way. Another team can build a sophisticated LLM product using essentially the same software process it used in 2019.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
