Lantern, a worked example · Record
RULE-ASMT-AUTH: Require assignment permission
This Atlas is drawn from the records of an invented product, so it can be published to show what the Atlas shows. A team's own Atlas may contain internal and restricted records and stays inside the organization. The files are authoritative; these pages are a derived view of them.
Snapshot: commit unknown · graph hash 3b31c362b352 · level L1 · scope examples/scheduling/**
Records › Rules › RULE-ASMT-AUTH
The record
examples/scheduling/RULE-ASMT-AUTH.md · View the file on GitHub
| Field | Value |
|---|---|
| ID | RULE-ASMT-AUTH |
| Title | Require assignment permission |
| Type | rule |
| Status | draft |
| Delivery | not stated |
| Owner | team-assessment |
| Visibility | internal |
| Audiences | engineering, product |
| Revision | 1 |
| Format | spec 0.2 · profile intentset/rule/0.2 |
Constraint
The server must reject scheduling unless the assessment is published and the actor is authorized to assign it to the requested class.
Everything below is derived: the Atlas reads it from this record and the others, and none of it is written in the file.
Linked from other records
The links other records write to this one, read the other way (Core §5).
- Governs:
BEH-ASMT-SCHEDULESchedule a student assessment - Verified by:
TEST-ASMT-SCHEDULEReview student assessment scheduling behavior - Explained by:
KB-ASMT-SCHEDULEPrepare a scheduled student assessment