# Requirements Checklist: Spec 395 - Product Surface Contract Enforcement and Surface Reduction Gate v1

**Purpose**: Validate preparation readiness for Spec 395 before implementation.
**Created**: 2026-06-21
**Feature**: `specs/395-product-surface-gate/spec.md`

## Spec Quality

- [x] CHK001 The selected candidate is directly provided by the user as Spec 395 and is not inferred from the automatic candidate queue.
- [x] CHK002 The completed-spec guardrail treats Specs 370, 375, and 377 as completed context only and does not reopen or rewrite their history.
- [x] CHK003 The spec states the concrete product problem: UI-affecting work can pass technically while expanding operator surface area, duplicating truth, exposing raw details, or skipping human/browser review.
- [x] CHK004 The spec defines the smallest enterprise-capable slice: a workflow/contract/guardrail gate with targeted tests, not a broad runtime redesign.
- [x] CHK005 Functional requirements are testable through documentation/template/guard assertions.
- [x] CHK006 Out-of-scope boundaries exclude broad page redesign, runtime Product Surface frameworks, migrations, models, routes, Filament page/resource changes, and browser visual regression infrastructure.
- [x] CHK007 Risks, assumptions, and follow-up candidates are recorded.

## Constitution And Guardrails

- [x] CHK008 UI Surface Impact is completed as `No UI surface impact` for the default slice with a rationale.
- [x] CHK009 Product Surface Impact requires future UI-affecting specs to declare page archetype, surface budget, technical demotion, browser proof, human sanity, and exception handling.
- [x] CHK010 Cross-cutting shared pattern reuse names existing UI bloat/productization guards and avoids a runtime UI framework.
- [x] CHK011 OperationRun UX impact states no OperationRun behavior is touched and future OperationRun links should be demoted by default.
- [x] CHK012 Provider boundary treatment keeps provider-specific terms in Technical Annex/provider diagnostics, not platform-core product vocabulary.
- [x] CHK013 Proportionality review justifies a narrow workflow gate and rejects full redesign, visual regression, and runtime taxonomy/framework work.
- [x] CHK014 RBAC, workspace/tenant isolation, auditability, and data minimization are addressed as no-runtime-impact constraints.
- [x] CHK015 Test governance names `surface-guard` / heavy-governance ownership and forbids hidden browser/DB fixture cost.
- [x] CHK016 Filament v5 / Livewire v4 compliance, provider registration, global search, destructive action, asset, testing, and deployment posture are stated in the plan.

## Task Readiness

- [x] CHK017 `tasks.md` includes repo-truth and completed-spec source verification before implementation edits.
- [x] CHK018 `tasks.md` includes canonical contract/documentation tasks before template references.
- [x] CHK019 `tasks.md` includes Spec Kit template, AGENTS, and PR checklist gate tasks.
- [x] CHK020 `tasks.md` includes targeted guard-test and lane-registration tasks.
- [x] CHK021 `tasks.md` includes a stop-before-runtime-UI-change boundary and follow-up-candidate path.
- [x] CHK022 `tasks.md` includes validation, browser/no-browser rationale, human sanity, and implementation-report tasks.
- [x] CHK023 `tasks.md` includes explicit non-goals to prevent runtime UI redesign creep.

## Preparation Outcome

- [x] CHK024 Candidate Selection Gate result: pass for a user-provided explicit candidate.
- [x] CHK025 Spec Readiness Gate result: pass for preparation.
- [x] CHK026 Plan Readiness Gate result: pass for preparation.
- [x] CHK027 Tasks Readiness Gate result: pass for implementation handoff.
- [x] CHK028 Workflow outcome: keep as prepared, implementation not started.

## Notes

This checklist validates preparation only. It does not claim Product Surface Contract implementation, guard-test execution, PR-template enforcement, browser verification, human sanity review, or runtime UI reduction.