<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Heysen</title><description>Documentation for Heysen — the multi-tenant platform US life-insurance brokerages run on. Agent handbook, commission semantics, and data-delivery rules.</description><link>https://doc.heysen.io/</link><language>en</language><item><title>Versioned source data — read one version, never sum them</title><link>https://doc.heysen.io/blog/versioned-source-data-one-version/</link><guid isPermaLink="true">https://doc.heysen.io/blog/versioned-source-data-one-version/</guid><description>Our source replica is append-only, so &quot;what does this record say now&quot; is the highest version and not a sum. A delivery that added second versions showed us why that rule needs a guard, not a comment.</description><pubDate>Sat, 26 Sep 2026 00:00:00 GMT</pubDate><category>data</category><category>incidents</category><category>engineering</category><author>Heysen Engineering</author></item><item><title>What a reconciliation gate actually protects</title><link>https://doc.heysen.io/blog/what-a-reconciliation-gate-protects/</link><guid isPermaLink="true">https://doc.heysen.io/blog/what-a-reconciliation-gate-protects/</guid><description>Hashes prove a file arrived intact. They cannot prove the file was computed correctly. That gap is why every delivery has to pass controls before the checkpoint moves.</description><pubDate>Sun, 20 Sep 2026 00:00:00 GMT</pubDate><category>data</category><category>engineering</category><author>Heysen Engineering</author></item><item><title>When data is late — freshness rules instead of pretending it&apos;s current</title><link>https://doc.heysen.io/blog/when-data-is-late-freshness-rules/</link><guid isPermaLink="true">https://doc.heysen.io/blog/when-data-is-late-freshness-rules/</guid><description>A daily file is evidence about the day it was produced, not a permanent truth. What we do when the feed does not arrive, and why &quot;delayed&quot; is better than a stale number with no label.</description><pubDate>Wed, 16 Sep 2026 00:00:00 GMT</pubDate><category>data</category><category>product-decisions</category><author>Heysen Engineering</author></item><item><title>Why your commission number has one source of truth</title><link>https://doc.heysen.io/blog/why-your-commission-number-has-one-source-of-truth/</link><guid isPermaLink="true">https://doc.heysen.io/blog/why-your-commission-number-has-one-source-of-truth/</guid><description>An agency can load its own income results, a processor can approve results, and legacy settlements can exist all at once. Here is why we show one number and label where it came from.</description><pubDate>Sat, 12 Sep 2026 00:00:00 GMT</pubDate><featured>true</featured><category>commission</category><category>data</category><category>product-decisions</category><author>Heysen Engineering</author></item><item><title>License holders vs the producer who earned the commission</title><link>https://doc.heysen.io/blog/license-holders-vs-the-producer-who-earned-the-commission/</link><guid isPermaLink="true">https://doc.heysen.io/blog/license-holders-vs-the-producer-who-earned-the-commission/</guid><description>Some agencies route every policy through a few licensed holders while somebody else writes the business. Modelling that honestly takes two separate mechanisms — and one of them is not about policies at all.</description><pubDate>Tue, 08 Sep 2026 00:00:00 GMT</pubDate><category>attribution</category><category>compliance</category><author>Heysen Engineering</author></item></channel></rss>