Scope work assignment queries to the operator's organization
The job list is scoped in the controller, but the claim repository accepts a globally valid job ID.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Tenant isolation · Repository design
Estimated field mix
- Security50%
- Database engineering30%
- Backend20%
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
A fictional inspection service assigns review jobs to staff. Polling clients sometimes claim the same job and a disconnected client can finish work after reassignment.
Setup prerequisites
- Create synthetic jobs and two independent database clients.
- Use explicit state methods and an injected clock.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Require organization scope at repository entry.
- Claim and detail queries enforce that scope.
- Return no other-organization job metadata on denial.
Implementation constraints
- Test direct repository calls as well as API routes.
Verification to include
- Claim a permitted synthetic job.
- Claim another organization's ID and verify unchanged row state.
Deliverables
- Tenant-scoped assignment repository
Rollout and recovery
Deploy repository guards before broader polling; inspect safe denial counters.
Value of the work
For the engineer: Practice database concurrency, leases and transactional invariants.
For the team: Review whether assignment authority remains reliable during contention and recovery.
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.