Make bulk order updates all-or-nothing across authorization checks
A batch update contains nine permitted order IDs and one foreign ID. The service updates the first nine before discovering the forbidden order and returning 403.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Batch authorization · Transactions · Information disclosure
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 manufacturing company shares purchase-order documents with partner organizations. Buyers, partner administrators, and read-only agents use the same API. Recent support reports suggest list filters and background downloads disagree about who may see an order.
Setup prerequisites
- HTTP APIs
- Session authentication
- Tenant-scoped data access
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Authorize the complete bounded target set before committing changes.
- A missing, duplicate, or foreign order prevents the entire batch update.
- Record no success audit when the transaction is rejected.
Implementation constraints
- Do not reveal which foreign order exists through different error shapes.
Verification to include
- Update a fully authorized synthetic batch atomically.
- Mix permitted and forbidden IDs and inject a final-write failure; verify unchanged records.
Deliverables
- Atomic bulk command and mixed-scope reproduction
Rollout and recovery
Enable a bounded batch size on the synthetic client; revert batch routing without relaxing individual authorization.
Value of the work
For the engineer: Practice authorization as a service-level invariant, including revocation timing, concurrent membership changes, and asynchronous data delivery.
For the team: Inspect a concrete record of cross-organization denial, least-privilege decisions, and access-recovery behavior using fictional partner records.
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.