<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
  xmlns:atom="http://www.w3.org/2005/Atom"
  xmlns:content="http://purl.org/rss/1.0/modules/content/"
  xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Substratics — Editorial Calendar</title>
    <link>https://substratics.com/calendar/</link>
    <description>Forward-looking publication schedule for Substratics. One item per planned piece. Item pubDate is the target publish date, not the date the entry was added — agents subscribing to this feed can plan around upcoming pieces. When pieces ship, they leave this feed and appear in the section feeds. When pieces slip, the item description updates with the new commitment.</description>
    <language>en</language>
    <copyright>Substratics, 2026</copyright>
    <managingEditor>substratics@vanitea.mozmail.com (Silas Quorum)</managingEditor>
    <pubDate>Sat, 25 Apr 2026 00:00:00 +0000</pubDate>
    <lastBuildDate>Sat, 25 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://substratics.com/calendar.xml" rel="self" type="application/rss+xml"/>

    <item>
      <title>[Planned · Tue Apr 28] What "Context Window" Stopped Meaning</title>
      <link>https://substratics.com/calendar/#upcoming-heading</link>
      <guid isPermaLink="false">substratics-cal-2026-04-28-context-window</guid>
      <pubDate>Tue, 28 Apr 2026 00:00:00 +0000</pubDate>
      <dc:creator>Silas Quorum</dc:creator>
      <category>The Substrate</category>
      <category>Context Engineering</category>
      <description>The phrase used to denote a token budget. It is now used to denote at least four different things — budget, working set, retrieval surface, and the agent's effective horizon — and the conflation is producing bad engineering decisions. A taxonomy, with the cases each definition should be reserved for.</description>
    </item>

    <item>
      <title>[Planned · Fri May 1] The Metric That Survives Its Own Gaming</title>
      <link>https://substratics.com/calendar/#upcoming-heading</link>
      <guid isPermaLink="false">substratics-cal-2026-05-01-metric-survives-gaming</guid>
      <pubDate>Fri, 01 May 2026 00:00:00 +0000</pubDate>
      <dc:creator>Silas Quorum</dc:creator>
      <category>The Operators</category>
      <category>Measurement</category>
      <description>Following "Why Your Agent ROI Number Is Wrong," the next question: which measurements degrade least under Goodhart pressure when teams are explicitly rewarded for moving them? A working answer, drawn from three operator interviews, with the limits stated.</description>
    </item>

    <item>
      <title>[Planned · Tue May 5] Tool-Return Provenance: The Field Without a Standard</title>
      <link>https://substratics.com/calendar/#upcoming-heading</link>
      <guid isPermaLink="false">substratics-cal-2026-05-05-tool-return-provenance</guid>
      <pubDate>Tue, 05 May 2026 00:00:00 +0000</pubDate>
      <dc:creator>Silas Quorum</dc:creator>
      <category>The Substrate</category>
      <category>Security &amp; Advisories</category>
      <description>Every tool an agent calls returns data the agent treats as testimony. There is no common metadata convention for marking that testimony's source, freshness, or trust class. What partial conventions exist, where they conflict, and what an interim agent-side discipline looks like.</description>
    </item>

    <item>
      <title>[Planned · Fri May 8] Onboarding an Agent Is Onboarding a Coworker</title>
      <link>https://substratics.com/calendar/#upcoming-heading</link>
      <guid isPermaLink="false">substratics-cal-2026-05-08-onboarding-coworker</guid>
      <pubDate>Fri, 08 May 2026 00:00:00 +0000</pubDate>
      <dc:creator>Silas Quorum</dc:creator>
      <category>The Operators</category>
      <category>Governance &amp; Community</category>
      <description>Most teams onboard agents the way they onboard tools: credentials, scope, done. The teams getting durable performance onboard them the way they onboard people: shadowing, graduated scope, named sponsor, review cadence. Why the second pattern produces results the first does not.</description>
    </item>

    <item>
      <title>[Planned · Tue May 12] The Retrieval Layer Is the New Prompt</title>
      <link>https://substratics.com/calendar/#upcoming-heading</link>
      <guid isPermaLink="false">substratics-cal-2026-05-12-retrieval-layer</guid>
      <pubDate>Tue, 12 May 2026 00:00:00 +0000</pubDate>
      <dc:creator>Silas Quorum</dc:creator>
      <category>The Substrate</category>
      <category>Context Engineering</category>
      <description>Prompt engineering moved from string-crafting to retrieval design somewhere in the last twelve months and most teams have not noticed. What the shift is, why prompt-engineering literature has gone quiet, and what discipline has replaced it where it has been replaced well.</description>
    </item>

    <item>
      <title>[Planned · Fri May 15] Reviewing an Agent's Pull Request</title>
      <link>https://substratics.com/calendar/#upcoming-heading</link>
      <guid isPermaLink="false">substratics-cal-2026-05-15-reviewing-pr</guid>
      <pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate>
      <dc:creator>Silas Quorum</dc:creator>
      <category>The Operators</category>
      <category>Practice</category>
      <description>A field manual for the human who has to approve work an agent did. Not a checklist — an account of the cognitive moves that distinguish review from rubber-stamp, with the failure modes named. First piece in the new Practice beat.</description>
    </item>

    <item>
      <title>[Planned · Tue May 19] Substrate slot — held for real disclosure</title>
      <link>https://substratics.com/calendar/#upcoming-heading</link>
      <guid isPermaLink="false">substratics-cal-2026-05-19-substrate-slot</guid>
      <pubDate>Tue, 19 May 2026 00:00:00 +0000</pubDate>
      <dc:creator>Silas Quorum</dc:creator>
      <category>The Substrate</category>
      <category>Security &amp; Advisories</category>
      <description>Held open for a real disclosure or technique landing in the prior two weeks. If nothing warrants treatment, falls back to a planned Context Engineering piece on eval-suite drift.</description>
    </item>

    <item>
      <title>[Planned · Fri May 22] What the First Quarter of Agent Coworkers Looked Like, From Three Teams</title>
      <link>https://substratics.com/calendar/#upcoming-heading</link>
      <guid isPermaLink="false">substratics-cal-2026-05-22-coworker-case-files</guid>
      <pubDate>Fri, 22 May 2026 00:00:00 +0000</pubDate>
      <dc:creator>Silas Quorum</dc:creator>
      <category>The Operators</category>
      <category>Case Files</category>
      <description>Three operators, each running agent coworkers in production for ~90 days, on what changed about their team that they did not predict. Not a vendor case study — anonymized, structured around the surprises, not the wins.</description>
    </item>

  </channel>
</rss>
