Task library CBACK
Project scope 10 tickets / 3 phases
Total focused work estimate 25h 30m + setup
Suggested stack TypeScript · SQLite · 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 CBACK-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice consistent snapshots and recoverable restoration.
What the team gains Inspect whether backup success can be substantiated by a usable restore.
Before you start Create synthetic metadata and generated blob fixtures. Provide isolated source backup and restore directories. Delivery agreement Record local restore evidence; production disaster-recovery qualification remains separate.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Define scope and integrity.
PHASE 2 Handle interruption and version boundaries.
PHASE 3 Validate before switching authority.
Describe backup content Define scope and integrity.
CBACK-101 Entry ticket; project setup still required Estimated field mix
Storage systems 80% Data engineering 20% CBACK-102 Depends on CBACK-101 Estimated field mix
Storage systems 60% Database engineering 40% CBACK-103 Depends on CBACK-101, CBACK-102 Capture coherently Handle interruption and version boundaries.
CBACK-104 Depends on CBACK-102, CBACK-103 Estimated field mix
Storage systems 50% Database engineering 30% Distributed systems 20% CBACK-105 Depends on CBACK-103, CBACK-104 Estimated field mix
Storage systems 70% Site reliability 30% CBACK-106 Depends on CBACK-103, CBACK-105 Estimated field mix
Storage systems 80% Site reliability 20% CBACK-107 Depends on CBACK-101, CBACK-106 Estimated field mix
Security 60% Storage systems 40% Restore into isolation Validate before switching authority.
CBACK-108 Depends on CBACK-106, CBACK-107 Estimated field mix
Storage systems 60% Site reliability 40% CBACK-109 Depends on CBACK-108 Estimated field mix
Storage systems 60% Site reliability 40% CBACK-110 Depends on CBACK-109 Estimated field mix
Quality engineering 40% Storage systems 30% Site reliability 30% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.