Task library BENV
Project scope 10 tickets / 3 phases
Total focused work estimate 26h 30m + setup
Suggested stack TypeScript · PostgreSQL · Infrastructure plan fixtures 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 BENV-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice resource lifecycle state machines, isolation, and reconciliation.
What the team gains Make review environments predictable, isolated, and accountable to a budget.
Before you start Author a local environment-provider double and synthetic pull-request events; provision no external resources. Delivery agreement Deliver a local lifecycle controller and cleanup rehearsal using simulated resource records.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Define identity, scope, and resource limits.
PHASE 2 Create, update, expire, and reconcile environments.
PHASE 3 Verify cleanup safety and cost controls.
Model environment ownership Define identity, scope, and resource limits.
BENV-101 Entry ticket; project setup still required Estimated field mix
Cloud infrastructure 60% Platform engineering 40% BENV-102 Depends on BENV-101 Estimated field mix
Cloud infrastructure 70% Platform engineering 30% Manage lifecycle Create, update, expire, and reconcile environments.
BENV-103 Depends on BENV-102 Estimated field mix
Cloud infrastructure 50% Distributed systems 50% BENV-104 Depends on BENV-103 Estimated field mix
Security 50% Cloud infrastructure 30% Database engineering 20% BENV-105 Depends on BENV-104 Estimated field mix
Security 70% Cloud infrastructure 30% BENV-106 Depends on BENV-103, BENV-105 Estimated field mix
Cloud infrastructure 50% Distributed systems 30% Platform engineering 20% BENV-107 Depends on BENV-103, BENV-106 Estimated field mix
Cloud infrastructure 50% Distributed systems 30% Site reliability 20% Operate within bounds Verify cleanup safety and cost controls.
BENV-108 Depends on BENV-107 Estimated field mix
Security 50% Cloud infrastructure 50% BENV-109 Depends on BENV-104, BENV-108 Estimated field mix
System design 40% Cloud infrastructure 40% Security 20% BENV-110 Depends on BENV-109 Estimated field mix
Frontend 40% Cloud infrastructure 30% Site reliability 30% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.