ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
185f2795c6
TenantAtlas/specs/297-managed-environment-canonical-route-cutover/checklists/requirements.md
Ahmed Darrazi 185f2795c6
Some checks failed
PR Fast Feedback / fast-feedback (pull_request) Failing after 1m45s
Details
feat: retire legacy tenant route surfaces
2026-05-13 01:31:46 +02:00

2.6 KiB
Raw Blame History

Requirements Checklist: Managed Environment Canonical Route Cutover

Purpose: Preparation readiness checklist for Spec 297.
Created: 2026-05-12

Spec Readiness

  • Problem statement names the active legacy surfaces.
  • Goals distinguish product/route/UI/test truth from DB/model rename.
  • Non-goals explicitly forbid compatibility layer, DB rename, broad localization, Package Execution, Guided Operations, Microsoft provider refactor, and broad RBAC refactor.
  • Functional requirements cover TenantPanelProvider, /admin/t, /admin/tenants, canonical managed-environment links, intended URLs, required permissions, provider connections, helper rename, copy cleanup, guards, and RBAC.
  • Acceptance criteria define route, link, helper, intended URL, provider/permission, RBAC, and validation outcomes.
  • Final implementation output contract is included.

Constitution / Governance

  • SPEC-GATE-001 candidate check is filled.
  • Proportionality review is filled for the possible link helper and spec-local audit artifact.
  • No new persisted truth is introduced.
  • Workspace isolation and managed-environment entitlement are explicit.
  • RBAC 404/403 semantics are explicit.
  • Provider boundary handling distinguishes platform route truth from Microsoft tenant ID terminology.
  • Test governance is explicit and bounded.

Filament / Laravel

  • Filament v5 / Livewire v4 compliance is explicitly stated.
  • Provider registration location is apps/platform/bootstrap/providers.php.
  • Global search impact for retired resources is called out.
  • Destructive-action confirmation and server authorization expectations are preserved.
  • Asset strategy is unchanged unless implementation discovers otherwise.
  • Testing plan names Filament/Page/Action/Guard proof surfaces.

Implementation Readiness

  • spec.md exists.
  • plan.md exists.
  • tasks.md exists.
  • research.md exists.
  • data-model.md exists and says no persistence changes are planned.
  • quickstart.md exists.
  • legacy-surface-audit.md exists with initial prep findings and refresh requirements.
  • Logical route/link contract exists.
  • Tasks are ordered, small, and verifiable.

Open Items For Implementation

  • Refresh legacy-surface-audit.md after branch/session setup.
  • Determine whether an existing managed-environment link helper can be extended.
  • Determine the exact TenantResource retirement mechanism.
  • Determine whether any old /admin/tenants... URL has safe canonical resolution; default remains 404.