ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
platform-dev
TenantAtlas/specs/300-internal-tenant-model-naming-consolidation/checklists/requirements.md
ahmido 292d555eac refactor: consolidate internal tenant model naming (#355) 
## Summary
- consolidate internal platform naming from `Tenant` to `Environment` / `ManagedEnvironment` across models, controllers, services, and Filament resources
- rename environment-scoped UI surfaces such as dashboards, chooser flows, navigation, and related widgets to match the updated environment-first domain language
- align middleware, onboarding/review lifecycle services, jobs, and route/context controllers with the new environment-scoped architecture

## Validation
- not rerun as part of this commit/push/PR request

## Notes
- branch is 1 commit ahead of `platform-dev`
- main commit: `refactor: consolidate internal tenant model naming`

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #355
2026-05-14 11:13:28 +00:00

3.3 KiB
Raw Permalink Blame History

Requirements Checklist: Internal Tenant Model Naming Consolidation

Purpose: Preparation readiness review for Spec 300
Created: 2026-05-13
Feature: specs/300-internal-tenant-model-naming-consolidation/spec.md

Candidate And Scope

  • CHK001 The selected candidate was directly provided by the user as Spec 300.
  • CHK002 The scope is cleanup-only and explicitly follows Specs 297-299.
  • CHK003 Completed-spec guardrail was checked for Specs 297-299; they are dependency context, not rewrite targets.
  • CHK004 The spec does not create a new product feature, navigation redesign, provider framework, OperationRun architecture, or localization sweep.
  • CHK005 The spec uses current repo truth: ManagedEnvironment and managed_environments already exist.

Constitution And Architecture

  • CHK006 SPEC-GATE-001 candidate check is filled.
  • CHK007 Proportionality review is filled for the broad structural rename blast radius.
  • CHK008 No new persisted product truth, enum/status family, DTO/presenter layer, registry, resolver, or UI framework is introduced.
  • CHK009 LEAN-001 compatibility posture is explicit: no aliases, no dual-write/read, no route compatibility unless the spec stops for migration risk.
  • CHK010 Provider boundary handling distinguishes platform Managed Environment truth from Microsoft/Entra/Graph tenant truth.

Route, RBAC, And Filament

  • CHK011 Canonical /admin/workspaces/{workspace}/environments/... route contract is explicit.
  • CHK012 Retired /admin/t/... and /admin/tenants/... route families remain forbidden.
  • CHK013 Workspace membership and Managed Environment membership semantics are preserved.
  • CHK014 Filament v5 / Livewire v4.0+ compliance is explicit.
  • CHK015 Laravel 12 panel provider registration location is apps/platform/bootstrap/providers.php.
  • CHK016 Global search impact is explicitly called out for renamed resources.
  • CHK017 Destructive action confirmation, execution via ->action(...), authorization, and audit preservation are explicit.
  • CHK018 Asset strategy is unchanged unless implementation unexpectedly registers Filament assets.

Test Governance

  • CHK019 Runtime/test impact is explicit.
  • CHK020 Focused validation lanes are named.
  • CHK021 Browser smoke anchors are explicit and do not become a hidden broad browser family.
  • CHK022 Fixture/helper cost risk is called out, especially around renamed tenant context helpers.
  • CHK023 Final scans and close-out inventory are required.

Artifact Readiness

  • CHK024 spec.md exists.
  • CHK025 plan.md exists.
  • CHK026 tasks.md exists.
  • CHK027 tenant-reference-inventory.md exists as a preparation baseline.
  • CHK028 allowed-tenant-references.md exists as a preparation baseline.
  • CHK029 Tasks are ordered, phased, and verifiable.
  • CHK030 No application implementation was performed during preparation.

Review Outcome

  • CHK031 Review outcome class: documentation-required-exception because provider/framework tenant references must remain allowed and documented.
  • CHK032 Workflow outcome: keep.
  • CHK033 Final note location: active feature PR close-out entry Guardrail / Structural Tenant Naming Consolidation / Smoke Coverage.