Task library ABOUND
Project scope 10 tickets / 3 phases
Total focused work estimate 33h 30m + setup
Suggested stack TypeScript · PostgreSQL · HTTP · Provider interfaces 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 ABOUND-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice boundary decisions backed by executable consistency and failure checks.
What the team gains Review architecture tradeoffs with explicit assumptions before infrastructure commitment.
Before you start Create synthetic upload metadata and a fake processing provider. Treat diagrams as proposals; implement only local contract probes. Delivery agreement Ten scoped tickets across three phases. Build a synthetic local service or select a ticket after recreating its prerequisites; estimates exclude setup.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Define workload, authority and state ownership.
PHASE 2 Make contracts and failure semantics executable.
PHASE 3 Test alternatives, failure modes and migration steps.
Frame the boundary Define workload, authority and state ownership.
ABOUND-101 Entry ticket; project setup still required Estimated field mix
System design 50% Performance engineering 50% ABOUND-102 Depends on ABOUND-101 Estimated field mix
System design 60% Security 40% ABOUND-103 Depends on ABOUND-101, ABOUND-102 Estimated field mix
System design 50% Storage systems 30% Security 20% Specify the interactions Make contracts and failure semantics executable.
ABOUND-104 Depends on ABOUND-102, ABOUND-103 Estimated field mix
System design 50% Backend 30% Distributed systems 20% ABOUND-105 Depends on ABOUND-104 Estimated field mix
System design 40% Distributed systems 40% Database engineering 20% ABOUND-106 Depends on ABOUND-104, ABOUND-105 Estimated field mix
System design 50% Distributed systems 50% ABOUND-107 Depends on ABOUND-104, ABOUND-106 Estimated field mix
System design 50% Backend 30% Real-time systems 20% Challenge the design Test alternatives, failure modes and migration steps.
ABOUND-108 Depends on ABOUND-101, ABOUND-105, ABOUND-106 Estimated field mix
Performance engineering 50% System design 30% Site reliability 20% ABOUND-109 Depends on ABOUND-103, ABOUND-106, ABOUND-108 Estimated field mix
System design 70% Distributed systems 30% ABOUND-110 Depends on ABOUND-105, ABOUND-107, ABOUND-109 Estimated field mix
System design 50% Platform engineering 30% Backend 20% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.