<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Operator Notes . The Pivotal Protocol</title>
    <link>https://thepivotalprotocol.com/operator-notes</link>
    <atom:link href="https://thepivotalprotocol.com/operator-notes/feed.xml" rel="self" type="application/rss+xml" />
    <description>Frameworks and operational patterns for solo and small-team clinical operators. Published as they clear the editorial bar.</description>
    <language>en-us</language>
    <copyright>Copyright 2026 The Pivotal Protocol. All rights reserved.</copyright>
    <lastBuildDate>Tue, 21 Apr 2026 12:00:00 +0000</lastBuildDate>
    <pubDate>Tue, 21 Apr 2026 12:00:00 +0000</pubDate>
    <ttl>1440</ttl>
    <image>
      <url>https://thepivotalprotocol.com/pivotal_logo.png</url>
      <title>Operator Notes . The Pivotal Protocol</title>
      <link>https://thepivotalprotocol.com/operator-notes</link>
    </image>

    <item>
      <title>No. 02 . The Two-Vault Pattern</title>
      <link>https://thepivotalprotocol.com/vault</link>
      <guid isPermaLink="false">pivotalprotocol-operator-notes-002</guid>
      <pubDate>Tue, 21 Apr 2026 12:00:00 +0000</pubDate>
      <dc:creator>Pivotal Protocol Operator Notes Editorial</dc:creator>
      <description><![CDATA[<p><em>A Practical Architecture for Operators Who Cannot Accept Cloud Exposure of Named-Human Data.</em></p><p>Solo and small-team operators commonly consolidate all knowledge-management work into a single tool under a single sync policy. For operators handling named-human data, this forces an unnecessary choice between cloud convenience and data sovereignty. The Two-Vault Pattern resolves the tension with two functionally identical knowledge repositories operated under two different sync policies, separated by a single classification rule. Implementation is under an hour in any tool that supports folder-scoped vaults.</p><p>5 pages. 7 citations. <a href="https://thepivotalprotocol.com/vault">Download PDF</a>.</p>]]></description>
      <enclosure url="https://thepivotalprotocol.com/operator-notes/OperatorNotes_No02_TwoVaultPattern.pdf" type="application/pdf" length="419214" />
    </item>

    <item>
      <title>No. 01 . Data Sovereignty in the Age of Cloud Convenience</title>
      <link>https://thepivotalprotocol.com/sov</link>
      <guid isPermaLink="false">pivotalprotocol-operator-notes-001</guid>
      <pubDate>Tue, 21 Apr 2026 12:00:00 +0000</pubDate>
      <dc:creator>Pivotal Protocol Operator Notes Editorial</dc:creator>
      <description><![CDATA[<p><em>A Decision Framework for Operators Handling Named-Human Data.</em></p><p>The cloud-versus-local debate is usually framed as a security question. It is not. Security is one axis of four. When a cloud provider's security is assumed sufficient, four non-security exposures remain: legal discoverability, availability dependency, jurisdictional drift, and provider-policy risk. This paper argues that sensitivity-based partitioning is the wrong decision variable. The correct variable is control loss cost, and the operational rule that follows is simple enough to write on a card.</p><p>6 pages. 10 citations. <a href="https://thepivotalprotocol.com/sov">Download PDF</a>.</p>]]></description>
      <enclosure url="https://thepivotalprotocol.com/operator-notes/OperatorNotes_No01_DataSovereignty.pdf" type="application/pdf" length="398082" />
    </item>

  </channel>
</rss>
