Task library CBUILD
Project scope 10 tickets / 3 phases
Total focused work estimate 24h + 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 CBUILD-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice dependency graphs and cache correctness.
What the team gains Inspect whether build speed improvements preserve output correctness.
Before you start Create a synthetic module graph and deterministic transform stub. Provide file-change, missing-input and interrupted-output fixtures. Delivery agreement Measure local fixture behavior; broad compiler-performance claims are excluded.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Parse and validate local graph edges.
PHASE 2 Reuse only compatible outputs.
PHASE 3 Publish outputs and explain cache decisions.
Establish dependency identity Parse and validate local graph edges.
CBUILD-101 Entry ticket; project setup still required Estimated field mix
Developer tooling 50% Compiler and language tooling 30% Security 20% CBUILD-102 Depends on CBUILD-101 Estimated field mix
Compiler and language tooling 70% Developer tooling 30% CBUILD-103 Depends on CBUILD-101, CBUILD-102 Estimated field mix
Compiler and language tooling 60% Developer tooling 40% Invalidate and rebuild Reuse only compatible outputs.
CBUILD-104 Depends on CBUILD-103 Estimated field mix
Developer tooling 50% Compiler and language tooling 30% Performance engineering 20% CBUILD-105 Depends on CBUILD-103, CBUILD-104 Estimated field mix
Compiler and language tooling 50% Developer tooling 30% Performance engineering 20% CBUILD-106 Depends on CBUILD-104, CBUILD-105 Estimated field mix
Developer tooling 60% Compiler and language tooling 40% CBUILD-107 Depends on CBUILD-105, CBUILD-106 Estimated field mix
Developer tooling 50% Compiler and language tooling 50% Recover interrupted builds Publish outputs and explain cache decisions.
CBUILD-108 Depends on CBUILD-106, CBUILD-107 Estimated field mix
Developer tooling 50% Storage systems 30% Site reliability 20% CBUILD-109 Depends on CBUILD-105, CBUILD-108 Estimated field mix
Developer tooling 60% Compiler and language tooling 40% CBUILD-110 Depends on CBUILD-104, CBUILD-109 Estimated field mix
Developer tooling 80% Compiler and language tooling 20% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.