Define the difference between accepted and completed bulk work
The current endpoint returns success before any imported row has been validated.
- Focused work estimate
- 1h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- API modeling
Estimated field mix
- API design80%
- 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 catalog API needs to accept imports too large for one synchronous request. Partners need to distinguish accepted work, completed items, and recoverable failures.
Setup prerequisites
- Create a local API and worker double with synthetic catalog records and controlled interruption points.
Preceding work
No earlier ticket is required. Complete the project setup above.
Acceptance criteria
- Publish accepted, running, completed, and failed meanings.
- Define terminal partial-success representation.
- Keep transport acceptance separate from item validity.
Implementation constraints
- Use explicit operation transition methods.
Verification to include
- Represent an accepted unprocessed import.
- Show completed-with-errors without claiming every item succeeded.
Deliverables
- Bulk operation schema.
Rollout and recovery
Review lifecycle vocabulary before adding endpoints.
Value of the work
For the engineer: Practice asynchronous resource contracts, partial outcomes, and idempotent operations.
For the team: Provide predictable bulk integration behavior without ambiguous success or repeated effects.
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.