Specify fixed-delay behavior for periodic kiosk maintenance
Long cache refreshes cause catch-up bursts because scheduling alternates between fixed-rate and fixed-delay behavior. Choose fixed-delay for this job class.
- Focused work estimate
- 2h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Scheduling · Time
Estimated field mix
- Embedded and edge100%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
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.
Project context
Fictional kiosk software schedules cache refresh and display housekeeping. Build a software clock and job adapter; do not control real machinery or purchase hardware.
Setup prerequisites
- Implement injected wall and monotonic clocks.
- Create synthetic jobs with controllable completion and failure.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Next run starts after completion plus delay
- Slow runs do not overlap
- Failure still follows documented next-run policy
Implementation constraints
- Limit the change to the declared maintenance class.
Verification to include
- Complete short job
- Complete job longer than interval
Deliverables
- Periodic policy and fake-clock cases
Rollout and recovery
Pause periodic jobs while schedule semantics are repaired.
Value of the work
For the engineer: Practice timer semantics, cancellation and bounded scheduling.
For the team: Inspect predictable edge resource use and honest execution status.
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.