Task: Write an implementation-neutral, acceptance-ready specification for a Moodle-like online quiz system. Center a graded attempt with visible question status and navigation, persistent timer controls, and clear low-time warnings while covering the full lifecycle.
Specification protocol: State assumptions and unresolved decisions; do not invent a stack or Moodle compatibility. Define learner, author, instructor/proctor, administrator, and support/auditor roles. Cover question-bank versioning, randomization, attempt states, autosave, timing and accommodations, submission, scoring, partial credit, manual grading, feedback, appeals, reporting, retention, export, and audit events. Address authentication, authorization, least privilege, file/input safety, encryption expectations, privacy/deletion, threat modeling, proportionate cheating deterrence, and false-positive review. Specify keyboard and screen-reader use, focus, semantics, contrast, reflow, non-color cues, and timing alternatives. Deliver numbered requirements, data concepts, state transitions, permission matrix, edge/abuse cases, and measurable tests for reconnects, concurrency, timer drift, grading, accessibility, security, privacy, load, and recovery. Separate requirements from implementation options.