noCV
CTIMER-102 · Define time semantics

Validate emulated edge-job intervals before scheduling

Practice briefTaskFoundational

A zero interval creates an immediate callback loop. Enforce a documented supported interval range.

Focused work estimate
1h + prerequisites
Priority in the scenario
Medium
Engineering practice
Validation · Scheduling

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.

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.

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

  • Valid intervals register
  • Zero negative and oversized values fail
  • Rejected jobs allocate no timer

Implementation constraints

  • Do not silently clamp invalid configuration.

Verification to include

  • Register valid interval
  • Reject zero and negative interval

Deliverables

  • Interval validator and cases

Rollout and recovery

Reject new registrations if limits cannot be enforced.

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.