Choose where report artifacts become authoritative
A worker uploads a partial file and the API exposes its object key before completion checks finish.
- Focused work estimate
- 3h + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Storage lifecycle · System boundaries
Estimated field mix
- Storage systems50%
- System design30%
- Security20%
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 analytics product lets customers schedule expensive reports at the top of the hour. The API remains available only if report work is admitted and cancelled predictably.
Setup prerequisites
- Create a local scheduler model and synthetic report jobs.
- Use fake execution providers; no customer queries or candidate code run on worker hosts.
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- AADMIT-101 · Build a report arrival model that includes top-of-hour bursts
- AADMIT-102 · Define customer-visible report states and overload responses
- AADMIT-103 · Record the fairness decision for small and large report tenants
- AADMIT-104 · Specify transactional report admission with deterministic job identities
- AADMIT-105 · Design cancellation ownership for queued and running reports
Acceptance criteria
- Stage artifacts under a job generation.
- Publish only after verified storage identity and guarded completion.
- Keep incomplete or stale-generation artifacts inaccessible.
Implementation constraints
- Separate object upload from user-visible report publication.
Verification to include
- Publish a verified synthetic artifact for the active job.
- Complete an older generation and verify it cannot replace the visible result.
Deliverables
- Artifact publication boundary and contract probe
Rollout and recovery
Prototype with local storage; keep staged objects private until finalization succeeds.
Value of the work
For the engineer: Practice workload modeling, fairness and cancellation architecture.
For the team: Review controllable operating costs and predictable customer-facing overload behavior.
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.