https://deevnet.github.io/deevnet-docs/docs/roadmap/infrastructure/tenant-services/tenant-lifecycle/Recent content in Tenant Lifecycle on Deevnet IoTaaSHugoen-ushttps://deevnet.github.io/deevnet-docs/docs/roadmap/infrastructure/tenant-services/tenant-lifecycle/plan/Mon, 01 Jan 0001 00:00:00 +0000https://deevnet.github.io/deevnet-docs/docs/roadmap/infrastructure/tenant-services/tenant-lifecycle/plan/<h1 id="tenant-lifecycle-project-plan"> Tenant Lifecycle: Project Plan <a class="anchor" href="#tenant-lifecycle-project-plan">#</a> </h1> <p>A repeatable, code-defined tenant lifecycle: each tenant is an isolated workload that supplies its own IaC/CaC to rebuild from scratch against the substrate, one of three plans for the tenant platform with <a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/roadmap/infrastructure/tenant-services/tenant-fabric/plan/">Tenant Fabric</a> and <a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/roadmap/infrastructure/tenant-services/platform-services/plan/">Tenant Platform Services</a>.</p> <p><strong>Roadmap item:</strong> <a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/roadmap/infrastructure/tenant-services/tenant-lifecycle/">Tenant Lifecycle</a></p> <div class="progress-container"> <div class="progress-bar"><div class="progress-segment-completed" style="width: 81.25%;" title="13 completed"></div><div class="progress-segment-in-progress" style="width: 6.25%;" title="1 in progress"></div><div class="progress-segment-planned" style="width: 12.5%;" title="2 planned"></div></div> <div class="progress-legend"> <span class="progress-legend-completed">&#x2713; 13</span> | <span class="progress-legend-in-progress">&#x21bb; 1</span> | <span class="progress-legend-planned">&#x23f3; 2</span> (16 total) </div> </div> <p><strong>Legend:</strong> ✅ Complete | 🔄 In Progress | ⏳ Planned</p> <hr> <h2 id="define-tenant-contracts-"> Define tenant contracts ✅ <a class="anchor" href="#define-tenant-contracts-">#</a> </h2> <p>The contract is the Deevnet API and its Terraform provider ( <a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/architecture/decisions/tenant-model/0015-tenant-onboarding-through-api/">ADR-0015</a>, deployed by <a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/changes/2026/0010-tenant-api-cutover/">CHG-0010</a>), and it is specified in one place: <a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/architecture/tenant/boundary/">Substrate and Tenant</a>. Its terms are <a href="https://deevnet.github.io/deevnet-docs/deevnet-docs/docs/architecture/decisions/tenant-model/0043-tenant-contract-terms/">ADR-0043</a>.</p>