d4a5378adf
Frontend: - Replace Next.js with Vite + React + TypeScript - Add new component architecture (app-shell, sidebar, dashboard modules) - Implement product modules: FRAME, safety protocols, walkthrough checkin, campus/staff attendance, personality quiz, sign language, classroom timer - Add shadcn/ui component library with Tailwind CSS - Remove legacy generated components, stores, and pages Backend: - Add product migrations: frame_entries, user_progress, safety_quiz_results, walkthrough_checkins, communication_events, personality_quiz_results, campus_attendance_config/summaries, staff_attendance_records, content_catalog - Add corresponding models, services, and routes - Implement cookie-based auth with refresh token rotation - Add content catalog seeder with product content - Migrate to ESLint flat config - Switch from yarn to npm Infrastructure: - Update .gitignore for new tooling - Add project documentation (CLAUDE.md, docs/) - Remove deprecated config files and yarn.lock Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
41 lines
1.2 KiB
Markdown
41 lines
1.2 KiB
Markdown
# 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.
|