Developer reference
Application routes
Find public, authentication and private App Router surfaces and their data boundaries.
Routes organize the UI. API authentication and resource ownership remain required even when a route itself is private.
Private financial routes
| Route | Purpose |
|---|---|
/ | My Situation for a signed-in user. |
/coming | Upcoming obligations and plans. |
/subscriptions | Recurring subscriptions. |
/people | Loans, people and shared context. |
/people/[id] | Person detail. |
/people/gameyyas/[id] | Rotating savings arrangement. |
/people/identities/[id] | Real-world matter detail. |
/activity | Actual recorded movements and recording controls. |
/insights | Financial patterns and history. |
/settings | Setup, preferences, security and API tokens. |
/settings/import | Import source review and job lifecycle. |
Square-bracket segments represent owned record IDs. Do not accept an arbitrary ID as evidence of permission.
Public and auth routes
/welcome, /privacy and /roadmap are public product surfaces. /welcome is the canonical public landing page; signed-out root navigation leads to the public entry.
/login, /signup, /forgot-password and /update-password support authentication. They should not be indexed as public content or reveal private financial views before verification.
When changing navigation
Test direct navigation, authenticated transitions and browser Back. Ensure a stale private page cannot reveal a prior account after logout. Development-only previews are not stable public product routes.
For API routes, use the registered catalog rather than inferring transport paths from page routes.