Reject multipart uploads exceeding declared size limits
The coordinator accepts an unlimited part list. Bound declared object size and per-session part count.
- Focused work estimate
- 1h 15m + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Resource limits · Contracts
Estimated field mix
- Storage systems50%
- API design30%
- Performance engineering20%
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
Fictional document archive Fern stores synthetic byte objects. Use a local S3-compatible adapter or deterministic in-memory provider; no cloud credentials are needed.
Setup prerequisites
- Generate small deterministic byte fixtures.
- Implement local multipart provider responses including timeout and missing parts.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Valid declared sizes pass
- Part count has explicit maximum
- Rejected admission creates no provider session
Implementation constraints
- Limits must be checked before remote allocation.
Verification to include
- Admit small fixture
- Reject oversized declaration
Deliverables
- Admission policy and allocation checks
Rollout and recovery
Lower admission to a documented safe cap if accounting fails.
Value of the work
For the engineer: Practice object lifecycle, retry semantics and integrity verification.
For the team: Inspect whether uploads avoid corruption, orphan cost and tenant crossover.
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.