# 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. ## AENV — Make ephemeral review environments predictable A fictional team creates preview stacks for pull requests. Orphan databases consume resources and previews sometimes inherit settings intended for another branch. **Field:** Platform engineering. **Suggested stack:** TypeScript, Compose specification, PostgreSQL. **Engineer value:** Practice resource lifecycle, reconciliation and least-privilege setup. **Company value:** Review reliable preview workflows and accountable resource cleanup. **Delivery agreement:** Ten scoped tickets across three phases. Build a synthetic local service or select a ticket after recreating its prerequisites; estimates exclude setup. ### Setup prerequisites - Create a local provisioning adapter with synthetic repository events. - Use isolated disposable resources and no production credentials. ### Plan isolated previews Validate requests and resource boundaries. #### AENV-101 — Validate preview requests before allocating resources **Task · Medium priority · Foundational** noCV practice brief v5 · AENV-101 · Make ephemeral review environments predictable Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Plan isolated previews. Depends on: No preceding ticket. Difficulty: Foundational. Estimated focused work: 90 minutes; setup and prerequisite tickets are additional. Estimated field mix: Platform engineering 60% · API design 20% · 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. A branch name containing slashes and punctuation becomes an invalid database name after resources are already created. Acceptance criteria - Use an opaque environment ID for resource names. - Validate repository scope, revision and requested lifetime. - Reject malformed requests before any provider call. Implementation constraints - Treat branch labels as display data only. Verification - Accept a valid synthetic revision with a complex branch label. - Reject missing scope and excessive lifetime with zero allocation calls. Deliverables - Preview request schema Rollout and recovery: Enable request validation first; leave rejected previews unallocated. Project prerequisites: Create a local provisioning adapter with synthetic repository events. Use isolated disposable resources and no production credentials. Engineer value: Practice resource lifecycle, reconciliation and least-privilege setup. Company value: Review reliable preview workflows and accountable resource cleanup. 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. #### AENV-102 — Create a review-environment resource plan with an explicit quota **Task · Medium priority · Intermediate** noCV practice brief v5 · AENV-102 · Make ephemeral review environments predictable Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Plan isolated previews. Depends on: AENV-101. Difficulty: Intermediate. Estimated focused work: 150 minutes; setup and prerequisite tickets are additional. Estimated field mix: Platform engineering 60% · Cloud infrastructure 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. One preview requests every optional dependency and exhausts the local resource budget. Acceptance criteria - List CPU, memory, storage and lifetime requirements. - Reject plans exceeding per-environment or aggregate quotas. - Keep optional dependencies explicit rather than provisioned by default. Implementation constraints - Use documented synthetic quotas and a dry-run planner. Verification - Plan a minimal API and database preview. - Exceed storage and concurrent-environment quotas and reject allocation. Deliverables - Quota-aware plan command Rollout and recovery: Expose dry-run plans first; reduce admitted previews if available resources shrink. Project prerequisites: Create a local provisioning adapter with synthetic repository events. Use isolated disposable resources and no production credentials. Engineer value: Practice resource lifecycle, reconciliation and least-privilege setup. Company value: Review reliable preview workflows and accountable resource cleanup. 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. #### AENV-103 — Keep preview connection material out of build output **Bug · High priority · Foundational** noCV practice brief v5 · AENV-103 · Make ephemeral review environments predictable Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Plan isolated previews. Depends on: AENV-101. Difficulty: Foundational. Estimated focused work: 75 minutes; setup and prerequisite tickets are additional. Estimated field mix: Security 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. Provisioning logs print database URLs that contain temporary credentials. Acceptance criteria - Redact passwords, tokens and credential-bearing URLs. - Return secret references separately from public preview metadata. - Keep synthetic credentials out of generated manifests. Implementation constraints - Use allowlisted structured logging fields. Verification - Inspect successful provisioning logs for safe identifiers. - Inject a credential into provider errors and assert redaction. Deliverables - Log redaction and metadata projection Rollout and recovery: Deploy redaction before provisioning; rotate any affected disposable credentials. Project prerequisites: Create a local provisioning adapter with synthetic repository events. Use isolated disposable resources and no production credentials. Engineer value: Practice resource lifecycle, reconciliation and least-privilege setup. Company value: Review reliable preview workflows and accountable resource cleanup. 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. ### Reconcile environment state Make setup and updates repeatable. #### AENV-104 — Make preview creation resumable after a partial provider failure **Story · High priority · Advanced** noCV practice brief v5 · AENV-104 · Make ephemeral review environments predictable Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Reconcile environment state. Depends on: AENV-102, AENV-103. Difficulty: Advanced. Estimated focused work: 240 minutes; setup and prerequisite tickets are additional. Estimated field mix: Platform engineering 50% · Cloud infrastructure 30% · Distributed systems 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 is created but the API startup fails; retry creates a second database and loses track of the first. Acceptance criteria - Assign deterministic resource identities per environment generation. - Record each completed allocation before moving to the next. - Resume from observed resources instead of blindly recreating them. Implementation constraints - Use a provider interface with injected failure points. Verification - Fail after database creation and resume to one database. - Return an unexpected existing resource owner and halt without adoption. Deliverables - Reconciliation loop and partial-failure probe Rollout and recovery: Canary local environments; pause allocation while retaining resource records on inconsistency. Project prerequisites: Create a local provisioning adapter with synthetic repository events. Use isolated disposable resources and no production credentials. Engineer value: Practice resource lifecycle, reconciliation and least-privilege setup. Company value: Review reliable preview workflows and accountable resource cleanup. 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. #### AENV-105 — Bind preview updates to the exact requested source revision **Bug · Medium priority · Advanced** noCV practice brief v5 · AENV-105 · Make ephemeral review environments predictable Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Reconcile environment state. Depends on: AENV-104. Difficulty: Advanced. Estimated focused work: 210 minutes; setup and prerequisite tickets are additional. Estimated field mix: Platform engineering 60% · Distributed systems 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. A slow build for an older commit finishes after a newer build and replaces the current preview. Acceptance criteria - Track requested generation and source revision. - Only the current generation may become active. - Keep stale build artifacts visible for cleanup but never route traffic to them. Implementation constraints - Do not treat completion time as revision order. Verification - Complete two builds in reverse order and activate only the latest requested one. - Retry stale activation and preserve the selected generation. Deliverables - Generation guard and completion-order tests Rollout and recovery: Enable guarded routing; restore the prior valid generation if the new one fails readiness. Project prerequisites: Create a local provisioning adapter with synthetic repository events. Use isolated disposable resources and no production credentials. Engineer value: Practice resource lifecycle, reconciliation and least-privilege setup. Company value: Review reliable preview workflows and accountable resource cleanup. 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. #### AENV-106 — Initialize preview data from a synthetic schema contract **Story · Medium priority · Intermediate** noCV practice brief v5 · AENV-106 · Make ephemeral review environments predictable Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Reconcile environment state. Depends on: AENV-104, AENV-105. Difficulty: Intermediate. Estimated focused work: 180 minutes; setup and prerequisite tickets are additional. Estimated field mix: Platform engineering 40% · Quality engineering 30% · Database 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. Preview startup depends on a copy of production data, making reviews slow and difficult to share safely. Acceptance criteria - Create deterministic synthetic records covering declared UI states. - Apply migrations before seeding the environment. - Fail readiness when the seed contract is incomplete. Implementation constraints - Do not import real customer data or production secrets. Verification - Create two previews and compare declared synthetic identities and states. - Fail a migration and verify the seed does not mark the environment ready. Deliverables - Synthetic seed command and readiness checks Rollout and recovery: Enable the seed on new previews; recreate disposable data if the contract changes. Project prerequisites: Create a local provisioning adapter with synthetic repository events. Use isolated disposable resources and no production credentials. Engineer value: Practice resource lifecycle, reconciliation and least-privilege setup. Company value: Review reliable preview workflows and accountable resource cleanup. 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. #### AENV-107 — Probe readiness without accidentally validating only process liveness **Task · Medium priority · Advanced** noCV practice brief v5 · AENV-107 · Make ephemeral review environments predictable Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Reconcile environment state. Depends on: AENV-105, AENV-106. Difficulty: Advanced. Estimated focused work: 180 minutes; setup and prerequisite tickets are additional. Estimated field mix: Platform engineering 60% · Site reliability 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. The preview link is published while migrations are still running, so reviewers immediately hit missing-table errors. Acceptance criteria - Readiness checks required dependencies and schema version. - Liveness remains independent of external dependency availability. - Publish the link only after the current generation passes readiness. Implementation constraints - Bound probe time and omit secret diagnostics. Verification - Start a complete preview and publish its link. - Delay migration completion and assert no ready link is announced. Deliverables - Readiness contract and startup timeline Rollout and recovery: Canary readiness gating; suppress links and inspect the generation on repeated failures. Project prerequisites: Create a local provisioning adapter with synthetic repository events. Use isolated disposable resources and no production credentials. Engineer value: Practice resource lifecycle, reconciliation and least-privilege setup. Company value: Review reliable preview workflows and accountable resource cleanup. 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. ### Retire environments safely Detect expiration and recover incomplete cleanup. #### AENV-108 — Expire review environments with a grace period and owner visibility **Story · Medium priority · Foundational** noCV practice brief v5 · AENV-108 · Make ephemeral review environments predictable Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Retire environments safely. Depends on: AENV-104, AENV-107. Difficulty: Foundational. Estimated focused work: 90 minutes; setup and prerequisite tickets are additional. Estimated field mix: Platform engineering 60% · Cloud infrastructure 20% · 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. A preview remains allocated after its pull request closes because nobody owns the cleanup schedule. Acceptance criteria - Persist owner token, expiry instant and grace deadline. - List expiring environments without exposing credentials. - Allow authorized extension within the declared maximum lifetime. Implementation constraints - Use an injectable clock and synthetic ownership. Verification - Advance through expiry and grace states. - Attempt extension by another owner and reject it. Deliverables - Expiry state model and owner view Rollout and recovery: Enable expiry reporting before cleanup; extend only reviewed environments during adoption. Project prerequisites: Create a local provisioning adapter with synthetic repository events. Use isolated disposable resources and no production credentials. Engineer value: Practice resource lifecycle, reconciliation and least-privilege setup. Company value: Review reliable preview workflows and accountable resource cleanup. 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. #### AENV-109 — Delete only resources owned by the retired preview generation **Task · High priority · Expert** noCV practice brief v5 · AENV-109 · Make ephemeral review environments predictable Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Retire environments safely. Depends on: AENV-105, AENV-108. Difficulty: Expert. Estimated focused work: 300 minutes; setup and prerequisite tickets are additional. Estimated field mix: Platform engineering 50% · Cloud infrastructure 30% · 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. A cleanup job matches resource names by prefix and can remove a newer generation sharing the same branch label. Acceptance criteria - Match exact environment, generation and ownership tags. - Refuse deletion for missing or contradictory ownership. - Make retries converge after partial deletion. Implementation constraints - Provider deletion receives exact resource IDs, never wildcard names. Verification - Retire an old generation while keeping the new one usable. - Alter an ownership tag and verify cleanup stops before deletion. Deliverables - Ownership-checked cleanup and isolation tests Rollout and recovery: Dry-run deletion plans first; pause cleanup and preserve unresolved resources on ownership conflicts. Project prerequisites: Create a local provisioning adapter with synthetic repository events. Use isolated disposable resources and no production credentials. Engineer value: Practice resource lifecycle, reconciliation and least-privilege setup. Company value: Review reliable preview workflows and accountable resource cleanup. 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. #### AENV-110 — Reconcile orphan preview resources into an auditable cleanup queue **Chore · Medium priority · Expert** noCV practice brief v5 · AENV-110 · Make ephemeral review environments predictable Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Retire environments safely. Depends on: AENV-104, AENV-109. Difficulty: Expert. Estimated focused work: 300 minutes; setup and prerequisite tickets are additional. Estimated field mix: Platform engineering 50% · Cloud infrastructure 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. A process crashed before saving its final resource record; local storage now contains an environment no active preview references. Acceptance criteria - Compare provider inventory to durable environment generations. - Classify owned orphan, active and unknown resources. - Require review of unknown ownership before any deletion. Implementation constraints - Bound inventory scans and retain an immutable reconciliation report. Verification - Discover an owned orphan and propose exact cleanup identities. - Present an untagged resource and verify it is never automatically removed. Deliverables - Orphan inventory command and cleanup report Rollout and recovery: Run read-only first; execute only reviewed owned-orphan plans and stop on inventory drift. Project prerequisites: Create a local provisioning adapter with synthetic repository events. Use isolated disposable resources and no production credentials. Engineer value: Practice resource lifecycle, reconciliation and least-privilege setup. Company value: Review reliable preview workflows and accountable resource cleanup. 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.