<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ownership on F. Latini - IT Engineer</title><link>https://latini.dev/tags/ownership/</link><description>Recent content in Ownership on F. Latini - IT Engineer</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 08 Oct 2026 08:00:00 +0000</lastBuildDate><atom:link href="https://latini.dev/tags/ownership/index.xml" rel="self" type="application/rss+xml"/><item><title>The Estate You Cannot Enumerate</title><link>https://latini.dev/posts/the-estate-you-cannot-enumerate/</link><pubDate>Thu, 08 Oct 2026 08:00:00 +0000</pubDate><guid>https://latini.dev/posts/the-estate-you-cannot-enumerate/</guid><description>&lt;p&gt;&lt;strong&gt;TL;DR&lt;/strong&gt; - Ask most engineering organisations &amp;ldquo;what is running on the vulnerable version, and who owns each one?&amp;rdquo; and the honest answer is &amp;ldquo;give us two weeks&amp;rdquo;. Not because the question is hard, but because nobody owns the answer. The list gets rebuilt from scratch for every CVE, every forced migration, every audit, every cost sprint and every reorg, and thrown away afterwards. That is a platform capability being paid for as a recurring emergency. The fix is not a better catalogue, because a catalogue records what people declared, and the estate is whatever is actually running. Build the inventory from what the machines observe, treat the difference between declared and observed as the product, attach ownership to something that survives a reorg, make &amp;ldquo;unowned&amp;rdquo; a first-class state with a queue, and measure the whole thing by how long it takes to answer a question. Start with a nightly job and a table, not a portal.&lt;/p&gt;</description></item></channel></rss>