<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Vectros Blog</title>
    <link>https://vectros.ai/blog/</link>
    <atom:link href="https://vectros.ai/blog/feed.xml" rel="self" type="application/rss+xml" />
    <description>Notes from the Vectros team on building secure, agent-ready AI back ends.</description>
    <language>en-us</language>
    <lastBuildDate>Mon, 29 Jun 2026 00:00:00 GMT</lastBuildDate>
    <item>
      <title>Customer zero: we run our own engineering org on Vectros</title>
      <link>https://vectros.ai/blog/customer-zero/</link>
      <guid isPermaLink="true">https://vectros.ai/blog/customer-zero/</guid>
      <pubDate>Mon, 29 Jun 2026 00:00:00 GMT</pubDate>
      <description>Durable docs aren&apos;t the same as recallable knowledge. How we put our entire SDLC knowledge base on Vectros, made it queryable by humans and agents alike, and why finding the rough edges ourselves was the whole point.</description>
      <category>engineering</category>
      <category>dogfooding</category>
      <category>case study</category>
    </item>
    <item>
      <title>Status belongs in your tracker. Knowledge belongs somewhere else.</title>
      <link>https://vectros.ai/blog/dont-mirror-your-issue-tracker/</link>
      <guid isPermaLink="true">https://vectros.ai/blog/dont-mirror-your-issue-tracker/</guid>
      <pubDate>Sun, 28 Jun 2026 00:00:00 GMT</pubDate>
      <description>Your tracker owns live status; your knowledge base owns the durable why and how. Mirroring one into the other gives you a stale shadow copy. The fix is to promote the durable few by reference.</description>
      <category>engineering</category>
      <category>knowledge management</category>
      <category>developer experience</category>
    </item>
  </channel>
</rss>
