Task library CCONFIG Embedded and edge · Phased project 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.
Practice brief · Version 5
Project scope 10 tickets / 3 phases
Total focused work estimate 23h 15m + setup
Suggested stack TypeScript · Gateway emulator · SQLite adapter · Vitest 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 CCONFIG-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice desired/reported state, compatibility and rollback.
What the team gains Inspect whether remote configuration preserves working settings through offline and partial outcomes.
Before you start Define synthetic configuration schema and supported device capabilities. Implement local control-plane and gateway adapters with delayed messages. Delivery agreement Deliver local simulation changes; hardware validation and external fleet deployment are excluded.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Validate and scope desired settings.
PHASE 2 Handle revisions and partial failures.
PHASE 3 Explain offline drift and bound retries.
Specify configuration contracts Validate and scope desired settings.
CCONFIG-101 Entry ticket; project setup still required Estimated field mix
Embedded and edge 80% API design 20% CCONFIG-102 Depends on CCONFIG-101 Estimated field mix
Embedded and edge 50% Distributed systems 30% Frontend 20% CCONFIG-103 Depends on CCONFIG-101, CCONFIG-102 Estimated field mix
Security 70% Embedded and edge 30% Apply settings deliberately Handle revisions and partial failures.
CCONFIG-104 Depends on CCONFIG-102, CCONFIG-103 Estimated field mix
Distributed systems 60% Embedded and edge 40% CCONFIG-105 Depends on CCONFIG-101, CCONFIG-104 Estimated field mix
Embedded and edge 60% Storage systems 40% CCONFIG-106 Depends on CCONFIG-104, CCONFIG-105 Estimated field mix
Embedded and edge 70% API design 30% CCONFIG-107 Depends on CCONFIG-105, CCONFIG-106 Estimated field mix
Embedded and edge 40% Storage systems 30% Distributed systems 30% Recover gateway state Explain offline drift and bound retries.
CCONFIG-108 Depends on CCONFIG-104, CCONFIG-107 Estimated field mix
Distributed systems 60% Embedded and edge 40% CCONFIG-109 Depends on CCONFIG-106, CCONFIG-108 Estimated field mix
Embedded and edge 60% Distributed systems 40% CCONFIG-110 Depends on CCONFIG-107, CCONFIG-109 Estimated field mix
Privacy engineering 40% Embedded and edge 30% Site reliability 30% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.