# 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. ## CCONFIG — Versioned edge configuration with an offline gateway Fictional information-display gateways receive brightness schedules and cache limits. These settings affect only a software display emulator; no real devices, safety controls or customer data are used. **Field:** Embedded and edge. **Suggested stack:** TypeScript, Gateway emulator, SQLite adapter, Vitest. **Engineer value:** Practice desired/reported state, compatibility and rollback. **Company value:** Inspect whether remote configuration preserves working settings through offline and partial outcomes. **Delivery agreement:** Deliver local simulation changes; hardware validation and external fleet deployment are excluded. ### Setup prerequisites - Define synthetic configuration schema and supported device capabilities. - Implement local control-plane and gateway adapters with delayed messages. ### Specify configuration contracts Validate and scope desired settings. #### CCONFIG-101 — Validate emulated display brightness and cache-limit settings **Task · Medium priority · Foundational** noCV practice brief v5 · CCONFIG-101 · Versioned edge configuration with an offline gateway Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Specify configuration contracts. Depends on: No preceding ticket. Difficulty: Foundational. Estimated focused work: 75 minutes; setup and prerequisite tickets are additional. Estimated field mix: Embedded and edge 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. The gateway accepts negative cache capacity and brightness above the declared range. Add a bounded schema. Acceptance criteria - Supported ranges pass - Unknown fields reject - Invalid settings do not alter active state Implementation constraints - Schema limits are emulator contracts, not hardware ratings. Verification - Apply valid fixture values - Reject negative and oversized settings Deliverables - Configuration schema and cases Rollout and recovery: Reject incoming updates if schema validation fails. Project prerequisites: Define synthetic configuration schema and supported device capabilities. Implement local control-plane and gateway adapters with delayed messages. Engineer value: Practice desired/reported state, compatibility and rollback. Company value: Inspect whether remote configuration preserves working settings through offline and partial outcomes. 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. #### CCONFIG-102 — Keep desired and reported edge configuration separate **Bug · Medium priority · Foundational** noCV practice brief v5 · CCONFIG-102 · Versioned edge configuration with an offline gateway Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Specify configuration contracts. Depends on: CCONFIG-101. Difficulty: Foundational. Estimated focused work: 75 minutes; setup and prerequisite tickets are additional. Estimated field mix: Embedded and edge 50% · Distributed systems 30% · Frontend 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. Sending a setting immediately changes the dashboard to Applied before the gateway responds. Store separate desired and reported revisions. Acceptance criteria - Sending changes desired state - Acknowledgement changes reported state - Mismatch appears as pending drift Implementation constraints - Delivery is not application acknowledgement. Verification - Send then acknowledge - Drop delivery and inspect drift Deliverables - State model and projection cases Rollout and recovery: Stop displaying Applied when acknowledgement is absent. Project prerequisites: Define synthetic configuration schema and supported device capabilities. Implement local control-plane and gateway adapters with delayed messages. Engineer value: Practice desired/reported state, compatibility and rollback. Company value: Inspect whether remote configuration preserves working settings through offline and partial outcomes. 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. #### CCONFIG-103 — Scope emulated gateway configuration reads by organization **Task · High priority · Intermediate** noCV practice brief v5 · CCONFIG-103 · Versioned edge configuration with an offline gateway Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Specify configuration contracts. Depends on: CCONFIG-101, CCONFIG-102. Difficulty: Intermediate. Estimated focused work: 120 minutes; setup and prerequisite tickets are additional. Estimated field mix: Security 70% · Embedded and edge 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 guessed gateway ID exposes another organization's desired settings. Enforce tenant scope at repository lookup. Acceptance criteria - Owner reads permitted gateway - Foreign lookup is denied - Denied response omits settings Implementation constraints - Synthetic gateway IDs never establish authority alone. Verification - Read own fixture - Read foreign gateway by known ID Deliverables - Scoped repository and denial cases Rollout and recovery: Disable configuration reads when ownership cannot be verified. Project prerequisites: Define synthetic configuration schema and supported device capabilities. Implement local control-plane and gateway adapters with delayed messages. Engineer value: Practice desired/reported state, compatibility and rollback. Company value: Inspect whether remote configuration preserves working settings through offline and partial outcomes. 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. ### Apply settings deliberately Handle revisions and partial failures. #### CCONFIG-104 — Reject stale configuration revisions arriving at the edge gateway **Bug · High priority · Advanced** noCV practice brief v5 · CCONFIG-104 · Versioned edge configuration with an offline gateway Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Apply settings deliberately. Depends on: CCONFIG-102, CCONFIG-103. Difficulty: Advanced. Estimated focused work: 165 minutes; setup and prerequisite tickets are additional. Estimated field mix: Distributed systems 60% · Embedded and edge 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. Delayed delivery overwrites a newer brightness schedule. Compare monotonic desired revisions before applying. Acceptance criteria - Newer revision may apply - Older revision is rejected - Equal matching revision replays safely Implementation constraints - Reused revision with different payload is a conflict. Verification - Deliver increasing revisions - Deliver old or conflicting revision Deliverables - Revision guard and ordering cases Rollout and recovery: Request a fresh authoritative snapshot on conflict. Project prerequisites: Define synthetic configuration schema and supported device capabilities. Implement local control-plane and gateway adapters with delayed messages. Engineer value: Practice desired/reported state, compatibility and rollback. Company value: Inspect whether remote configuration preserves working settings through offline and partial outcomes. 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. #### CCONFIG-105 — Stage edge settings before committing a complete configuration **Task · High priority · Advanced** noCV practice brief v5 · CCONFIG-105 · Versioned edge configuration with an offline gateway Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Apply settings deliberately. Depends on: CCONFIG-101, CCONFIG-104. Difficulty: Advanced. Estimated focused work: 180 minutes; setup and prerequisite tickets are additional. Estimated field mix: Embedded and edge 60% · Storage 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. Applying brightness succeeds while cache settings fail, leaving an undocumented mixed state. Validate and stage the complete supported configuration. Acceptance criteria - All fields validate before mutation - Commit selects one complete revision - Failure retains prior active revision Implementation constraints - This ticket assumes reversible emulator setters; document that boundary. Verification - Apply valid full revision - Inject failure during staging Deliverables - Staged apply protocol and failure cases Rollout and recovery: Restore previous configuration if staging cannot remain isolated. Project prerequisites: Define synthetic configuration schema and supported device capabilities. Implement local control-plane and gateway adapters with delayed messages. Engineer value: Practice desired/reported state, compatibility and rollback. Company value: Inspect whether remote configuration preserves working settings through offline and partial outcomes. 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. #### CCONFIG-106 — Reject edge settings unsupported by the declared gateway capability version **Story · Medium priority · Intermediate** noCV practice brief v5 · CCONFIG-106 · Versioned edge configuration with an offline gateway Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Apply settings deliberately. Depends on: CCONFIG-104, CCONFIG-105. Difficulty: Intermediate. Estimated focused work: 135 minutes; setup and prerequisite tickets are additional. Estimated field mix: Embedded and edge 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. Older gateway emulators silently ignore new settings while reporting success. Check capability compatibility explicitly. Acceptance criteria - Supported configuration applies - Unsupported fields report incompatibility - Reported revision does not advance on rejection Implementation constraints - Do not infer capability from device display names. Verification - Apply to compatible fixture - Apply new field to older capability Deliverables - Compatibility check and cases Rollout and recovery: Keep existing revision on unsupported gateways. Project prerequisites: Define synthetic configuration schema and supported device capabilities. Implement local control-plane and gateway adapters with delayed messages. Engineer value: Practice desired/reported state, compatibility and rollback. Company value: Inspect whether remote configuration preserves working settings through offline and partial outcomes. 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. #### CCONFIG-107 — Persist edge-configuration acknowledgement after active settings commit **Bug · High priority · Expert** noCV practice brief v5 · CCONFIG-107 · Versioned edge configuration with an offline gateway Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Apply settings deliberately. Depends on: CCONFIG-105, CCONFIG-106. Difficulty: Expert. Estimated focused work: 240 minutes; setup and prerequisite tickets are additional. Estimated field mix: Embedded and edge 40% · Storage systems 30% · Distributed systems 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 crash after applying settings but before reporting leaves the control plane uncertain and repeated applies inconsistent. Reconcile local active revision on restart. Acceptance criteria - Active revision persists with settings - Restart can replay acknowledgement - Uncommitted settings cannot be reported applied Implementation constraints - Define commit ordering in the local adapter. Verification - Crash after settings commit - Crash before commit Deliverables - Apply journal and restart cases Rollout and recovery: Pause new applies until active-state reconciliation completes. Project prerequisites: Define synthetic configuration schema and supported device capabilities. Implement local control-plane and gateway adapters with delayed messages. Engineer value: Practice desired/reported state, compatibility and rollback. Company value: Inspect whether remote configuration preserves working settings through offline and partial outcomes. 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. ### Recover gateway state Explain offline drift and bound retries. #### CCONFIG-108 — Coalesce offline edge configuration deliveries to the latest eligible revision **Task · Medium priority · Advanced** noCV practice brief v5 · CCONFIG-108 · Versioned edge configuration with an offline gateway Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Recover gateway state. Depends on: CCONFIG-104, CCONFIG-107. Difficulty: Advanced. Estimated focused work: 180 minutes; setup and prerequisite tickets are additional. Estimated field mix: Distributed systems 60% · Embedded and edge 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 gateway reconnects to hundreds of obsolete brightness changes. Deliver the latest complete eligible snapshot deliberately. Acceptance criteria - Obsolete pending revisions are superseded - Latest revision remains auditable - Required transition constraints are checked Implementation constraints - Coalescing is permitted only for this replaceable configuration contract. Verification - Reconnect after several revisions - Include incompatible latest revision Deliverables - Offline delivery planner and cases Rollout and recovery: Send an explicit full snapshot if coalescing cannot prove eligibility. Project prerequisites: Define synthetic configuration schema and supported device capabilities. Implement local control-plane and gateway adapters with delayed messages. Engineer value: Practice desired/reported state, compatibility and rollback. Company value: Inspect whether remote configuration preserves working settings through offline and partial outcomes. 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. #### CCONFIG-109 — Expose edge-configuration rollback as a new desired revision **Story · Medium priority · Intermediate** noCV practice brief v5 · CCONFIG-109 · Versioned edge configuration with an offline gateway Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Recover gateway state. Depends on: CCONFIG-106, CCONFIG-108. Difficulty: Intermediate. Estimated focused work: 120 minutes; setup and prerequisite tickets are additional. Estimated field mix: Embedded and edge 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. Operators lower the revision number to restore older values and gateways reject it as stale. Create a new revision carrying the prior values. Acceptance criteria - Rollback increments revision - Prior values are copied explicitly - Current capability validation still applies Implementation constraints - Preserve original revision history. Verification - Roll back supported values - Attempt rollback containing now-unsupported field Deliverables - Rollback command and history cases Rollout and recovery: Retain current settings if rollback validation fails. Project prerequisites: Define synthetic configuration schema and supported device capabilities. Implement local control-plane and gateway adapters with delayed messages. Engineer value: Practice desired/reported state, compatibility and rollback. Company value: Inspect whether remote configuration preserves working settings through offline and partial outcomes. 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. #### CCONFIG-110 — Summarize edge-configuration drift without logging setting payloads **Chore · Low priority · Intermediate** noCV practice brief v5 · CCONFIG-110 · Versioned edge configuration with an offline gateway Fictional engineering practice briefs. Starter repositories, fixtures, automated grading, and verified ownership are not included. Phase: Recover gateway state. Depends on: CCONFIG-107, CCONFIG-109. Difficulty: Intermediate. Estimated focused work: 105 minutes; setup and prerequisite tickets are additional. Estimated field mix: Privacy engineering 40% · Embedded and edge 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. Drift diagnosis logs full configuration documents unnecessarily. Report revision gaps and typed rejection reasons. Acceptance criteria - Summary shows desired and reported revisions - Payload values are omitted - Offline uncertainty is explicit Implementation constraints - Use aggregate synthetic fleet observations only. Verification - Inspect converged gateway - Inspect offline and incompatible gateways Deliverables - Drift report and data-exclusion cases Rollout and recovery: Disable detailed diagnostics if configuration values leak. Project prerequisites: Define synthetic configuration schema and supported device capabilities. Implement local control-plane and gateway adapters with delayed messages. Engineer value: Practice desired/reported state, compatibility and rollback. Company value: Inspect whether remote configuration preserves working settings through offline and partial outcomes. 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.