# Requirements Checklist: Spec 337 - Evidence Path / Review Pack Product Process Flow Alignment

Purpose: validate the prepared spec artifacts before runtime implementation begins.

## Spec Identity

- [x] Spec number is reconciled to current repo state (`337`, because `336` already exists).
- [x] Branch name matches spec directory.
- [x] Input source and numbering reconciliation are documented.
- [x] Runtime posture forbids backend evidence/report/review-pack/export engine rewrites.

## Constitution / Spec Candidate Gate

- [x] Spec Candidate Check is completed.
- [x] Problem, today's failure, user-visible improvement, smallest version, non-goals, complexity, why-now, why-not-local, approval class, red flags, score, and decision are filled.
- [x] Proportionality review is included for the possible derived presenter.
- [x] No new persisted truth, enum family, lifecycle family, or generic workflow framework is proposed.
- [x] Shared pattern first is explicit through Spec 332 Product Process Flow reuse.

## Repo Truth

- [x] `repo-truth-map.md` exists.
- [x] Evidence snapshot source is classified.
- [x] Stored report source is classified.
- [x] Review pack source is classified.
- [x] Environment review / Customer Review Workspace relationship is classified.
- [x] OperationRun proof relationship is classified.
- [x] Export/download artifact relationship is classified.
- [x] Evidence freshness source is classified.
- [x] Customer-safe state source is classified.
- [x] RBAC/capabilities and routes/surfaces are classified.
- [x] Existing tests are listed.
- [x] Unavailable/deferred states are called out instead of invented.

## State Contract

- [x] `evidence-review-pack-state-contract.md` exists.
- [x] Default flow steps are defined.
- [x] Presentation vocabulary is explicitly not a new enum family.
- [x] Missing, generating, failed, stale, report missing, review-pack required, review-pack generating, review-pack failed, customer-safe review required, customer-safe ready, export available, and export unavailable states are covered.
- [x] Each state includes visible status, reason, impact, primary next action, flow gate states, proof, customer-safe state, export state, and diagnostics default.
- [x] False customer-safe, auditor-ready, complete, and export-ready claims are forbidden.

## UI / Filament Guardrails

- [x] UI Surface Impact is completed and does not claim "No UI surface impact".
- [x] UI/Productization Coverage is completed.
- [x] Decision-first surface role is completed.
- [x] Audience-aware disclosure is completed.
- [x] UI/UX surface classification is completed.
- [x] Operator surface contract is completed.
- [x] Livewire v4 / Filament v5 posture is explicit.
- [x] Provider registration location remains `apps/platform/bootstrap/providers.php`.
- [x] Global search state is addressed for relevant resources.
- [x] No new destructive actions are proposed.
- [x] Asset/deployment posture is explicit: no global asset or `filament:assets` change expected.

## Testing / Validation

- [x] Feature test file path is specified.
- [x] Browser smoke file path is specified.
- [x] Required screenshots path and filenames are specified.
- [x] Required assertions cover missing evidence, report missing, review-pack required, review-pack available, OperationRun proof, RBAC/context, collapsed diagnostics, and no raw JSON.
- [x] Validation commands are listed.
- [x] Unreachable browser states must be documented rather than faked.

## Implementation Readiness

- [x] `spec.md`, `plan.md`, `tasks.md`, `repo-truth-map.md`, `evidence-review-pack-state-contract.md`, `checklists/requirements.md`, and screenshot directory are present.
- [x] Runtime implementation has not started in this preparation step.
- [x] Recommended next prompt is implementation, not more preparation.