Task library COBJS
Project scope 10 tickets / 3 phases
Total focused work estimate 23h + setup
Suggested stack TypeScript · S3-compatible adapter · PostgreSQL adapter · Vitest Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included.
Choose a bounded subset for an assessment or practice session. Prerequisites and remaining project work must be agreed separately.
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Pattern topics identify design choices to practice. Read the ticket's acceptance criteria and justify the simplest suitable approach. Tags are not capability or ownership evidence; an untagged ticket has no curated pattern topic assigned.
Recommended next step Start with COBJS-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice object lifecycle, retry semantics and integrity verification.
What the team gains Inspect whether uploads avoid corruption, orphan cost and tenant crossover.
Before you start Generate small deterministic byte fixtures. Implement local multipart provider responses including timeout and missing parts. Delivery agreement Submit bounded coordinator changes; external cloud rollout is separate.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Specify keys, parts and quotas.
PHASE 2 Handle retries and integrity boundaries.
PHASE 3 Reclaim resources and inspect outcomes.
Define upload ownership Specify keys, parts and quotas.
COBJS-101 Entry ticket; project setup still required Estimated field mix
API design 60% Storage systems 40% COBJS-102 Depends on COBJS-101 Estimated field mix
Security 60% Storage systems 40% COBJS-103 Depends on COBJS-102 Estimated field mix
Storage systems 50% API design 30% Performance engineering 20% Complete reliably Handle retries and integrity boundaries.
COBJS-104 Depends on COBJS-102, COBJS-103 Estimated field mix
Storage systems 50% Distributed systems 50% COBJS-105 Depends on COBJS-104 Estimated field mix
Storage systems 80% API design 20% COBJS-106 Depends on COBJS-105 Estimated field mix
Storage systems 80% Backend 20% COBJS-107 Depends on COBJS-105, COBJS-106 Estimated field mix
Storage systems 50% Distributed systems 30% Database engineering 20% Recover abandoned work Reclaim resources and inspect outcomes.
COBJS-108 Depends on COBJS-107 Estimated field mix
Storage systems 70% Site reliability 30% COBJS-109 Depends on COBJS-104, COBJS-108 Estimated field mix
Frontend 50% Storage systems 30% API design 20% COBJS-110 Depends on COBJS-109 Estimated field mix
Security 50% Site reliability 30% Storage systems 20% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.