TenantAtlas/specs/262-lifecycle-governance-taxonomy/quickstart.md

Quickstart: Workspace, Tenant & Managed Object Lifecycle Governance v1

Preconditions

1. No application runtime needs to be started for this slice.
2. Keep validation repo-based and artifact-based. No Sail test lane or browser smoke is required because this package changes no runtime behavior.

Scenario 1: Verify the six lifecycle dimensions

1. Open specs/262-lifecycle-governance-taxonomy/contracts/lifecycle-governance-taxonomy.yaml.
2. Open docs/product/standards/lifecycle-governance.md.
3. Verify the contract and standard list exactly these dimensions:
   • local record lifecycle
   • provider presence lifecycle
   • operator suppression lifecycle
   • commercial/workspace lifecycle
   • retention/compliance lifecycle
   • restoreability lifecycle
4. Confirm each dimension names current repo-real sources and reserved follow-up values separately.

Scenario 2: Verify the deferred candidate questions are answered

1. Review specs/262-lifecycle-governance-taxonomy/spec.md, specs/262-lifecycle-governance-taxonomy/data-model.md, and docs/product/standards/lifecycle-governance.md.
2. Confirm the package gives explicit answers for:
   • what deleted means
   • what missing from provider means
   • what ignored means
   • what workspace suspension or closure means in relation to retention and restoreability
   • whether export requested is named as a reserved retention/compliance value while the actual export workflow remains a follow-up slice
   • that concrete artifact-level export contents are intentionally deferred to Data Export Before Deletion v1
   • what data remains retained versus purgeable

Scenario 3: Verify current repo truth maps cleanly into the taxonomy

1. Use the repo search commands below.
2. Confirm that tenant lifecycle, commercial lifecycle, provider presence, retention expiry, and restore continuity all map into one dimension each.
3. Confirm the package does not claim runtime meanings that the repo does not yet implement.

Scenario 4: Verify follow-up boundaries remain explicit

1. Review the follow-up slice list in spec.md, data-model.md, contracts/lifecycle-governance-taxonomy.yaml, and docs/product/standards/lifecycle-governance.md.
2. Confirm the package repeats these exact follow-up slice names:
   • Provider-Missing Managed Object Truth v1
   • Workspace & Tenant Closure Lifecycle v1
   • Data Export Before Deletion v1
   • Retention & Purge Governance v1
   • Restoreability Expiry & Evidence Retention v1
3. Confirm that export requested is treated as a reserved retention/compliance value and that those follow-up slices stay separate rather than hidden in the primary scope.

Focused Validation Commands

export PATH="/bin:/usr/bin:/usr/local/bin:$PATH" && cd /Users/ahmeddarrazi/Documents/projects/wt-plattform && rg -n -- "Workspace, Tenant & Managed Object Lifecycle Governance v1|Provider-Missing Managed Object Truth v1|Workspace & Tenant Closure Lifecycle v1|Data Export Before Deletion v1|Retention & Purge Governance v1|Restoreability Expiry & Evidence Retention v1" docs/product/spec-candidates.md specs/262-lifecycle-governance-taxonomy

export PATH="/bin:/usr/bin:/usr/local/bin:$PATH" && cd /Users/ahmeddarrazi/Documents/projects/wt-plattform && rg -n -- "local record lifecycle|provider presence lifecycle|operator suppression lifecycle|commercial/workspace lifecycle|retention/compliance lifecycle|restoreability lifecycle|export_requested|OperationRun" docs/product/standards/lifecycle-governance.md specs/262-lifecycle-governance-taxonomy/contracts/lifecycle-governance-taxonomy.yaml specs/262-lifecycle-governance-taxonomy/data-model.md

export PATH="/bin:/usr/bin:/usr/local/bin:$PATH" && cd /Users/ahmeddarrazi/Documents/projects/wt-plattform && rg -n -- "draft|onboarding|active|archived|ignored_at|missing_from_provider_at|suspended|expired|retention" apps/platform/app/Models/Tenant.php apps/platform/app/Models/Policy.php apps/platform/app/Models/ReviewPack.php apps/platform/app/Models/BackupSet.php apps/platform/app/Models/RestoreRun.php apps/platform/app/Console/Commands/PruneReviewPacksCommand.php apps/platform/config/tenantpilot.php specs/143-tenant-lifecycle-operability-context-semantics/spec.md specs/251-commercial-entitlements-billing-state/spec.md specs/261-provider-missing-policy-visibility/spec.md specs/091-backupschedule-retention-lifecycle/spec.md

Finish

1. Re-run the preparation checklist in specs/262-lifecycle-governance-taxonomy/checklists/requirements.md.
2. Confirm the package still introduces no runtime behavior, no new product persistence, and no hidden follow-up implementation.

Close-Out Outcome

• Review outcome: Core Enterprise
• Workflow outcome: implemented on the standards-and-contract path only
• Test-governance outcome: keep docs-only validation with no runtime lane expansion