<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Process Metronome Blog</title>
    <link>https://process-metronome.com/blog/</link>
    <description>Insights on AI orchestration, operational knowledge graphs, and how teams scale with structure.</description>
    <language>en</language>
    <atom:link href="https://process-metronome.com/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The operational graph</title>
      <link>https://process-metronome.com/blog/operational-graph/</link>
      <guid isPermaLink="true">https://process-metronome.com/blog/operational-graph/</guid>
      <description>When the graph is sovereign and sessions are derived, AI agents get a structural foundation they can be trusted to operate within.</description>
      <pubDate>Sat, 28 Mar 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The procedural graph is not enough</title>
      <link>https://process-metronome.com/blog/procedural-graph-not-enough/</link>
      <guid isPermaLink="true">https://process-metronome.com/blog/procedural-graph-not-enough/</guid>
      <description>AI adoption in operations keeps failing for the same structural reason. Making models smarter about your domain is not the fix.</description>
      <pubDate>Fri, 27 Mar 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>The Metronome Approach to AI in Operations</title>
      <link>https://process-metronome.com/blog/the-metronome-approach-to-ai-in-operations/</link>
      <guid isPermaLink="true">https://process-metronome.com/blog/the-metronome-approach-to-ai-in-operations/</guid>
      <description>Why operational AI needs architectural constraints, not just better models. An introduction to the philosophy behind Process Metronome.</description>
      <pubDate>Mon, 16 Mar 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Seven pillars of operational AI trust</title>
      <link>https://process-metronome.com/blog/seven-pillars-of-operational-ai-trust/</link>
      <guid isPermaLink="true">https://process-metronome.com/blog/seven-pillars-of-operational-ai-trust/</guid>
      <description>Explicit intent, determinism, compliance by design, subsidiarity, atomicity, auditability, and human accountability: the architectural foundations that make AI trustworthy in operations.</description>
      <pubDate>Mon, 16 Mar 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Explicit Intent: Why AI Must Not Decide Its Own Objectives</title>
      <link>https://process-metronome.com/blog/explicit-intent/</link>
      <guid isPermaLink="true">https://process-metronome.com/blog/explicit-intent/</guid>
      <description>The first pillar of operational AI trust. When AI agents derive their goals from the operational context rather than inference, every action has a clear origin.</description>
      <pubDate>Mon, 16 Mar 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Determinism: Why Every AI Action Must Be Expected</title>
      <link>https://process-metronome.com/blog/determinism/</link>
      <guid isPermaLink="true">https://process-metronome.com/blog/determinism/</guid>
      <description>The second pillar of operational AI trust. When every AI action is generated by a known process step, operations teams can anticipate what happens next.</description>
      <pubDate>Mon, 16 Mar 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Compliance by Design: Making Invalid Operations Inexpressible</title>
      <link>https://process-metronome.com/blog/compliance-by-design/</link>
      <guid isPermaLink="true">https://process-metronome.com/blog/compliance-by-design/</guid>
      <description>The third pillar of operational AI trust. When the architecture makes constraint violations structurally impossible, compliance stops being a checklist.</description>
      <pubDate>Mon, 16 Mar 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Subsidiarity: Why Decisions Must Stay Close to the Ground</title>
      <link>https://process-metronome.com/blog/subsidiarity/</link>
      <guid isPermaLink="true">https://process-metronome.com/blog/subsidiarity/</guid>
      <description>The fourth pillar of operational AI trust. When actions route to the person closest to the event, AI supports local judgment instead of overriding it.</description>
      <pubDate>Mon, 16 Mar 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Atomicity: Why AI Must Act One Step at a Time</title>
      <link>https://process-metronome.com/blog/atomicity/</link>
      <guid isPermaLink="true">https://process-metronome.com/blog/atomicity/</guid>
      <description>The fifth pillar of operational AI trust. When each AI interaction produces exactly one outcome, autonomous chains cannot form and trust is preserved.</description>
      <pubDate>Mon, 16 Mar 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Auditability: Why AI and Humans Must Share the Same Record</title>
      <link>https://process-metronome.com/blog/auditability/</link>
      <guid isPermaLink="true">https://process-metronome.com/blog/auditability/</guid>
      <description>The sixth pillar of operational AI trust. When AI and human actions live in the same audit trail, there is one version of the truth and no reconciliation needed.</description>
      <pubDate>Mon, 16 Mar 2026 00:00:00 GMT</pubDate>
    </item>
    <item>
      <title>Human Accountability: Why Every AI Action Needs a Named Owner</title>
      <link>https://process-metronome.com/blog/human-accountability/</link>
      <guid isPermaLink="true">https://process-metronome.com/blog/human-accountability/</guid>
      <description>The seventh pillar of operational AI trust. When every AI invocation traces back to a named human principal, accountability never disappears into the algorithm.</description>
      <pubDate>Mon, 16 Mar 2026 00:00:00 GMT</pubDate>
    </item>
  </channel>
</rss>