TenantAtlas/specs/325-screenshot-anchored-strategic-target-images/checklists/requirements.md

Requirements Checklist - Spec 325

Purpose: Validate Spec 325 preparation completeness and implementation-readiness. Created: 2026-05-17 Feature: specs/325-screenshot-anchored-strategic-target-images/spec.md

Scope

• Spec remains docs/image target artifact work.
• No product runtime UI is changed by the prepared spec.
• No routes are changed by the prepared spec.
• No Filament/Livewire/Blade runtime files are changed by the prepared spec.
• No business logic is changed by the prepared spec.
• No database schema is changed by the prepared spec.

Selection

• Selected surfaces must come from Spec 323 artifacts.
• No more than 10 surfaces may be selected.
• P0/P1 rationale is required.
• Deferred strategic surfaces are required.

Screenshot Anchoring

• Every selected surface must reference a current screenshot and/or page report.
• Every brief must describe concrete current-state problems.
• Every target image must have source/brief/sidecar.
• No target image may be accepted as standalone truth.

Target Briefs

• Every selected surface requires a target experience brief.
• User promise is required.
• Primary persona is required.
• First-five-seconds target is required.
• Primary decision is required.
• Primary action is required.
• Information hierarchy is required.
• Main view / detail drawer / advanced split is required.
• Visual target direction is required.
• Status/trust model is required.
• Repo-truth classifications are required.
• Image generation prompt is required.
• Implementation pattern requirements are required.

Target Images

• Every selected surface requires at least one target image.
• Customer/auditor/management-facing surfaces require light target image or documented reason.
• Target images must be screenshot-anchored.
• Target images must not be generic SaaS dashboards.
• Target images must not imply false product truth.
• Target images must not present conceptual-future-state as implemented.
• Target images must avoid fake green success.
• Target images must be readable and reviewable.

Customer / Risk

• Customer-facing surfaces must be customer-safe.
• Dangerous actions must include guardrail concepts.
• Evidence/audit paths must be represented where relevant.
• Technical diagnostics must be secondary.

Coverage Artifacts

• Strategic surfaces file update is required.
• Design coverage matrix update is required if target-image coverage is tracked.
• Grouped follow-up candidates update is required.
• Follow-up implementation candidates creation is required.
• README links to artifacts are required.

Validation

• bash scripts/check-ui-productization-coverage HEAD is required during implementation.
• git diff --check is required during implementation.
• Full Pest/runtime suite must be intentionally not run unless runtime files changed.
• Pint must be intentionally not run unless PHP files changed.

Candidate Selection Gate

• Candidate is directly user-provided.
• Candidate aligns with Spec 323/324 product direction.
• Existing related completed specs are treated as historical context only.
• Existing specs/325-tenantial-strategic-surface-target-mockups/ contains no tracked completed spec artifacts.
• Scope is bounded to a small docs/image target-artifact slice.
• Adjacent pattern-library work is deferred to Spec 326.

Spec Readiness Gate

• spec.md exists.
• plan.md exists.
• tasks.md exists.
• checklists/requirements.md exists.
• Problem statement, user value, functional requirements, non-goals, acceptance criteria, risks, and assumptions are present.
• Plan identifies affected repo surfaces and no-runtime constraints.
• Tasks are ordered, small, and verifiable.
• Workspace/environment context, RBAC/customer-safety, audit/evidence, OperationRun truth, and dangerous-action UX expectations are addressed where relevant.
• No open question blocks safe implementation.