CCAL-103 · Read the schedule

Describe staffing time-zone changes explicitly

Practice briefTaskFoundational

The calendar silently changes times when the display zone changes. Show zone context without announcing every cell.

Focused work estimate: 1h 15m + prerequisites
Priority in the scenario: Medium
Engineering practice: Time · Live regions

Estimated field mix

Accessibility70%
Frontend30%

Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.

Your next step

Review it, then add it to your workspace.

The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.

Use in my work board View project and downloads

Project context

Fictional studio Loom assigns editorial shifts. Build synthetic shifts and a local scheduling adapter; no real staff records are used.

Setup prerequisites

Create synthetic shifts including overlaps and daylight-saving boundaries.
Implement a local schedule revision adapter.

Preceding work

Complete these dependencies, or supply their agreed outputs before taking this ticket.

CCAL-101 · Name staffing shifts independently of calendar color

Acceptance criteria

Header identifies display zone
Shift detail exposes full date/time
Zone change has one status announcement

Implementation constraints

Store instants independently from labels.

Verification to include

Change zone and inspect detail
Use ambiguous clock time fixture

Deliverables

Zone labels and manual reading protocol

Rollout and recovery

Fix display to documented UTC if conversion fails.

Value of the work

For the engineer: Practice focus models and accessible alternatives for spatial interfaces.

For the team: Inspect whether scheduling remains usable across input methods and failure states.

Evidence boundaries

Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.

Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.