STAGE 1: Plan a vertical slice
Concept: A feature is complete across interface, server and data.
Task: Choose browse-and-register as the first slice; write its user flow and acceptance scenarios.
Acceptance: Keep payments and sensitive identity collection outside this practice project.

My assumptions:

My work / file link:

My checks and results:

What I changed:


STAGE 2: Connect the layers
Concept: Each boundary needs validation and a stable contract.
Task: Build or design a registration form, server operation and relational storage.
Acceptance: Client-side validation does not replace server-side checks.

My assumptions:

My work / file link:

My checks and results:

What I changed:


STAGE 3: Handle failure states
Concept: Users need useful feedback when a request fails.
Task: Design full, duplicate, unavailable and invalid-input states.
Acceptance: The interface does not show success until the server confirms it.

My assumptions:

My work / file link:

My checks and results:

What I changed:


STAGE 4: Test the journey
Concept: End-to-end evidence complements unit tests.
Task: Run or specify complete journeys with clean fixtures and record actual results.
Acceptance: Clearly distinguish implemented features from planned features.

My assumptions:

My work / file link:

My checks and results:

What I changed:
