Task library CKV
Project scope 10 tickets / 3 phases
Total focused work estimate 26h 15m + setup
Suggested stack TypeScript · Filesystem 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 CKV-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice storage formats, durability boundaries and corruption handling.
What the team gains Inspect whether an engineer can state and test persistence guarantees.
Before you start Create a disposable local fixture directory. Implement fault injection for partial writes, sync failure and process restart. Delivery agreement Each ticket adds one narrow engine behavior; publish measured local limits, not database performance claims.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Define bounded encoding and reads.
PHASE 2 Handle torn records and atomic updates.
PHASE 3 Compact safely and inspect damage.
Specify records Define bounded encoding and reads.
CKV-101 Entry ticket; project setup still required Estimated field mix
Storage systems 70% Database engineering 30% CKV-102 Depends on CKV-101 Estimated field mix
API design 60% Storage systems 40% CKV-103 Depends on CKV-101, CKV-102 Estimated field mix
Storage systems 60% Database engineering 40% Recover durable writes Handle torn records and atomic updates.
CKV-104 Depends on CKV-103 Estimated field mix
Storage systems 70% Database engineering 30% CKV-105 Depends on CKV-103, CKV-104 Estimated field mix
Storage systems 80% Database engineering 20% CKV-106 Depends on CKV-104, CKV-105 Estimated field mix
Storage systems 60% Database engineering 40% CKV-107 Depends on CKV-104, CKV-106 Estimated field mix
Database engineering 60% Storage systems 40% Reclaim old storage Compact safely and inspect damage.
CKV-108 Depends on CKV-106, CKV-107 Estimated field mix
Storage systems 50% Database engineering 30% Performance engineering 20% CKV-109 Depends on CKV-108 Estimated field mix
Storage systems 70% Database engineering 30% CKV-110 Depends on CKV-105, CKV-109 Estimated field mix
Developer tooling 50% Storage systems 50% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.