CAUCT-104 · Resolve concurrent changes

Scope workshop hold lookup and cancellation to its owner

Practice briefBugIntermediate

Knowing a hold ID lets another user cancel it. Enforce owner scope in the repository boundary.

Focused work estimate: 2h 15m + prerequisites
Priority in the scenario: High
Engineering practice: Authorization · Repository design

Estimated field mix

Security70%
Backend30%

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 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

Owner reads and cancels
Foreign owner is denied
Denied calls do not disclose hold details

Implementation constraints

Synthetic identities remain required in all adapter calls.

Verification to include

Cancel own hold
Cancel another account's hold

Deliverables

Scoped hold repository and denial tests

Rollout and recovery

Disable cancellation if scope cannot be established.

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.