Skip to content

Lantern, a worked example · Record

TEST-ASMT-SCHEDULE: Review student assessment scheduling behavior

An invented example

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 › Verifications › TEST-ASMT-SCHEDULE

The record

examples/scheduling/TEST-ASMT-SCHEDULE.md · View the file on GitHub

Field Value
ID TEST-ASMT-SCHEDULE
Title Review student assessment scheduling behavior
Type verification
Status draft
Owner team-assessment
Visibility internal
Audiences engineering, product
Revision 1
Verifies BEH-ASMT-SCHEDULE, RULE-ASMT-FUTURE, RULE-ASMT-AUTH, SCN-ASMT-SCHEDULE
Method manual
Locator examples/scheduling/TEST-ASMT-SCHEDULE.md
Selector schedule-review-v1
Format spec 0.2 · profile intentset/verification/0.2

Procedure

In a pilot environment, run: authorized published/future request; past-time rejection; unauthorized-class rejection; unpublished rejection; student access before and after release. Record inputs, observed outputs, environment, commit, graph hash, and reviewer. This procedure has not been executed.

Expected result

The valid request is recorded, rejected requests create no schedule, and student access follows the reviewed release-time tolerance. The procedure cannot pass until that tolerance is defined.

Everything below is derived: the Atlas reads it from this record and the others, and none of it is written in the file.

Evidence

Linked from other records

No other record links to this one.

Also on the verification page, among the claims it covers.