<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Barycenter Systems · Writing</title>
    <link>https://barycenter.systems/writing</link>
    <atom:link href="https://barycenter.systems/rss.xml" rel="self" type="application/rss+xml" />
    <description>Essays and research notes on autonomous mission intelligence: mission autonomy under human authority.</description>
    <language>en</language>
    <lastBuildDate>Sat, 11 Jul 2026 12:00:00 GMT</lastBuildDate>
    <item>
      <title>Why space missions need a trust boundary, not a smarter model</title>
      <link>https://barycenter.systems/writing/trust-boundary</link>
      <guid isPermaLink="true">https://barycenter.systems/writing/trust-boundary</guid>
      <pubDate>Sat, 11 Jul 2026 12:00:00 GMT</pubDate>
      <dc:creator>Naveen Joshi</dc:creator>
      <description>NASA's own ranked shortfalls describe a missing systems layer, not a missing model. The layer that is missing is a trust boundary: a separate mechanism that decides what may execute.</description>
    </item>
    <item>
      <title>What thirty years of JPL autonomy actually proved</title>
      <link>https://barycenter.systems/writing/jpl-thirty-years</link>
      <guid isPermaLink="true">https://barycenter.systems/writing/jpl-thirty-years</guid>
      <pubDate>Sat, 11 Jul 2026 12:00:00 GMT</pubDate>
      <dc:creator>Naveen Joshi</dc:creator>
      <description>Remote Agent, CASPER, AEGIS, AutoNav, TRN, Ingenuity: what each system solved, what it deliberately did not, and why the strongest were hybrids with a separate mechanism deciding what may execute.</description>
    </item>
    <item>
      <title>Permits, not promises: what an assurance kernel does</title>
      <link>https://barycenter.systems/writing/permits-not-promises</link>
      <guid isPermaLink="true">https://barycenter.systems/writing/permits-not-promises</guid>
      <pubDate>Sat, 11 Jul 2026 12:00:00 GMT</pubDate>
      <dc:creator>Naveen Joshi</dc:creator>
      <description>How execution permits work, why the assurance kernel is independent, and what deterministic replay actually buys an accident board. References DO-178C, NPR 7150.2, and ECSS as design targets.</description>
    </item>
  </channel>
</rss>
