Frontend architecture

The frontend uses Next.js App Router and React to ask questions and collect user intent. Financial meaning and ownership remain on the server; client components explain the returned answer.

Trace the feature

1. Find its route.
2. Understand its layout and providers.
3. Reuse the API data flow and actual hooks.
4. Locate the relevant component responsibility.
5. Match the design and accessibility system.

Separate inquiry from action

An inquiry can read a balance or upcoming commitment. A financial command records money and must have clear pending, success and recovery states. A preview does not record money; a coach advancing does not prove a command succeeded.

Handle asynchronous identity

Authentication restoration and data requests can finish after a route or account changes. Retire stale generations and keep private content concealed until owned identity is freshly verified. Include dialogs and other portals in privacy testing.

Preserve evidence

Render currency, date or period, and any completeness or conversion note with a financial result. Loading, empty and unavailable are different states. Do not recompute missing evidence into an attractive but unsupported number.

See navigation for where a new action should live.