ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
platform-dev
TenantAtlas/specs/357-report-profiles-disclosure-policy-v1/checklists/requirements.md
ahmido b7907bd69d feat: add report profile and disclosure policy to rendered review reports (#428) 
Implementing report profiles and disclosure policy as per spec 357.

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #428
2026-06-06 09:41:19 +00:00

3.2 KiB
Raw Permalink Blame History

Requirements Checklist: Spec 357 - Report Profiles & Disclosure Policy v1

Purpose: Confirm Spec 357 is selected safely, scoped narrowly, and ready for a later implementation loop.
Created: 2026-06-05
Feature: /Users/ahmeddarrazi/Documents/projects/wt-plattform/specs/357-report-profiles-disclosure-policy-v1/spec.md

Candidate Selection

  • CHK001 The candidate is directly provided by the user and is also a repo-real follow-up over current rendered-report truth.
  • CHK002 No specs/357-* package existed before this preparation run.
  • CHK003 Related specs 347, 355, and 356 were checked for completed/prepared/runtime signals and are treated as context only.
  • CHK004 Close alternatives are deferred instead of hidden inside the primary scope: billing/subscription truth, localization adoption, governance-artifact lifecycle, first AI runtime consumer, and customer-portal consumption.
  • CHK005 The selected slice is bounded to static profile/disclosure policy plus the existing rendered-report family.

Spec Completeness

  • CHK006 spec.md defines problem, user-visible improvement, smallest viable version, explicit non-goals, and why-now rationale.
  • CHK007 The Spec Candidate Check is filled and scored above the approval threshold.
  • CHK008 Scope, routes, data ownership, RBAC, and canonical-view filter/entitlement rules are explicit.
  • CHK009 UI Surface Impact and UI/Productization Coverage are completed for the existing strategic report surfaces.
  • CHK010 Cross-cutting reuse, OperationRun posture, provider-boundary check, proportionality review, testing impact, user stories, and acceptance criteria are all explicit.
  • CHK011 No template placeholders ([FEATURE], [DATE], NEEDS CLARIFICATION) remain in spec.md.

Plan Quality

  • CHK012 plan.md is repo-aware and names the existing runtime seams to extend.
  • CHK013 The plan keeps the slice inside the current ReviewPack rendered-report family and forbids new persistence, delivery workflow, PDF stack, portal, and AI scope.
  • CHK014 Livewire v4 posture, Filament provider location, and current global-search/no-new-panel expectations are explicit.
  • CHK015 The plan distinguishes repo-real truth, current gaps, technical approach, authorization posture, and rollout impact clearly enough for implementation.
  • CHK016 The plan declares Unit + Feature + one bounded Browser smoke as the narrowest honest validation mix.

Task Quality

  • CHK017 tasks.md exists and is ordered into small, verifiable phases.
  • CHK018 Tasks start with repo truth and failing tests before behavior changes.
  • CHK019 Tasks reference concrete repo files or namespaces and avoid speculative architecture.
  • CHK020 Tasks include explicit validation commands, screenshot capture, and git diff --check.
  • CHK021 Tasks explicitly forbid new persistence, delivery workflow, PDF stack, portal, AI, and provider-boundary widening.

Readiness

  • CHK022 spec.md, plan.md, tasks.md, and this checklist exist.
  • CHK023 No open question blocks safe implementation; defaults remain conservative if unanswered.
  • CHK024 The slice is small enough for a bounded implementation loop.
  • CHK025 Result: ready for implementation loop.