Task library CROUTE
Project scope 10 tickets / 3 phases
Total focused work estimate 22h 30m + setup
Suggested stack React Native · TypeScript · SQLite · Emulator 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 CROUTE-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice durable mobile state and explicit sync conflicts.
What the team gains Inspect how an engineer protects field work during disconnection.
Before you start Create synthetic visits and a local sync adapter. Provide controllable connectivity and process-restart simulation. Delivery agreement Use synthetic notes and emulator runs; no location tracking or real dispatch.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Define local visit state.
PHASE 2 Persist notes and resolve conflicts.
PHASE 3 Bound retries and explain sync outcomes.
Make visits readable Define local visit state.
CROUTE-101 Entry ticket; project setup still required CROUTE-102 Entry ticket; project setup still required CROUTE-103 Depends on CROUTE-101, CROUTE-102 Estimated field mix
Mobile 60% Database engineering 40% Protect offline work Persist notes and resolve conflicts.
CROUTE-104 Depends on CROUTE-103 Estimated field mix
Mobile 40% Database engineering 30% Distributed systems 30% CROUTE-105 Depends on CROUTE-104 Estimated field mix
Mobile 50% Distributed systems 50% CROUTE-106 Depends on CROUTE-104 Estimated field mix
Mobile 50% Distributed systems 30% Site reliability 20% CROUTE-107 Depends on CROUTE-102, CROUTE-103 Estimated field mix
Storage systems 60% Mobile 40% Recover interruptions Bound retries and explain sync outcomes.
CROUTE-108 Depends on CROUTE-106 Estimated field mix
Mobile 60% Site reliability 40% CROUTE-109 Depends on CROUTE-105, CROUTE-108 CROUTE-110 Depends on CROUTE-106, CROUTE-109 Estimated field mix
Privacy engineering 60% Mobile 40% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.