# Requirements Docs AGENTS

## Purpose

- Requirement docs define active scope, roles, workflows, and business constraints for the current phase.

## Current mainline

- Keep requirements docs aligned with:
  - platform core
  - facility reservation
  - course resources
  - optional library extension

## Rules

- If a module is not in the active course-design mainline, prefer archive over reintroducing it here.
- Requirements should state:
  - scope
  - actors
  - state transitions
  - business constraints
  - out-of-scope items
- Important business constraints should be written clearly enough to later map into database constraints where appropriate.