# Fallback Screens Backend

Fallback Screens is currently a frontend-only core module.

There is no backend source folder for this module.

## Backend Relationship

Backend modules may return HTTP status codes or API error payloads that eventually lead the admin frontend to show a fallback screen, but the fallback UI is owned by:

```txt
apps/admin/src/core/FallbackScreens/
```

Examples:

| Status | Frontend fallback      | Notes                                         |
| ------ | ---------------------- | --------------------------------------------- |
| `403`  | `/error/403` or inline | Used for permission denied states.            |
| `404`  | `/error/404`           | Used for unknown frontend routes.             |
| `500`  | `/error/500`           | Used for generic server failure presentation. |

## When Backend Changes Are Needed

Backend changes are only needed when:

- A backend endpoint should return a different status code.
- A redirect or auth flow should navigate the frontend to a fallback route.
- A feature needs a new machine-readable error contract that the frontend can map to a fallback screen.