ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
platform-dev
TenantAtlas/specs/330-environment-dashboard-baseline-compare-productization/checklists/requirements.md
ahmido 0c7adefe5b Spec 330: environment dashboard baseline compare productization (#392) 
## Summary
- add the baseline compare landing experience for the environment dashboard productization flow
- expand the environment dashboard overview and summary-building logic to support richer baseline comparison states and assessments
- update the supporting Blade templates for the new compare and overview presentation
- add English and German translations for the baseline compare surface
- include the Spec 330 planning and task artifacts alongside the implementation

## Tests
- touched browser, feature, and unit coverage for the new baseline compare flow
- updated test files include `Spec330EnvironmentDashboardBaselineCompareSmokeTest`, `BaselineCompareLandingWhyNoFindingsTest`, `Spec330EnvironmentDashboardBaselineCompareProductizationTest`, `HeaderContextBarTest`, and `ManagedEnvironmentModelTest`
- no additional test run was performed as part of this commit/push/PR workflow

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #392
2026-05-20 20:32:39 +00:00

2.2 KiB
Raw Permalink Blame History

Spec 330 Requirements Checklist

Purpose: Preparation-quality validation for Spec 330 before runtime implementation. Created: 2026-05-19 Feature: spec.md

Content Quality

  • Spec is focused on user value and decision-first environment governance.
  • No implementation code changes are included in preparation artifacts.
  • Requirements are testable and measurable.
  • Scope is constrained to Environment Dashboard and Baseline Compare productization.
  • Out-of-scope items explicitly exclude new engines, migrations, packages, env vars, queues, scheduler, storage, and broad backend foundation.

Product Requirements

  • Environment Dashboard primary question is defined.
  • Baseline Compare primary question is defined.
  • Decision-first ordering is defined for both surfaces.
  • No false-green language is prohibited unless repo-backed.
  • Diagnostics/raw payload/raw diff are required to be collapsed or secondary by default.
  • Static platform-copy use of tenant is prohibited while dynamic names containing Tenant remain allowed.

Repo Truth

  • Current repo paths were verified and corrected from the input draft where needed.
  • Repo truth map exists and covers required data areas.
  • UI elements are mapped to source, scope, authorization, fallback, and classification.
  • OperationRun, evidence, baseline, and drift links are documented as proof/context rather than broad health certification.

Scope And Routing

  • Both surfaces are specified as environment-owned.
  • Explicit workspace/environment route ownership is required.
  • Remembered environment fallback is rejected as ownership authority.
  • Legacy tenant/context aliases are prohibited.
  • Cross-workspace environment access must be rejected.

Readiness

  • Candidate Selection Gate is documented.
  • Proportionality review is included and identifies no new persisted entity, abstraction, enum/status family, or taxonomy/framework.
  • Implementation phases and validation commands are present.
  • Tests and browser smoke expectations are listed.
  • Follow-up specs are listed but excluded from Spec 330 implementation.