ahmido
a9c54205bf
Implemented the accepted risk resolution guidance, including the AcceptedRiskResolutionAdapter, guidance cards, and updated related Filament views. Added unit, feature, and browser tests. Co-authored-by: Ahmed Darrazi <ahmed.darrazi@live.de> Reviewed-on: #425
37 lines
2.3 KiB
Markdown
37 lines
2.3 KiB
Markdown
# Requirements Checklist: Spec 354 - Finding Exceptions / Accepted Risk Resolution Guidance v1
|
|
|
|
Purpose: Validate preparation readiness only. This checklist does not certify implementation, runtime tests, or browser proof.
|
|
|
|
## Candidate And Guardrail
|
|
|
|
- [x] CHK001 The candidate source is explicit: direct user draft plus repo-real accepted-risk follow-up materials.
|
|
- [x] CHK002 No completed spec package is being reopened or normalized back to preparation state.
|
|
- [x] CHK003 The selected slice is narrower than a broad governance-workbench, portal, or GRC rebuild and fits the post-Spec-353 follow-through need.
|
|
|
|
## Repo Truth Alignment
|
|
|
|
- [x] CHK004 The prep records the exact current accepted-risk owner surfaces instead of inventing new queue/detail pages.
|
|
- [x] CHK005 Existing `FindingRiskGovernanceResolver` truth is named explicitly as the primary guidance source.
|
|
- [x] CHK006 Existing customer-safe accepted-risk wording in downstream review-output surfaces is treated as continuity context, not a new owner surface.
|
|
- [x] CHK007 Existing queue audit coverage (`ui-012`) is carried forward as the strategic productization proof source.
|
|
|
|
## Constitution And Scope
|
|
|
|
- [x] CHK008 The spec forbids new persistence, a new workflow engine, a new review-impact framework, and a broader portal/workbench rewrite.
|
|
- [x] CHK009 Provider/platform boundary handling is explicit and keeps this slice platform-core and governance-owned.
|
|
- [x] CHK010 Existing capability, audit, and `OperationRun` ownership remain explicit.
|
|
- [x] CHK011 UI/Productization coverage is explicit for queue and detail surfaces.
|
|
|
|
## Test Governance And Readiness
|
|
|
|
- [x] CHK012 Unit, Feature/Livewire, and Browser coverage are named in the narrowest honest mix.
|
|
- [x] CHK013 The plan names concrete runtime seams and likely touched files instead of relying on vague architecture intent.
|
|
- [x] CHK014 The tasks are ordered, verifiable, and scoped to this slice only.
|
|
- [x] CHK015 No open question blocks a bounded implementation loop.
|
|
|
|
## Review Outcome
|
|
|
|
- [x] Ready for implementation prep handoff.
|
|
- [x] Main caveat recorded: any stale-governance case based on finding-change timestamps is conditional and must be omitted if repo proof is weak.
|
|
- [x] This checklist validates preparation only. No application implementation, runtime test execution, or browser smoke has been performed in this prep step.
|