Lantern, a worked example · Record
SLICE-ASMT-SCHEDULE: Student assessment scheduling slice
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 › Slices › SLICE-ASMT-SCHEDULE
The record
examples/scheduling/SLICE-ASMT-SCHEDULE.md · View the file on GitHub
| Field | Value |
|---|---|
| ID | SLICE-ASMT-SCHEDULE |
| Title | Student assessment scheduling slice |
| Type | slice |
| Status | draft |
| Delivery | not stated |
| Owner | team-assessment |
| Visibility | internal |
| Audiences | engineering, product |
| Revision | 1 |
| Implements | BEH-ASMT-SCHEDULE |
| Exposes | CONTRACT-ASMT-SCHEDULE |
| Informed by | ADR-ASMT-SEAM |
| Slice kind | product |
| Domain | assessment |
| Entrypoint | src/features/assessment/schedule/index.ts |
| Layers | application src/features/assessment/schedule/domain/use-cases/**; external src/features/assessment/schedule/client/**; model src/features/assessment/schedule/domain/models/**; policy src/features/assessment/schedule/domain/policies/**; presentation src/features/assessment/schedule/ui/** |
| Claims | source src/features/assessment/schedule/**; backend amplify/functions/schedule-assessment/** |
| Uses resources | RES-ASSESSMENT-DATA |
| Format | spec 0.2 · profile intentset/slice/0.2 |
Responsibility
Accountable implementation owner for scheduled assessment delivery. Code paths are planned; this example is L1 only and makes no implementation-conformance claim.
Public contract
ScheduleAssessment accepts a class, assessment, and release time and returns a stable schedule identifier or a typed rejection.
Verification
TEST-ASMT-SCHEDULE defines a manual pilot review, with no execution evidence yet.
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
No other record links to this one.
Also on the ownership page, with its path claims, layers and shared resources.