noCV
CAUCT-101 · Define hold rules

Specify workshop seat counts without negative availability

Practice briefTaskFoundational

The prototype subtracts all historical holds and displays negative seats. Project availability from current authoritative states.

Focused work estimate
1h 15m + prerequisites
Priority in the scenario
High
Engineering practice
State modeling · Time

Estimated field mix

  • Backend60%
  • Database engineering40%

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

No earlier ticket is required. Complete the project setup above.

Acceptance criteria

  • Only active holds consume seats
  • Confirmed reservations consume seats
  • Expired holds do not consume seats

Implementation constraints

  • Define active using injected time.

Verification to include

  • Project mixed states
  • Use boundary expiry instant

Deliverables

  • Availability projection and cases

Rollout and recovery

Hide counts if state cannot be reconciled.

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.