Production Frontend

Build a robust application UI with forms, server-state synchronization, and deliberate state boundaries.

Required deliverables

Constraints

Non-happy states are first-class.
Query keys are systematic.
Repository abstraction is added only where it solves a concrete coupling/testability problem.

Execution sequence

Build without following a transcript

01
Write acceptance criteria and a boundary diagram before implementation.
02
Create a clean checkpoint/branch and inventory the existing files, routes, database objects, and configuration you are allowed to change.
03
Build one vertical slice that reaches an observable result end-to-end before broadening the feature.
04
Add the remaining required behavior incrementally. After each coherent change, run the narrowest verification and inspect the output.
05
Exercise at least two non-happy paths: malformed/missing input, authorization failure, network/database failure, race condition, or configuration error as applicable.
06
Run the full milestone quality gate and record results.
07
Perform a closed-reference rebuild or architecture walkthrough. Document trade-offs and one deliberate non-goal.

Evidence packet

Repository/file-tree diff

commands and exit status

browser/API/database evidence

one controlled failure + diagnosis

tests/quality-gate result

short architecture decision note

Review rubric

Required behavior works and failure paths are deliberate.

Responsibilities and dependency direction match the course model.

Claims are backed by repeatable commands, requests, tests, or stored data.

At least one failure is reproduced, isolated, fixed, and reverified.

The final feature can be explained or partly rebuilt without copying the reference.

Milestone progress

A milestone is complete when the deliverables, failure testing, and review rubric are satisfied without following a transcript.