<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"><channel>
<title>Field Notes</title>
<link>https://field-notes.resonantconstructs.ai/</link>
<description>What actually happened, how it broke, and what was changed.</description>
<language>en</language>
<item>
<title>The Claim Ledger That Was Not Enforcing Its Own Contract</title>
<link>https://field-notes.resonantconstructs.ai/posts/the-claim-ledger-that-was-not-enforcing-its-own-contract/</link>
<guid isPermaLink="true">https://field-notes.resonantconstructs.ai/posts/the-claim-ledger-that-was-not-enforcing-its-own-contract/</guid>
<pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate>
<description>Our marketing contract required every claim to carry a presentation role and a copy-ready flag. The generated ledgers carried neither, so internal task instructions were being classified as public marketing claims.</description>
</item>
</channel></rss>
