Preparing the next view without exposing private workflow data.
Systems programming · Phased project
Make a native work queue survive real thread interleavings
A fictional image-indexing utility runs CPU-only synthetic jobs through a Rust worker pool. Its prototype loses wakeups, blocks shutdown, and treats cancellation as completion. Build a local library and deterministic concurrency harness; image content, GPU work, and production deployment are excluded.
Practice brief · Version 5
Project scope
10 tickets / 3 phases
Total focused work estimate
34h 30m + setup
Suggested stack
Rust · Threads · Loom or deterministic scheduler · Criterion
Recommended next step
Start with SCONCUR-101
Open the first ticket for its prerequisites, acceptance criteria, verification plan, and an editable task draft.
Practice happens-before reasoning, ownership transfer, cancellation and liveness testing.
What the team gains
Review a worker primitive whose overload and shutdown behavior are predictable before it supports build or media workloads.
Before you start
Mutexes and condition variables
Atomics
Thread lifecycle
Delivery agreement
Ten linked tickets across three phases. Use synthetic inputs and a local harness; provide source, focused tests, measurements where requested, and a recovery note.
AI tools are welcome during implementation. Record assumptions, review the result, and verify its behavior.