<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Making Data Systems Behave - treasury</title><link>https://makingdatabehave.com/</link><description/><atom:link href="https://makingdatabehave.com/treasury/feed.xml" rel="self"/><lastBuildDate>Wed, 22 Jul 2026 14:20:41 +0100</lastBuildDate><item><title>Why Treasury Liquidity Looks Like a Digital Twin Problem</title><link>https://makingdatabehave.com/treasury/1</link><description>&lt;p&gt;Treasury liquidity behaves like a time-dependent network: usable cash depends on where value sits, which routes remain available and whether it can arrive before it is needed.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rob Wilson</dc:creator><pubDate>Wed, 22 Jul 2026 00:00:00 +0100</pubDate><guid>tag:makingdatabehave.com,2026-07-22:/treasury/1</guid><category>treasury</category><category>data-engineering</category><category>dataops</category><category>data-architecture</category><category>treasury</category><category>liquidity</category></item></channel></rss>