ahmido/TenantAtlas
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects 1 Releases Wiki Activity
platform-dev
TenantAtlas/specs/361-report-evidence-reconciliation/checklists/requirements.md
ahmido 252cd4513d feat: implement report evidence reconciliation (#432) 
Implemented report evidence reconciliation.

Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de>
Reviewed-on: #432
2026-06-06 22:40:59 +00:00

4.7 KiB
Raw Permalink Blame History

Requirements Checklist: Spec 361 - Report and Evidence Reconciliation Adapters

Purpose: Preparation analysis for Spec 361 readiness
Created: 2026-06-06
Feature: /Users/ahmeddarrazi/Documents/projects/wt-plattform/specs/361-report-evidence-reconciliation/spec.md

Candidate Selection And Guardrails

  • CHK001 The candidate source is explicit: direct user-provided Spec 361 draft from the attached pasted-text.txt.
  • CHK002 No specs/361-* package existed before Spec Kit branch creation.
  • CHK003 The active candidate queue's no safe automatic next-best-prep target note is respected; this package is an intentional manual promotion, not an auto-selected queue item.
  • CHK004 Related specs were checked and treated correctly: Spec 358 is queue-truth context, Spec 359 is merged adapter baseline, Spec 360 is canonical-cutover context, and Specs 347/349/351/356/357 are review-pack or rendered-report context only.
  • CHK005 Repo-truth deviations from the user draft are recorded in spec.md, especially the narrowed safe scope around EvidenceSnapshot and ReviewPack plus the explicit defer/fail-closed treatment for generic StoredReport families.

Required Prep Artifacts

  • CHK006 spec.md exists and contains no template placeholders.
  • CHK007 plan.md exists and is repo-aware.
  • CHK008 tasks.md exists and is ordered, small, and verifiable.
  • CHK009 This checklist exists.

Spec Quality

  • CHK010 Spec Candidate Check is completed and scores above the approval threshold.
  • CHK011 The spec keeps OperationRun, EvidenceSnapshot, ReviewPack, and StoredReport persistence unchanged.
  • CHK012 The spec explains why bounded adapter extension is justified now under ABSTR-001: the repo already has real adapter-backed reconciliation consumers.
  • CHK013 The spec keeps scope bounded to evidence reconciliation, review-pack reconciliation, and honest unsupported generic report-family handling.
  • CHK014 The proportionality review rejects a generic report-artifact engine, new operation types, new persistence, and weak "latest artifact exists" heuristics.

Plan / Task Alignment

  • CHK015 The plan identifies the actual repo surfaces likely to change, including the current registry, write seam, artifact models, artifact-truth presenters, and operations/detail pages.
  • CHK016 The plan keeps Filament v5 / Livewire v4 posture and provider-registration location visible.
  • CHK017 The plan explicitly states that no migration, no new panel/provider, no new global search change, and no new asset strategy are expected.
  • CHK018 The tasks start with repo truth and failing tests before runtime edits.
  • CHK019 The tasks include explicit anti-creep guardrails against new persistence, new operation types, generic stored-report heuristics, and rendered-report scope creep.

UI / Monitoring / Artifact Coverage

  • CHK020 UI Surface Impact is completed and does not claim a new page family.
  • CHK021 The changed surfaces are correctly classified as existing operations monitoring/detail plus existing artifact detail follow-through, not a new strategic customer-facing page.
  • CHK022 No new page-report identity or route-inventory expansion is required unless implementation proves a materially new visible hierarchy.
  • CHK023 Audience-aware disclosure and no-overclaim wording boundaries are explicit for both operations and artifact detail surfaces.

Test Governance

  • CHK024 The declared test families are the narrowest honest proof: Unit + Feature + one bounded Browser smoke.
  • CHK025 No heavy-governance family or PGSQL-only schema lane is introduced by default.
  • CHK026 Planned validation commands are explicit, partitioned into primary merge gate and contextual artifact regressions, and remain scoped to Spec 361 plus directly adjacent evidence/review-pack coverage.

Readiness Gate Outcome

  • CHK027 Candidate Selection Gate passes.
  • CHK028 Spec Readiness Gate passes.
  • CHK029 Runtime implementation has not started in this preparation step.
  • CHK030 Recommended next step is implementation, not more prep.

Review Outcome

  • Outcome class: acceptable-special-case
  • Workflow outcome: keep
  • Final note location: active feature PR close-out entry Guardrail / Smoke Coverage
  • Preparation analyze result: pass via repo-based cross-artifact review; no standalone local speckit.tasks or speckit.analyze generator command was exposed in this repo surface beyond prompts and agent instructions
  • Tooling note: Spec Kit branch/spec creation succeeded via create-new-feature.sh, setup-plan.sh generated the plan file, and tasks.md plus this checklist were authored manually to match the repo's Spec Kit templates and agent instructions