Task library CFRAME Embedded and edge · Phased project An emulated device-link framing library Fictional environmental-display devices send synthetic noncritical readings to a local gateway. Implement a byte-stream emulator; no physical device, radio, credentials or safety-critical control is involved.
Practice brief · Version 5
Project scope 10 tickets / 3 phases
Total focused work estimate 22h 45m + setup
Suggested stack TypeScript · Byte-stream emulator · 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 CFRAME-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice incremental parsing, fixed resource limits and protocol recovery.
What the team gains Inspect whether a device adapter survives malformed input without corrupting accepted readings.
Before you start Specify a small frame format with length sequence payload and checksum. Generate local byte streams with fragmentation corruption and reconnects. Delivery agreement All execution uses software fixtures; hardware timing and production readiness are unqualified.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Validate bytes before interpreting payloads.
PHASE 2 Recover fragmented and damaged streams.
PHASE 3 Limit work and explain rejected data.
Handle partial transport Recover fragmented and damaged streams.
CFRAME-104 Depends on CFRAME-102, CFRAME-103 Estimated field mix
Embedded and edge 50% Networking 50% CFRAME-105 Depends on CFRAME-104 Estimated field mix
Embedded and edge 50% Networking 50% CFRAME-106 Depends on CFRAME-104, CFRAME-105 Estimated field mix
Embedded and edge 60% Networking 40% CFRAME-107 Depends on CFRAME-103, CFRAME-106 Estimated field mix
Embedded and edge 50% Networking 30% Distributed systems 20% Bound receiver behavior Limit work and explain rejected data.
CFRAME-108 Depends on CFRAME-104, CFRAME-107 Estimated field mix
Embedded and edge 40% Performance engineering 40% Networking 20% CFRAME-109 Depends on CFRAME-106, CFRAME-107 Estimated field mix
Embedded and edge 60% Networking 40% CFRAME-110 Depends on CFRAME-108, CFRAME-109 Estimated field mix
Embedded and edge 40% Site reliability 30% Privacy engineering 30% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.