ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
platform-dev
TenantAtlas/specs/298-managed-environment-terminology-copy-cleanup/checklists/requirements.md
ahmido 5722c4f051 feat: clean up managed environment terminology copy (#353) 
## Summary
- replace tenant-first operator copy with environment and managed environment terminology across Filament pages, resources, services, Blade views, and localization
- align baseline compare, findings, governance, monitoring, backup schedule, and required-permissions surfaces with the managed-environment vocabulary
- update guard, feature, and browser smoke coverage and add the Spec 298 audit artifacts documenting allowed provider, internal, and regression-guard tenant references

## Validation
- cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Guards
- cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Localization
- cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/Workspaces
- cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/ProviderConnections
- cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Feature/RequiredPermissions
- cd apps/platform && ./vendor/bin/sail artisan test --compact tests/Browser/Spec190BaselineCompareMatrixSmokeTest.php tests/Browser/Spec281ProviderConnectionScopeSmokeTest.php tests/Browser/Spec285WorkspaceRbacEnvironmentAccessSmokeTest.php tests/Browser/Dashboard/TenantDashboardProductizationSmokeTest.php
- cd apps/platform && ./vendor/bin/sail bin pint --dirty --format agent

## Notes
- Filament remains on Livewire v4.
- No panel provider or asset-strategy changes are included in this branch.
- Existing destructive actions retain their confirmation and authorization behavior.

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #353
2026-05-13 09:34:08 +00:00

4.5 KiB
Raw Permalink Blame History

Requirements Checklist: Managed Environment Terminology & Copy Cleanup

Purpose: Validate that Spec 298 preparation is bounded, implementation-ready, and constitution-aligned.
Created: 2026-05-13
Feature: spec.md

Applicability And Low-Impact Gate

  • CHK001 The change explicitly affects operator-facing copy, localization values, tests, guards, and possible browser smoke anchors.
  • CHK002 The spec, plan, and tasks carry the same native/custom classification, shared-family relevance, state-layer ownership, and exception policy.

Native, Shared-Family, And State Ownership

  • CHK003 The scope keeps existing Laravel/Filament/Blade surfaces and does not introduce a new custom UI system.
  • CHK004 No shared-detail or shared-family surface is replaced; labels and selectors are updated in place.
  • CHK005 Copy/value, page/action label, view text, test helper wording, guard regex descriptions, and browser selectors are named as separate state layers.
  • CHK006 Existing action hierarchy and inspect/open models remain unchanged unless an affected label needs a noun update.

Shared Pattern Reuse

  • CHK007 The cross-cutting interaction classes are explicitly marked: localization, shell/context copy, action labels, guard tests, and browser anchors.
  • CHK008 The existing shared paths are named: localization arrays, ManagedEnvironmentLinks, setAdminEnvironmentContext(), and current guard/browser patterns.
  • CHK009 No parallel operator-facing vocabulary framework is introduced.

OperationRun Start UX Contract

  • CHK010 The spec states that no new OperationRun start/completion/link behavior is introduced.
  • CHK011 Existing OperationRun UX/link contracts remain the owner if copy around operations is touched.
  • CHK012 No queued DB notification or terminal notification behavior changes are planned.

Provider Boundary And Vocabulary

  • CHK013 Provider-owned terms such as Microsoft tenant ID and Entra tenant ID are allowed only when the external provider is the subject.
  • CHK014 Generic platform/operator vocabulary is required to use workspace, managed environment, environment, provider connection, operation, finding, review, evidence, and governance terms.

Signals, Exceptions, And Test Depth

  • CHK015 Repository signals are classified as review-mandatory: final scans, guard literals, browser selector changes, localization value decisions, and destructive action label changes.
  • CHK016 Remaining tenant references must be documented in terminology-audit.md with explicit categories.
  • CHK017 Required surface test profiles are explicit: standard-native-filament, global-context-shell, and targeted browser-smoke only when touched.
  • CHK018 The chosen test lanes are focused and do not require a full-suite repair loop.

Audience-Aware Disclosure And Decision Hierarchy

  • CHK019 Default-visible context copy must be environment-first while provider/raw/support details remain in existing disclosure tiers.
  • CHK020 Customer/read-only paths do not gain raw JSON, copied context payloads, fingerprints, or internal reason ownership.
  • CHK021 The spec does not add new primary actions; it only relabels existing actions where needed.
  • CHK022 Duplicate or contradictory tenant/environment wording is treated as drift to fix or document.

Filament v5 Contract

  • CHK023 Filament v5 / Livewire v4.0+ compliance is explicit.
  • CHK024 Laravel 12 panel provider registration remains in apps/platform/bootstrap/providers.php.
  • CHK025 Globally searchable resource handling is called out for any touched resource.
  • CHK026 Destructive actions that are relabeled must retain ->action(...), ->requiresConfirmation(), and authorization.
  • CHK027 Asset strategy is unchanged unless implementation unexpectedly registers assets, in which case filament:assets is required in deployment notes.
  • CHK028 Testing plan names affected pages/actions/guards/browser anchors.

Review Outcome

  • CHK029 Review outcome class: acceptable-special-case.
  • CHK030 Workflow outcome: keep.
  • CHK031 Final note location: active feature PR close-out entry Guardrail / Terminology Cleanup / Smoke Coverage.

Notes

  • This is a cleanup spec, not a broad rename or localization foundation.
  • Remaining provider/internal/historical tenant references are allowed only when categorized in the audit.