# 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. ## CFORM — A procurement form that protects drafts Fictional procurement team Northroom collects purchase requests in a browser form. Work uses local stubs and cannot place purchases. **Field:** Frontend. **Suggested stack:** React, TypeScript, CSS Modules, Playwright. **Engineer value:** Practice state boundaries and form schema transitions. **Company value:** Inspect how hidden obsolete data and duplicate requests are prevented. **Delivery agreement:** Submit each form behavior as a separate change. ### Setup prerequisites - Create synthetic categories and conditional request fields. - Stub draft revisions and submission outcomes. ### Clarify fields Specify amounts and conditional values. #### CFORM-101 — Preserve procurement amount precision during editing **Bug · Medium priority · Foundational** noCV practice brief v5 · CFORM-101 · A procurement form that protects drafts Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Clarify fields. Depends on: No preceding ticket. Difficulty: Foundational. Estimated focused work: 75 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 100%. Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence. Entered 19.90 becomes 19.9 and later rounds. Separate edit text from validated minor units. Acceptance criteria - Review uses currency precision - Incomplete text stays editable - Excess precision blocks submit Implementation constraints - Parse decimals without binary float arithmetic. Verification - Review 19.90 - Enter excess decimal places Deliverables - Amount parser and field cases Rollout and recovery: Revert formatting while retaining minor-unit storage. Project prerequisites: Create synthetic categories and conditional request fields. Stub draft revisions and submission outcomes. Engineer value: Practice state boundaries and form schema transitions. Company value: Inspect how hidden obsolete data and duplicate requests are prevented. 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. #### CFORM-102 — Link procurement error summaries to affected fields **Story · Medium priority · Foundational** noCV practice brief v5 · CFORM-102 · A procurement form that protects drafts Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Clarify fields. Depends on: No preceding ticket. Difficulty: Foundational. Estimated focused work: 75 minutes; setup and prerequisite tickets are additional. Estimated field mix: Accessibility 60% · Frontend 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. Required fields missing gives no location. Add field errors and a navigable summary. Acceptance criteria - Summary links focus fields - Labels expose required state - Corrections clear only relevant errors Implementation constraints - Use stable description IDs. Verification - Follow summary link - Submit several missing values Deliverables - Summary and keyboard checks Rollout and recovery: Retain field errors if summary navigation fails. Project prerequisites: Create synthetic categories and conditional request fields. Stub draft revisions and submission outcomes. Engineer value: Practice state boundaries and form schema transitions. Company value: Inspect how hidden obsolete data and duplicate requests are prevented. 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. #### CFORM-103 — Remove obsolete shipping fields on procurement category changes **Bug · High priority · Intermediate** noCV practice brief v5 · CFORM-103 · A procurement form that protects drafts Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Clarify fields. Depends on: CFORM-101. Difficulty: Intermediate. Estimated focused work: 120 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 80% · Privacy 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. Switching hardware to services retains a hidden shipping address in the payload. Make conditional removal explicit. Acceptance criteria - Payload excludes inactive fields - Discard prompts identify entered data - Cancel preserves category Implementation constraints - Hidden inputs are not a serialization policy. Verification - Switch empty category - Cancel populated category switch Deliverables - Conditional payload projection Rollout and recovery: Disable category changes until removal is corrected. Project prerequisites: Create synthetic categories and conditional request fields. Stub draft revisions and submission outcomes. Engineer value: Practice state boundaries and form schema transitions. Company value: Inspect how hidden obsolete data and duplicate requests are prevented. 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. ### Protect progress Recover drafts and schema changes. #### CFORM-104 — Allow earlier procurement corrections after final-step errors **Task · Medium priority · Intermediate** noCV practice brief v5 · CFORM-104 · A procurement form that protects drafts Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Protect progress. Depends on: CFORM-102, CFORM-103. Difficulty: Intermediate. Estimated focused work: 120 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 100%. 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 final-step error blocks users from returning to fix amounts. Separate navigation from submission validity. Acceptance criteria - Back stays available - Forward validates applicable step - Submit validates full active payload Implementation constraints - Share one validation contract. Verification - Correct earlier amount - Fail final validation and go Back Deliverables - Step validation coordinator Rollout and recovery: Fall back to a single-page form. Project prerequisites: Create synthetic categories and conditional request fields. Stub draft revisions and submission outcomes. Engineer value: Practice state boundaries and form schema transitions. Company value: Inspect how hidden obsolete data and duplicate requests are prevented. 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. #### CFORM-105 — Show acknowledged and unsaved procurement draft states **Story · High priority · Advanced** noCV practice brief v5 · CFORM-105 · A procurement form that protects drafts Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Protect progress. Depends on: CFORM-104. Difficulty: Advanced. Estimated focused work: 165 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 70% · API design 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. Failed autosaves look saved. Track acknowledgements without interrupting editing. Acceptance criteria - Saved means acknowledged revision - Failure retains edits - Late acknowledgement cannot mark newer edits saved Implementation constraints - Debouncing cannot establish revision ownership. Verification - Save then edit - Resolve saves out of order Deliverables - Draft states and race tests Rollout and recovery: Disable autosave and expose explicit save. Project prerequisites: Create synthetic categories and conditional request fields. Stub draft revisions and submission outcomes. Engineer value: Practice state boundaries and form schema transitions. Company value: Inspect how hidden obsolete data and duplicate requests are prevented. 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. #### CFORM-106 — Stop conflicting procurement saves from another tab **Bug · High priority · Advanced** noCV practice brief v5 · CFORM-106 · A procurement form that protects drafts Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Protect progress. Depends on: CFORM-105. Difficulty: Advanced. Estimated focused work: 180 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 60% · API design 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. Two tabs silently overwrite a draft. Require expected revisions and preserve conflicting local work. Acceptance criteria - Stale writes fail visibly - Local edits remain recoverable - Reconciliation is explicit Implementation constraints - Browser warnings cannot replace revision checks. Verification - Save one tab - Submit stale save in second Deliverables - Multi-tab conflict flow Rollout and recovery: Pause writes on unresolved conflict. Project prerequisites: Create synthetic categories and conditional request fields. Stub draft revisions and submission outcomes. Engineer value: Practice state boundaries and form schema transitions. Company value: Inspect how hidden obsolete data and duplicate requests are prevented. 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. #### CFORM-107 — Migrate one procurement draft schema transition **Task · High priority · Expert** noCV practice brief v5 · CFORM-107 · A procurement form that protects drafts Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Protect progress. Depends on: CFORM-103, CFORM-105. Difficulty: Expert. Estimated focused work: 240 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 100%. 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 category field changes shape while drafts remain open. Add one deterministic version migration. Acceptance criteria - Old version migrates predictably - Future versions stay read-only - Dropped fields appear in review Implementation constraints - Preserve original draft until acknowledgement. Verification - Migrate old fixture - Open unsupported future version Deliverables - Migration and preserved-original cases Rollout and recovery: Restore old reader using preserved drafts. Project prerequisites: Create synthetic categories and conditional request fields. Stub draft revisions and submission outcomes. Engineer value: Practice state boundaries and form schema transitions. Company value: Inspect how hidden obsolete data and duplicate requests are prevented. 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. ### Submit deliberately Bind review to confirmed writes. #### CFORM-108 — Bind procurement review to the exact submission snapshot **Story · Medium priority · Intermediate** noCV practice brief v5 · CFORM-108 · A procurement form that protects drafts Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Submit deliberately. Depends on: CFORM-104, CFORM-107. Difficulty: Intermediate. Estimated focused work: 135 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 80% · API design 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. Review recomputes defaults differently from submit. Create one validated snapshot for both. Acceptance criteria - Review matches sent values - Editing invalidates review - Inactive fields are excluded Implementation constraints - Confirmation identifies snapshot revision. Verification - Review and submit unchanged - Edit amount after review Deliverables - Snapshot projection and checks Rollout and recovery: Disable submit if snapshot matching fails. Project prerequisites: Create synthetic categories and conditional request fields. Stub draft revisions and submission outcomes. Engineer value: Practice state boundaries and form schema transitions. Company value: Inspect how hidden obsolete data and duplicate requests are prevented. 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. #### CFORM-109 — Reconcile uncertain procurement submissions before retrying **Bug · High priority · Advanced** noCV practice brief v5 · CFORM-109 · A procurement form that protects drafts Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Submit deliberately. Depends on: CFORM-108. Difficulty: Advanced. Estimated focused work: 180 minutes; setup and prerequisite tickets are additional. Estimated field mix: Frontend 50% · API design 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. A timeout followed by retry creates duplicate requests. Retain one submission key until resolved. Acceptance criteria - Retry reuses key - Success locks snapshot - Unknown outcomes expose status lookup Implementation constraints - Timeout alone cannot prove failure. Verification - Submit then retry - Timeout after adapter acceptance Deliverables - Submission coordinator and timeout case Rollout and recovery: Pause retries while allowing lookup. Project prerequisites: Create synthetic categories and conditional request fields. Stub draft revisions and submission outcomes. Engineer value: Practice state boundaries and form schema transitions. Company value: Inspect how hidden obsolete data and duplicate requests are prevented. 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. #### CFORM-110 — Export one recoverable procurement draft without session data **Chore · Low priority · Intermediate** noCV practice brief v5 · CFORM-110 · A procurement form that protects drafts Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Submit deliberately. Depends on: CFORM-106, CFORM-109. Difficulty: Intermediate. Estimated focused work: 105 minutes; setup and prerequisite tickets are additional. Estimated field mix: Privacy engineering 60% · Frontend 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. Support requests whole browser storage to recover drafts. Offer scoped, previewed export instead. Acceptance criteria - Preview lists included fields - Session tokens are omitted - Invalid drafts export as drafts Implementation constraints - Never trust exported content as HTML. Verification - Export current draft - Check other drafts and tokens are absent Deliverables - Draft export and scope checks Rollout and recovery: Remove export if isolation fails. Project prerequisites: Create synthetic categories and conditional request fields. Stub draft revisions and submission outcomes. Engineer value: Practice state boundaries and form schema transitions. Company value: Inspect how hidden obsolete data and duplicate requests are prevented. 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.