<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Declarative Reconciliation on Deevnet IoTaaS</title><link>https://deevnet.github.io/deevnet-docs/docs/roadmap/infrastructure/substrate/reconciliation/</link><description>Recent content in Declarative Reconciliation on Deevnet IoTaaS</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://deevnet.github.io/deevnet-docs/docs/roadmap/infrastructure/substrate/reconciliation/index.xml" rel="self" type="application/rss+xml"/><item><title>Declarative Reconciliation: Project Plan</title><link>https://deevnet.github.io/deevnet-docs/docs/roadmap/infrastructure/substrate/reconciliation/plan/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deevnet.github.io/deevnet-docs/docs/roadmap/infrastructure/substrate/reconciliation/plan/</guid><description>&lt;h1 id="declarative-reconciliation-project-plan">
 Declarative Reconciliation: Project Plan
 &lt;a class="anchor" href="#declarative-reconciliation-project-plan">#&lt;/a>
&lt;/h1>
&lt;p>Close the gap between what inventory declares and what the substrate actually runs. Several roles today reconcile &lt;em>additively&lt;/em> — they create and update, but never remove — so deleting a host from inventory leaves its live state behind indefinitely.&lt;/p>
&lt;p>&lt;strong>Roadmap item:&lt;/strong> 
 &lt;a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/roadmap/infrastructure/substrate/reconciliation/">Declarative Reconciliation&lt;/a>&lt;/p>
&lt;div class="progress-container">
 &lt;div class="progress-bar">&lt;div class="progress-segment-completed" style="width: 9.090909090909092%;" title="1 completed">&lt;/div>&lt;div class="progress-segment-planned" style="width: 90.9090909090909%;" title="10 planned">&lt;/div>&lt;/div>
 &lt;div class="progress-legend">
 &lt;span class="progress-legend-completed">&amp;#x2713; 1&lt;/span> |
 &lt;span class="progress-legend-in-progress">&amp;#x21bb; 0&lt;/span> |
 &lt;span class="progress-legend-planned">&amp;#x23f3; 10&lt;/span>
 (11 total)
 &lt;/div>
&lt;/div>
&lt;p>&lt;strong>Legend:&lt;/strong> ✅ Complete | 🔄 In Progress | ⏳ Planned&lt;/p>
&lt;hr>
&lt;h2 id="project-vision--scope">
 Project Vision &amp;amp; Scope
 &lt;a class="anchor" href="#project-vision--scope">#&lt;/a>
&lt;/h2>
&lt;p>The substrate is meant to be reconstructible from its declarations. 
 &lt;a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/runbook/substrate/building-recovery/">Building Infrastructure&lt;/a> states that any host can be wiped and rebuilt from source control, and 
 &lt;a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/architecture/naming-and-addressing/">Naming and Addressing&lt;/a> makes a host&amp;rsquo;s address &amp;ldquo;a fact about its declaration, not about the order it booted in&amp;rdquo;.&lt;/p></description></item></channel></rss>