ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
platform-dev
TenantAtlas/specs/352-environment-dashboard-operator-guidance-consolidation/checklists/requirements.md
ahmido 9a564d6bf2 feat: environment dashboard operator guidance consolidation (spec 352) (#423) 
Implemented the consolidated operator guidance panel for the environment dashboard. Updated EnvironmentDashboardSummaryBuilder to prioritize and select guidance based on the operator guidance contract. Added comprehensive unit, feature, and browser tests to verify the guidance selection logic and UI rendering.

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #423
2026-06-04 12:56:02 +00:00

4.0 KiB
Raw Permalink Blame History

Requirements Checklist: Spec 352 - Environment Dashboard Operator Guidance Consolidation

Purpose: Validate that Spec 352 is bounded, repo-based, constitution-aligned, and ready for a later implementation loop.
Created: 2026-06-04
Feature: specs/352-environment-dashboard-operator-guidance-consolidation/spec.md

Candidate Selection And Guardrail

  • CHK001 The package names the direct user-provided Spec 352 draft as the candidate source and records that this is a manual promotion rather than an automatic next-best-prep selection from docs/product/spec-candidates.md.
  • CHK002 Spec 330 is treated as implemented historical context only and is not reopened or normalized.
  • CHK003 Specs 338, 350, and 351 are treated as dependency context only and are not rewritten or converted back into preparation-only wording.
  • CHK003A Spec 346 is treated as adjacent governance-owner dependency context only and is neither reopened nor closed by this prep package.
  • CHK004 The prep explicitly records that Spec 351 has repo-real action semantics but still carries residual browser-audit observations that stay out of scope for this dashboard follow-up.
  • CHK005 The scope is narrowed to the existing Environment Dashboard only; Baseline Compare, Governance Inbox, provider redesign, backup/restore follow-through, portal, PDF, PSA, and AI remain deferred.

Repo Truth And Architecture

  • CHK006 The spec and plan anchor the work to EnvironmentDashboard, EnvironmentDashboardSummaryBuilder, EnvironmentDashboardSummary, and the existing dashboard Blade view.
  • CHK007 The artifacts record that the current dashboard already has recommendedActions, readinessDecision, readiness dimensions, proof panels, and supporting signals.
  • CHK008 The repo-truth map documents the current recommendedActions() ranking and the absence of an explicit dashboard operatorGuidance contract.
  • CHK009 The contract note keeps any new guidance payload derived-only and request-scoped; no new persistence is introduced.
  • CHK010 The plan forbids a generic new dashboard/workflow/provider framework and allows only a bounded page-local helper if necessary.

UI/Productization Coverage

  • CHK011 UI Surface Impact is explicit and limited to the existing Environment Dashboard surface.
  • CHK012 UI/Productization Coverage reuses the existing UI-002 Environment Dashboard page report and does not invent a new route taxonomy.
  • CHK013 The spec requires one dominant primary action, subordinate secondary links, and a calm No urgent operator action fallback.
  • CHK014 The spec and plan preserve current readiness dimensions, proof items, supporting signals, and collapsed diagnostics as secondary context.

Testing And Validation

  • CHK015 Planned tests cover deterministic guidance selection, provider-priority behavior, review-output reuse, environment scope, and calm no-action rendering.
  • CHK016 Validation commands explicitly rerun Environment Dashboard plus Spec 330, Spec 350, Spec 351, and ResolutionGuidance regressions.
  • CHK017 The artifacts include pint --dirty and git diff --check as final validation steps.

Readiness Gate

  • CHK018 Candidate Selection Gate passes: the candidate is direct user input, not already specced as 352, and is scoped as a narrow follow-up over current repo truth.
  • CHK019 Spec Readiness Gate passes: spec.md, plan.md, tasks.md, repo-truth-map.md, and a bounded contract note exist and are aligned.
  • CHK020 No blocking product question remains; the remaining work is bounded implementation and later verification of the exact dominant-case behavior per fixture.
  • CHK021 No application implementation has been performed in this preparation step.

Notes

  • The package is intentionally framed as a Spec 330 follow-up rather than a fresh dashboard productization effort.
  • The package is intentionally navigation-first and must not use the dashboard to hide unresolved owner-surface behavior or to execute new high-impact actions directly.