ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
platform-dev
TenantAtlas/specs/355-platform-sellable-smoke-matrix/checklists/requirements.md
ahmido f35782a163 feat: platform sellable smoke matrix (spec 355) (#426) 
Added artifacts, screenshots, and documentation for the platform sellable smoke matrix. Fixed a bug in FindingRiskGovernanceResolver and updated related tests.

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #426
2026-06-05 10:42:31 +00:00

2.5 KiB
Raw Permalink Blame History

Requirements Checklist: Spec 355 - Platform Sellable Smoke Matrix

Purpose: Validate preparation readiness only. This checklist does not certify implementation, runtime tests, or browser proof.

Candidate And Guardrail

  • CHK001 The candidate source is explicit: direct user-provided Spec 355 draft plus current operator-surface repo truth.
  • CHK002 No completed spec package is being reopened or normalized back to preparation state.
  • CHK003 The selected slice stays verification-first and does not expand into portal, renderer, AI, workflow-engine, or navigation-rewrite scope.

Repo Truth Alignment

  • CHK004 The prep names the exact current owner surfaces instead of inventing new sellable-readiness pages.
  • CHK005 The prep records the dependency ambiguity across Specs 351-354 explicitly and turns it into a first-phase implementation gate.
  • CHK006 Existing smoke helpers and browser-test history are captured as context rather than being treated as automatic proof for Spec 355.
  • CHK007 Evidence Overview and operation detail coverage gaps are recorded instead of being hidden behind a broad "already audited" claim.

Constitution And Scope

  • CHK008 The spec forbids new persistence, a new readiness entity, a new workflow engine, a new provider framework, and broad surface rewrites.
  • CHK009 Provider/platform boundary handling is explicit and keeps Spec 355 in verification mode rather than broadening shared seams.
  • CHK010 Existing RBAC, audit, and OperationRun ownership remain explicit and unchanged.
  • CHK011 UI/Productization coverage is explicit for all in-scope strategic surfaces.

Artifact And Task Readiness

  • CHK012 The smoke matrix artifact exists with the required columns and required flow rows.
  • CHK013 The readiness report artifact exists with the required executive-summary sections.
  • CHK014 The tasks are ordered, verifiable, and include repo state, fixture inventory, browser flows, classification, optional minimal fixes, and final regression work.
  • CHK015 No blocking preparation question remains; runtime dependency and fixture uncertainty are surfaced as explicit implementation gates, not silent assumptions.

Review Outcome

  • Ready for implementation prep handoff.
  • Main caveat recorded: final readiness classification remains gated on dependency re-verification and honest fixture availability during implementation.
  • This checklist validates preparation only. No application implementation, runtime test execution, or browser smoke has been performed in this prep step.