https://deevnet.github.io/deevnet-docs/docs/policies/lifecycle-management/Recent content in Lifecycle Management on Deevnet IoTaaSHugoen-ushttps://deevnet.github.io/deevnet-docs/docs/policies/lifecycle-management/discovery/Mon, 01 Jan 0001 00:00:00 +0000https://deevnet.github.io/deevnet-docs/docs/policies/lifecycle-management/discovery/<h1 id="discovery-hahahugoshortcode151s0hbhb"> Discovery <span class="status-badge status-planned">Planned</span> <a class="anchor" href="#discovery-hahahugoshortcode151s0hbhb">#</a> </h1> <p>Stage 4 of <a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/policies/lifecycle-management/">Lifecycle Management</a>: knowing what is actually running, and learning what upstream has released for it. Discovery doesn&rsquo;t change anything. What it finds starts another stage: a patch, a certification, an upgrade or a retirement.</p> <hr> <h2 id="validate-what-is-running"> Validate what is running <a class="anchor" href="#validate-what-is-running">#</a> </h2> <p>The <a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/platforms/software-catalog/">Software Catalog</a> is the system of record for versions, but most of what it holds is <strong>declared</strong>: inventory pins, role defaults, lockfiles. A pin is intent. It says what the automation deploys, not what is running after a manual upgrade, a failed play or a host rebuilt by hand. Some entries were never written down at all.</p>