
  <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
      <title>Rambling Me</title>
      <link>https://www.rambling-me.com/blog</link>
      <description>A blog to reflect my thoughts, learnings, and observations</description>
      <language>en-us</language>
      <managingEditor>me@rambling-me.com (Dopeking)</managingEditor>
      <webMaster>me@rambling-me.com (Dopeking)</webMaster>
      <lastBuildDate>Mon, 11 May 2026 00:00:00 GMT</lastBuildDate>
      <atom:link href="https://www.rambling-me.com/tags/architecture/feed.xml" rel="self" type="application/rss+xml"/>
      
  <item>
    <guid>https://www.rambling-me.com/blog/posts/technology/agentic/4-docs-as-the-source-of-truth</guid>
    <title>AI State of Play - Part 4: Docs as the Source of Truth</title>
    <link>https://www.rambling-me.com/blog/posts/technology/agentic/4-docs-as-the-source-of-truth</link>
    <description>PRDs, ADRs, design docs and acceptance criteria are not deliverables that engineers tolerate. With agentic tools, they are the substrate that makes agentic engineering work - the same artefacts feeding the implementation agent, the QA agent, and the design agent, with the spec compiled into code, tests, and UI alike. Part 4 walks a worked example end-to-end: adding a public API and RBAC to a B2B SaaS, with auth as the feature carrying through this post and into Part 5.</description>
    <pubDate>Mon, 11 May 2026 00:00:00 GMT</pubDate>
    <author>me@rambling-me.com (Dopeking)</author>
    <category>technology</category><category>ai</category><category>agentic</category><category>claude code</category><category>developer tools</category><category>software development</category><category>documentation</category><category>architecture</category>
  </item>

    </channel>
  </rss>
