Phase 23 · Lesson 12

Hands On Lab and Phase Exit

≈ 2 min core reading · 316 source/companion words

Learning contract

What you should be able to do after this

Explain Hands On Lab and Phase Exit without relying on framework buzzwords.
Connect the lesson to the phase outcome: Choose the correct owner for URL state, server state, local UI state, forms, and global client state instead of duplicating everything.
Reproduce the relevant behavior and verify it with evidence.
Diagnose at least one representative failure instead of guessing.

Figure 23.12 — TaskFlow boundary map

classify state

choose authoritative owner

derive values

share only when necessary

avoid synchronization loops

This lesson belongs to Phase 23. Keep the full request/data path visible even when today's code changes only one box.

Instructor workflow: predict first → implement the smallest slice → run it → inspect evidence → break one assumption → diagnose → explain it back. Do not copy the whole code block before understanding the first failing boundary.

Hands-On Lab and Phase Exit Volume 06 - Professional Frontend | Phase 23

Lab 1 - State inventory Create an inventory of every stateful value on the Tasks screen. For each value, record category, authoritative owner, lifetime, reset event, and whether it must survive refresh/navigation.

Lab 2 - Remove one duplicated state path Find code shaped like: query data -> useEffect -> useState -> render

Replace it with: query data -> render

Then verify: - background refetch updates the table - pagination still works - no stale copy remains

Lab 3 - URL-owned filters • Change status/search/page through navigation.

• Refresh the browser and confirm the same view returns.

• Use browser Back/Forward and confirm the query follows the URL.

• Copy the URL into a new tab and confirm the same collection state is reconstructed.

Lab 4 - Workspace architecture Design the next routing shape for multi-workspace TaskFlow. Compare a Context-only active workspace with a route-scoped workspace such as /w/[workspaceSlug]/tasks. Document which state remains canonical and what Context merely distributes.

Phase exit checklist • I can classify state before choosing a hook/library.

• I can explain why query data should not normally be copied into local state.

• I can distinguish form draft state from server state.

• I use URL state for shareable navigation state.

• I keep local UI state close to its interaction owner.

• I know when Context is useful and when it is hiding unclear ownership.

• I derive values instead of synchronizing duplicates.

• I can justify adding a new global state library only with a concrete unsolved problem.

Sources used in this phase

Source Why it matters

React - Sharing State Between Components Single source of truth; lift shared state to the closest common owner.

React - Managing State Avoid redundant/duplicate state; structure state intentionally.

Next.js - useSearchParams URL query state in the App Router.

TanStack Query - Query State / Cache Server-state cache is separate from local UI state.

TanStack Query - SSR/Hydration Request-scoped QueryClient and cache isolation.

Executable lesson studio · state

Now turn the explanation into engineering skill.

Hands On Lab and Phase Exit matters because it changes a real boundary in TaskFlow. The goal is to understand the inputs, owner, observable output, and failure modes before adding more abstraction.

By the end, you should be able to

Explain Hands On Lab and Phase Exit in terms of concrete inputs, ownership, outputs, and evidence.
Implement or reproduce the smallest TaskFlow slice that demonstrates this state concept.
Diagnose one representative state failure using observable evidence instead of trial-and-error.

Figure 23.12B — Mental model

value

owner

lifetime

source of truth

consumer

Read left-to-right while implementing. When debugging, walk right-to-left until the first observed fact differs from your prediction.

Code-along sequence

One coherent change at a time

01
Restate the goal of “Hands On Lab and Phase Exit” as one observable behavior. Write the success signal before touching code.
02
Trace the boundary map: value → owner → lifetime → source of truth → consumer. Mark the one boundary this lesson changes.
03
Inspect the current repository state and record the exact files, route, table, or runtime involved. Avoid creating an abstraction before you can name the existing owner.
04
Implement the smallest vertical slice. Add one coherent change, run the narrowest verification command, and read the output before continuing.
05
Connect the slice to TaskFlow’s phase artifact: A state ownership map for TaskFlow plus refactored examples removing redundant synchronized state.. Verify behavior from the outside as a user or API client would.
06
Create one controlled failure that is safe to reproduce. Predict the symptom first, capture evidence, locate the earliest broken boundary, then fix only that cause.
07
Close the reference and rebuild or explain the core change from memory. Record what you would monitor or test before trusting the same change in production.

txtClassify before choosing a state tool

API task rows       -> TanStack Query
Search/filter URL    -> URL/search params
Create form fields   -> React Hook Form
Dialog open/closed   -> local UI state
Authenticated user  -> auth/session state

Do not copy this as a finished answer. Predict what each boundary does, type the smallest useful slice, run it, then compare the result with your prediction.

Verification

Prove the happy path

Run the narrowest relevant command or request and require a clean exit/status.
Inspect the boundary-specific evidence: terminal output, Network panel, database row/query plan, test report, container health, or deployment logs.
Repeat the behavior once after the change so a one-off cached or stale result cannot masquerade as success.

Break it on purpose

Build debugging memory

Storing derived values that can be computed
Change one assumption in the state example—identity, input, configuration, ordering, connectivity, or state—and predict the exact symptom before running it.

SymptomInvestigation path

Expected result does not appear

Return to the nearest observable boundary: input, network, process log, database, or rendered UI. Compare actual evidence with the predicted path.

A shortcut appears to fix it

Change one variable at a time and reproduce the original failure after the fix; otherwise you have correlation, not diagnosis.

Closed-reference challenge

Can you transfer the idea?

Without copying the final source, create a second small scenario that applies “Hands On Lab and Phase Exit” to a different TaskFlow resource or input. Write the acceptance criteria first, implement it, and provide the evidence that each criterion is satisfied.

Explain-back

Answer these without reopening the solution

What problem does Hands On Lab and Phase Exit solve in TaskFlow, and what would be observably wrong without it?
Which part of the state boundary owns the decision, and which neighboring layer must not own it?
What evidence proves the happy path instead of merely suggesting it worked?
Name one realistic failure or abuse case and the first place you would inspect.
If requirements doubled tomorrow, which part of this design should stay stable and which part is allowed to change?

Lesson studio

Turn the reading into skill

Do it

Create a diagram showing source of truth and allowed data flow for the screen.

Use the smallest change that demonstrates this lesson. Stop after it works and capture evidence.

Break it safely

Storing derived values that can be computed

Predict the symptom before causing the failure. Then locate the earliest boundary where reality diverges from expectation.

Explain it back

Why does this responsibility live here, what input does it trust, what output proves success, and what would go wrong if another layer owned it?

If your explanation is vague, repeat the boundary trace before moving on.

Exit ticket

Before marking complete

Close the reference. Reproduce the core idea from memory or explain the exact request/data flow aloud. Then check your diff or notes for accidental shortcuts that bypass validation, authorization, error handling, or verification earned in earlier phases.

← State Testing Debugging and Common Failures Guided Build Lab →