noCV
CAUCT-105 · Resolve concurrent changes

Confirm workshop holds only before the expiry boundary

Practice briefTaskAdvanced

Confirm and expiry cleanup race, creating reservations from expired holds. Add an atomic transition with one time rule.

Focused work estimate
3h + prerequisites
Priority in the scenario
High
Engineering practice
State machines · Concurrency

Estimated field mix

  • Database engineering60%
  • Backend40%

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 craft studio Maple offers workshop seats. Implement synthetic reservations without payments or real booking services.

Setup prerequisites

  • Create synthetic workshops with small capacities.
  • Implement local transactional hold storage and injected clocks.

Preceding work

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

Acceptance criteria

  • Eligible hold confirms once
  • Expired hold cannot confirm
  • Cleanup cannot remove confirmed reservation

Implementation constraints

  • Compare time inside the authoritative transition.

Verification to include

  • Confirm before boundary
  • Race confirm with expiry cleanup

Deliverables

  • Confirmation transition and boundary cases

Rollout and recovery

Pause confirmation if atomicity fails.

Value of the work

For the engineer: Practice contention, expiry and truthful realtime projections.

For the team: Inspect whether concurrent clients avoid overselling and recover uncertain results.

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.