Task library CPRES
Project scope 10 tickets / 3 phases
Total focused work estimate 23h + setup
Suggested stack TypeScript · WebSocket · Redis 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 CPRES-101 Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
What the engineer takes away Practice ephemeral state, ordering and reconnect semantics.
What the team gains Inspect whether online indicators avoid stale or unauthorized claims.
Before you start Create synthetic memberships and session identifiers. Implement controllable sockets and an in-memory TTL adapter. Delivery agreement Presence means an active connection lease only; it does not infer attention or productivity.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.
Delivery phases PHASE 1 Specify scopes and expiry.
PHASE 2 Handle identity and reconnect races.
PHASE 3 Limit work and diagnose stale indicators.
Define presence meaning Specify scopes and expiry.
CPRES-101 Entry ticket; project setup still required Estimated field mix
Real-time systems 60% Distributed systems 40% CPRES-102 Entry ticket; project setup still required Estimated field mix
Security 50% Real-time systems 50% CPRES-103 Depends on CPRES-101, CPRES-102 Estimated field mix
Security 70% Real-time systems 30% Distribute state safely Handle identity and reconnect races.
CPRES-104 Depends on CPRES-103 Estimated field mix
Real-time systems 70% Data engineering 30% CPRES-105 Depends on CPRES-103, CPRES-104 Estimated field mix
Distributed systems 60% Real-time systems 40% CPRES-106 Depends on CPRES-104, CPRES-105 Estimated field mix
Real-time systems 50% Distributed systems 50% CPRES-107 Depends on CPRES-101, CPRES-105, CPRES-106 Estimated field mix
Distributed systems 50% Real-time systems 30% Site reliability 20% Bound operating behavior Limit work and diagnose stale indicators.
CPRES-108 Depends on CPRES-106 Estimated field mix
Performance engineering 50% Real-time systems 30% Site reliability 20% CPRES-109 Depends on CPRES-107, CPRES-108 Estimated field mix
Frontend 60% Real-time systems 40% CPRES-110 Depends on CPRES-109 Estimated field mix
Privacy engineering 50% Site reliability 30% Real-time systems 20% Use this project CSV keeps grouping and dependency keys as descriptive fields. Import mapping depends on your tracker configuration.