# noCV engineering task library Content version 5 Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs. Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence. ## BENV — Ephemeral review-environment lifecycle A fictional product team creates preview environments for pull requests. Forgotten environments accumulate cost, and shared test data leaks between reviews. **Field:** Cloud infrastructure. **Suggested stack:** TypeScript, PostgreSQL, Infrastructure plan fixtures. **Engineer value:** Practice resource lifecycle state machines, isolation, and reconciliation. **Company value:** Make review environments predictable, isolated, and accountable to a budget. **Delivery agreement:** Deliver a local lifecycle controller and cleanup rehearsal using simulated resource records. ### Setup prerequisites - Author a local environment-provider double and synthetic pull-request events; provision no external resources. ### Model environment ownership Define identity, scope, and resource limits. #### BENV-101 — Define review-environment identity independently of branch names **Task · Medium priority · Foundational** noCV practice brief v5 · BENV-101 · Ephemeral review-environment lifecycle Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Model environment ownership. Depends on: No preceding ticket. Difficulty: Foundational. Estimated focused work: 60 minutes; setup and prerequisite tickets are additional. Estimated field mix: Cloud infrastructure 60% · Platform engineering 40%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Renamed branches orphan their original preview resources. Acceptance criteria - Use stable repository and change identities. - Keep branch names as mutable labels. - Record owner and expiry explicitly. Implementation constraints - Use fictional repositories and no real webhook subscription. Verification - Rename a synthetic branch without creating another environment. - Reject conflicting repository identity reuse. Deliverables - Environment identity model. Rollout and recovery: Adopt identity recording before resource creation. Project prerequisites: Author a local environment-provider double and synthetic pull-request events; provision no external resources. Engineer value: Practice resource lifecycle state machines, isolation, and reconciliation. Company value: Make review environments predictable, isolated, and accountable to a budget. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### BENV-102 — Set per-environment and per-team resource ceilings **Task · High priority · Intermediate** noCV practice brief v5 · BENV-102 · Ephemeral review-environment lifecycle Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Model environment ownership. Depends on: BENV-101. Difficulty: Intermediate. Estimated focused work: 120 minutes; setup and prerequisite tickets are additional. Estimated field mix: Cloud infrastructure 70% · Platform engineering 30%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. One team opens enough previews to exhaust the shared database quota. Acceptance criteria - Declare resource units and budget limits. - Reserve capacity before creation. - Reject requests exceeding either ceiling. Implementation constraints - Provider resources are simulated records. Verification - Reserve an allowed preview. - Race requests at the limit and prevent over-allocation. Deliverables - Quota reservation logic. Rollout and recovery: Start with low fixture quotas; release reservations only through terminal lifecycle actions. Project prerequisites: Author a local environment-provider double and synthetic pull-request events; provision no external resources. Engineer value: Practice resource lifecycle state machines, isolation, and reconciliation. Company value: Make review environments predictable, isolated, and accountable to a budget. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. ### Manage lifecycle Create, update, expire, and reconcile environments. #### BENV-103 — Create environments through idempotent provider operations **Task · High priority · Advanced** noCV practice brief v5 · BENV-103 · Ephemeral review-environment lifecycle Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Manage lifecycle. Depends on: BENV-102. Difficulty: Advanced. Estimated focused work: 180 minutes; setup and prerequisite tickets are additional. Estimated field mix: Cloud infrastructure 50% · Distributed systems 50%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. A create timeout produces two environments for the same review. Acceptance criteria - Persist a stable operation identity before dispatch. - Adopt matching provider resources after retry. - Reject conflicting provider ownership metadata. Implementation constraints - Use explicit provider interfaces and local doubles. Verification - Recover after an accepted create loses its response. - Detect an existing resource owned by another review. Deliverables - Idempotent provision coordinator. Rollout and recovery: Keep uncertain creates pending until reconciliation. Project prerequisites: Author a local environment-provider double and synthetic pull-request events; provision no external resources. Engineer value: Practice resource lifecycle state machines, isolation, and reconciliation. Company value: Make review environments predictable, isolated, and accountable to a budget. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### BENV-104 — Seed synthetic review data in isolated namespaces **Task · High priority · Intermediate** noCV practice brief v5 · BENV-104 · Ephemeral review-environment lifecycle Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Manage lifecycle. Depends on: BENV-103. Difficulty: Intermediate. Estimated focused work: 150 minutes; setup and prerequisite tickets are additional. Estimated field mix: Security 50% · Cloud infrastructure 30% · Database engineering 20%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Two previews share account records and interfere with each other's review. Acceptance criteria - Assign a unique data namespace per environment. - Seed only synthetic records. - Deny reads across environment namespaces. Implementation constraints - Never copy production user data into previews. Verification - Run two previews with identical synthetic usernames. - Verify cross-environment reads and cleanup are denied. Deliverables - Isolated seed workflow. Rollout and recovery: Validate isolation before marking environments ready. Project prerequisites: Author a local environment-provider double and synthetic pull-request events; provision no external resources. Engineer value: Practice resource lifecycle state machines, isolation, and reconciliation. Company value: Make review environments predictable, isolated, and accountable to a budget. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### BENV-105 — Bind preview URLs and callbacks to the environment origin **Bug · High priority · Advanced** noCV practice brief v5 · BENV-105 · Ephemeral review-environment lifecycle Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Manage lifecycle. Depends on: BENV-104. Difficulty: Advanced. Estimated focused work: 180 minutes; setup and prerequisite tickets are additional. Estimated field mix: Security 70% · Cloud infrastructure 30%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. A preview callback redirects to an unrelated origin supplied in change metadata. Acceptance criteria - Derive allowed origins from trusted environment state. - Reject arbitrary redirect and callback destinations. - Expire origin authority when the environment closes. Implementation constraints - Use local URLs and do not contact external hosts. Verification - Accept the environment's declared local callback. - Reject a substituted external origin and stale environment. Deliverables - Origin binding guard. Rollout and recovery: Expose preview links only after origin validation. Project prerequisites: Author a local environment-provider double and synthetic pull-request events; provision no external resources. Engineer value: Practice resource lifecycle state machines, isolation, and reconciliation. Company value: Make review environments predictable, isolated, and accountable to a budget. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### BENV-106 — Expire environments using leases rather than event delivery alone **Task · High priority · Advanced** noCV practice brief v5 · BENV-106 · Ephemeral review-environment lifecycle Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Manage lifecycle. Depends on: BENV-103, BENV-105. Difficulty: Advanced. Estimated focused work: 180 minutes; setup and prerequisite tickets are additional. Estimated field mix: Cloud infrastructure 50% · Distributed systems 30% · Platform engineering 20%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. A missed close event leaves a preview running indefinitely. Acceptance criteria - Persist expiry and extension revisions. - Reclaim expired environments through a periodic scan. - Reject stale extensions after cleanup starts. Implementation constraints - Lifecycle state changes use explicit transitions. Verification - Expire an environment with no close event. - Race extension and cleanup without resurrecting deleted state. Deliverables - Lease-based expiry. Rollout and recovery: Start with dry-run expiry reports; enable cleanup after ownership checks. Project prerequisites: Author a local environment-provider double and synthetic pull-request events; provision no external resources. Engineer value: Practice resource lifecycle state machines, isolation, and reconciliation. Company value: Make review environments predictable, isolated, and accountable to a budget. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### BENV-107 — Reconcile partially created environments after provider failure **Bug · High priority · Advanced** noCV practice brief v5 · BENV-107 · Ephemeral review-environment lifecycle Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Manage lifecycle. Depends on: BENV-103, BENV-106. Difficulty: Advanced. Estimated focused work: 210 minutes; setup and prerequisite tickets are additional. Estimated field mix: Cloud infrastructure 50% · Distributed systems 30% · Site reliability 20%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. The database resource exists but the web resource failed, leaving an unusable partial preview. Acceptance criteria - Record each provider resource identity. - Resume or compensate according to lifecycle policy. - Release quota only after owned resources are accounted for. Implementation constraints - Never delete resources without matching ownership metadata. Verification - Recover a partially created preview. - Encounter a foreign resource and stop compensation safely. Deliverables - Partial-creation reconciler. Rollout and recovery: Keep the environment unavailable until complete; retain reconciliation history. Project prerequisites: Author a local environment-provider double and synthetic pull-request events; provision no external resources. Engineer value: Practice resource lifecycle state machines, isolation, and reconciliation. Company value: Make review environments predictable, isolated, and accountable to a budget. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. ### Operate within bounds Verify cleanup safety and cost controls. #### BENV-108 — Produce a cleanup plan that proves exact resource ownership **Task · High priority · Intermediate** noCV practice brief v5 · BENV-108 · Ephemeral review-environment lifecycle Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Operate within bounds. Depends on: BENV-107. Difficulty: Intermediate. Estimated focused work: 150 minutes; setup and prerequisite tickets are additional. Estimated field mix: Security 50% · Cloud infrastructure 50%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. A broad name-prefix cleanup could delete another team's preview. Acceptance criteria - List exact resource IDs and ownership bindings. - Bind deletion intent to lifecycle revision. - Reject changed ownership or active lease. Implementation constraints - Cleanup applies only to the local provider double. Verification - Delete an expired owned environment. - Reject a foreign or newly extended resource. Deliverables - Reviewed cleanup plan. Rollout and recovery: Use dry-run output first; stop on any ownership mismatch. Project prerequisites: Author a local environment-provider double and synthetic pull-request events; provision no external resources. Engineer value: Practice resource lifecycle state machines, isolation, and reconciliation. Company value: Make review environments predictable, isolated, and accountable to a budget. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### BENV-109 — Compare pooled and dedicated preview dependencies **Task · High priority · Expert** noCV practice brief v5 · BENV-109 · Ephemeral review-environment lifecycle Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Operate within bounds. Depends on: BENV-104, BENV-108. Difficulty: Expert. Estimated focused work: 300 minutes; setup and prerequisite tickets are additional. Estimated field mix: System design 40% · Cloud infrastructure 40% · Security 20%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Dedicated databases simplify isolation but cost more than a shared instance with namespaces. Acceptance criteria - Compare isolation, startup time, cleanup, and quota assumptions. - Rehearse cross-environment denial for the pooled option. - Document failure domains and untested provider behavior. Implementation constraints - No speculative infrastructure is required beyond the local model. Verification - Evaluate both options against the same synthetic review workload. - Reject a cheaper option that fails isolation requirements. Deliverables - Preview architecture decision record. Rollout and recovery: Choose the smallest option satisfying isolation; keep migration and cleanup steps explicit. Project prerequisites: Author a local environment-provider double and synthetic pull-request events; provision no external resources. Engineer value: Practice resource lifecycle state machines, isolation, and reconciliation. Company value: Make review environments predictable, isolated, and accountable to a budget. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence. #### BENV-110 — Write a stale-preview support checklist **Chore · Low priority · Foundational** noCV practice brief v5 · BENV-110 · Ephemeral review-environment lifecycle Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Operate within bounds. Depends on: BENV-109. Difficulty: Foundational. Estimated focused work: 60 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 40% · Cloud infrastructure 30% · Site reliability 30%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Reviewers need to know whether a broken preview is creating, expired, or awaiting cleanup. Acceptance criteria - Expose lifecycle state and last safe failure category. - Show owner, expiry, and review identity. - Document scoped retry and extension behavior. Implementation constraints - Status contains no credentials or seed data. Verification - Diagnose an expired synthetic preview. - Reject extension after irreversible cleanup begins. Deliverables - Preview support guide. Rollout and recovery: Ship with lifecycle controls and update after state changes. Project prerequisites: Author a local environment-provider double and synthetic pull-request events; provision no external resources. Engineer value: Practice resource lifecycle state machines, isolation, and reconciliation. Company value: Make review environments predictable, isolated, and accountable to a budget. AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior. Planning status does not create Outcome Evidence or Ownership Evidence.