Lantern, a worked example · Record
CONTRACT-ASMT-SCHEDULE: ScheduleAssessment contract
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 › Contracts › CONTRACT-ASMT-SCHEDULE
The record
examples/scheduling/CONTRACT-ASMT-SCHEDULE.md · View the file on GitHub
| Field | Value |
|---|---|
| ID | CONTRACT-ASMT-SCHEDULE |
| Title | ScheduleAssessment contract |
| Type | contract |
| Status | draft |
| Delivery | not stated |
| Owner | team-assessment |
| Visibility | internal |
| Audiences | engineering, product |
| Revision | 1 |
| Format | spec 0.2 · profile intentset/contract/0.2 |
Interface
Input: assessmentId, classId, releaseAt (UTC timestamp). Success: scheduleId. Rejections: unauthorized, unpublished, invalid-time. Draft transport representation is not yet selected.
Compatibility
Removing a field or tightening accepted times is breaking. Consumers must be reviewed when preconditions change.
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).
- Exposed by:
SLICE-ASMT-SCHEDULEStudent assessment scheduling slice