Lantern, a worked example · Record
SCN-ASMT-SCHEDULE: Accept an eligible schedule
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 › Scenarios › SCN-ASMT-SCHEDULE
The record
examples/scheduling/SCN-ASMT-SCHEDULE.md · View the file on GitHub
| Field | Value |
|---|---|
| ID | SCN-ASMT-SCHEDULE |
| Title | Accept an eligible schedule |
| Type | scenario |
| Status | draft |
| Delivery | not stated |
| Owner | team-assessment |
| Visibility | internal |
| Audiences | engineering, product |
| Revision | 1 |
| Illustrates | BEH-ASMT-SCHEDULE |
| Format | spec 0.2 · profile intentset/scenario/0.2 |
Given
An authorized teacher, a published assessment, and a future release time.
When
The teacher schedules the assessment for a class they manage.
Then
The system records the schedule and does not expose the assessment to students before its release time.
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).
- Verified by:
TEST-ASMT-SCHEDULEReview student assessment scheduling behavior