<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Livastar Observer - Journal</title>
    <link>https://livastar.observer/journal</link>
    <description>Writing on quality engineering, AI-assisted development, and building trust-first products.</description>
    <language>en</language>
    <atom:link href="https://livastar.observer/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Wrapping a public site around a gated app</title>
      <link>https://livastar.observer/journal/prerendering-a-gated-spa</link>
      <guid isPermaLink="true">https://livastar.observer/journal/prerendering-a-gated-spa</guid>
      <pubDate>Invalid Date</pubDate>
      <description>A note on the original shared build: prerender public pages while keeping the product client-only. The personal site now has its own repository.</description>
    </item>
    <item>
      <title>Guardrails belong in code, not in a style guide</title>
      <link>https://livastar.observer/journal/guardrails-belong-in-code</link>
      <guid isPermaLink="true">https://livastar.observer/journal/guardrails-belong-in-code</guid>
      <pubDate>Invalid Date</pubDate>
      <description>A style guide asks people to remember the rules. A CI check refuses to merge when they forget. In trust-first domains, that difference is the whole game.</description>
    </item>
    <item>
      <title>One investigator per shard</title>
      <link>https://livastar.observer/journal/one-investigator-per-shard</link>
      <guid isPermaLink="true">https://livastar.observer/journal/one-investigator-per-shard</guid>
      <pubDate>Invalid Date</pubDate>
      <description>When several CI shards fail at once, the instinct is to debug them one by one. Fan out instead: one investigator per shard, in parallel, then synthesise.</description>
    </item>
  </channel>
</rss>
