Docs Work Items Eng R1 001 P0 Eng R1 001 Design Spec

Canonical source: docs/work-items/ENG-R1-001/P0-ENG-R1-001-DESIGN-SPEC.md · Snapshot commit: b9df7479add1

ENG-R1-001 — task design specification

• Task ID: ENG-R1-001
• Artifact kind: design
• Artifact state: draft
• Roadmap status: Backlog
• Milestone: R1
• Execution allowed: false
• Evidence boundary: Creation of this draft does not approve implementation, deployment, testing, restore, release, or production use.

Design inputs

• docs/product/releases/PRD-R1-MANUAL-JOURNAL-ARCHIVE.md
• docs/council/UX-DESIGN-REVIEW.md
• docs/design/UX-SPECIFICATION.md
• prototypes/calendar-ui/index-v5.html
• docs/council/execution/P0-PHASE1-TASK-DEFINITION-OF-READY.md

Experience objective

Specify every human-facing, operator-facing, status, error, privacy, recovery, and accessibility consequence of Manual Upload & Reflection Core without treating shared specifications or prototypes as task approval.

Required state family

• normal and success;
• empty and never-run;
• loading and long-running;
• validation and dependency error;
• interruption, timeout, retry, and stale result;
• denied, expired, blocked, unavailable, and not-configured prerequisite;
• destructive, spend-bearing, migration, recovery, and rollback states where applicable;
• wide, compact, 320 px, 200% text, 400% page zoom, landscape, light/dark theme, and reduced-motion behavior; and
• keyboard order, focus entry/return, semantic names, live-region behavior, non-color cues, target size, contrast, and screen-reader reading order.

Task traceability

• Outcome: Implement durable explicit-date text upload, duplicate override, Calendar, and authentic Journal Day display.
• Requirement IDs: LID-SCP-002, LID-SCP-003, LID-UP-001, LID-UP-002, LID-UP-003, LID-REF-001, LID-REF-004, LID-REF-005, LID-REF-006, LID-OPS-011, LID-OPS-018
• Parent design sources: docs/council/UX-DESIGN-REVIEW.md, docs/design/UX-SPECIFICATION.md, prototypes/calendar-ui/index-v5.html
• Prototype boundary: frozen prototypes are interaction inputs only; they do not prove runtime auth, persistence, privacy, recovery, accessibility conformance, or production behavior.

Design verification scenarios

1. ENG-R1-001-D-001 — Complete states: the applicable state family above is specified with exact content and permitted actions.
2. ENG-R1-001-D-002 — Responsive/accessibility: the task remains understandable and operable across the named responsive, keyboard, focus, screen-reader, contrast, zoom, theme, and motion conditions.
3. ENG-R1-001-D-003 — Truth/privacy: copy never claims success before durable evidence, never confuses backup with restore, and never exposes authentic/private data in review artifacts.

Open design decisions

• Exact task-specific journeys, layouts, components, content, and state applicability require Designer review.
• Architecture-dependent timing, evidence sources, recovery, failure, and maintenance facts remain provisional until the technical plan is approved.
• Any not-applicable decision requires a concrete rationale and explicit Designer/council concurrence; this draft does not assert it.

UI/UX Designer disposition

Draft / Hold. Shared UX and prototype sources are inputs. Substantive implementation cannot start until the task-specific design contract is approved or validly marked not applicable.