Phase 35 · Lesson 06

Frontend State and Server Client Boundary Review

≈ 2 min core reading · 179 source/companion words

Learning contract

What you should be able to do after this

Explain Frontend State and Server Client Boundary Review without relying on framework buzzwords.
Connect the lesson to the phase outcome: Review and refactor TaskFlow architecture using evidence: dependency direction, duplication, tests, complexity, security, and operational boundaries.
Reproduce the relevant behavior and verify it with evidence.
Diagnose at least one representative failure instead of guessing.

Figure 35.6 — TaskFlow boundary map

observe architecture

identify smell/risk

establish tests

small refactor

verify behavior

document decision

This lesson belongs to Phase 35. 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.

Frontend State and Server/Client Boundary Review Volumes 06 and 07 created several legitimate state owners. Phase 35 checks for accidental duplication and client-boundary growth after forms, TanStack Query, optimistic updates, and Realtime were added.

Review area Healthy signal Refactor trigger

Server data TanStack Query / Server Component fetch Copied into useState

URL filters Next.js URL/searchParams Hidden global store copy

Form draft React Hook Form Query cache mutated on each keystroke

Auth session Supabase Auth Homegrown duplicate auth store

Local interaction useState/useReducer Application-wide Context without need

Review client boundaries • Can a component become a Server Component again?

• Did one small event handler cause an entire page tree to become use client?

• Are large libraries shipped to the browser for interactions that could be isolated or lazy-loaded?

• Does Realtime invalidate authoritative server state instead of turning WebSocket payloads into a second backend? The browser should own interaction state, not duplicate the backend. Source basis: integrated TaskFlow architecture and engineering decisions established in Phases 00-34; this chapter is an internal review/refactoring synthesis rather than a new framework feature.

Executable lesson studio · state

Now turn the explanation into engineering skill.

Frontend State and Server Client Boundary Review 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 Frontend State and Server Client Boundary Review 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 35.6B — 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 “Frontend State and Server Client Boundary Review” 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: Architecture review report plus one behavior-preserving refactor backed by tests and an ADR.. 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

Refactor with no behavioral safety net
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 “Frontend State and Server Client Boundary Review” 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 Frontend State and Server Client Boundary Review 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

Write a short ADR recording context, decision, alternatives, consequences, and when to revisit.

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

Break it safely

Refactor with no behavioral safety net

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.

← Transactions Business Rules and Persistence Boundaries Authentication Authorization and Security Boundary Review →