ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
platform-dev
TenantAtlas/specs/350-operator-resolution-guidance-framework-v1/checklists/requirements.md
ahmido 4cf2712f92 feat: operator resolution guidance framework v1 (spec 350) (#421) 
Implemented the first version of the operator resolution guidance framework. Added new foundation classes (ResolutionCase, ResolutionAction) and a ReviewPackOutputResolutionAdapter. Updated the Customer Review Workspace and Environment Review Resource to use the new adapter. Added extensive test coverage for the framework and UI integrations.

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #421
2026-06-03 15:35:25 +00:00

3.4 KiB
Raw Permalink Blame History

Requirements Checklist: Spec 350 - Operator Resolution Guidance Framework v1

Purpose: Validate that Spec 350 is bounded, repo-based, constitution-aligned, and ready for a later implementation loop.
Created: 2026-06-03
Feature: specs/350-operator-resolution-guidance-framework-v1/spec.md

Candidate Selection And Guardrail

  • CHK001 The package names the direct user-provided candidate source and its roadmap alignment with customer review, governance inbox, provider readiness, and environment-readiness productization.
  • CHK002 Completed or active related specs are treated as context only and are not reopened or normalized.
  • CHK003 The speculative Spec-347 follow-up number conflict is documented and handled without rewriting historical artifacts.
  • CHK004 The scope is narrowed to a derived contract, one required review-output adapter, and only bounded optional provider/operation adapters rather than a workflow engine or broad platform rebuild.

Repo Truth And Architecture

  • CHK005 The spec and plan explicitly anchor the work to existing guidance producers: review output guidance, operation guidance, operator explanation, primary-next-step helpers, provider readiness summaries, and current strategic consumers.
  • CHK006 The artifacts state that any new case/action contract remains derived-only and request-scoped; no persistence is introduced.
  • CHK007 The plan forbids replacement-by-rewrite of ReviewPackOutputResolutionGuidance, OperationUxPresenter, and OperatorExplanationPattern.
  • CHK008 Optional consumers are bounded explicitly so Governance Inbox, provider readiness, and environment dashboard do not become hidden redesign scope.

UI/Productization Coverage

  • CHK009 UI Surface Impact is explicit and consistent with the intended review-output-first rollout plus bounded optional consumers.
  • CHK010 UI/Productization Coverage reuses the existing page-report identities and target-experience briefs, and it resolves UI-040 / UI-077 through the current audit registry instead of inventing a new audit taxonomy.
  • CHK011 The spec requires one dominant issue and one dominant next action rather than equal-weight warning groups.
  • CHK012 Audience-aware disclosure keeps technical detail, source refs, and raw/support detail secondary.

Testing And Validation

  • CHK013 Planned tests cover the shared contract, the required review-output adapter, the required review-output consumers, and one bounded browser smoke, with optional provider/operation tests only if those adapters are adopted.
  • CHK014 Validation commands explicitly rerun focused regressions for Specs 347 and 349, while treating Spec 346 / Governance Inbox and other non-review consumers as optional regressions only when those consumers are adopted.
  • CHK015 The artifacts name pint --dirty and git diff --check as final validation steps.

Review Outcome

  • CHK016 Review outcome class: documentation-required-exception
  • CHK017 Workflow outcome: keep
  • CHK018 Final note location is the active feature PR close-out entry Guardrail / Smoke Coverage.

Notes

  • This checklist validates preparation readiness only. No application implementation has been performed.
  • The documented exception is the new cross-domain contract itself; it is acceptable only because the spec keeps the implementation derived-only, review-output-first, and bounded to real current consumers.