# FRAME Entries Backend

## Purpose

`frame_entries` stores weekly F.R.A.M.E. focus entries per organization. The backend is the source of truth for persisted FRAME data.

## API

All routes require JWT authentication.

- `GET /api/frame_entries`: returns `{ rows, count }` for the current user's organization.
- `POST /api/frame_entries`: creates one entry and returns the created DTO.
- `PUT /api/frame_entries/:id`: updates one entry inside the current user's organization and returns the updated DTO.

## Access Rules

- All authenticated users in the organization can read FRAME entries.
- Editing is restricted to generated roles mapped to director or superintendent capabilities:
  - `Super Administrator`
  - `Administrator`
  - `Platform Owner`
  - `Tenant Director`
  - `Campus Manager`

The frontend may hide editing controls, but backend role checks remain authoritative.

## Data Contract

Required request fields:

- `week_of`
- `posted_date`
- `formal`
- `recognition`
- `application`
- `management`
- `emotional`
- `author`

Tenant scope is assigned from the current authenticated user. `campusId` is optional and defaults to the current staff profile campus when available.