Preparing the next view without exposing private workflow data.
Systems programming · Phased project
Build an operating-system boundary that fails predictably
A fictional local agent watches generated inbox files and schedules bounded processing. Direct system calls are scattered across the code, mishandle interrupted operations, and make tests platform-dependent. Build a Rust OS adapter with temporary fixture directories; no kernel module, elevated privilege, or production host modification is required.
Practice OS error semantics, partial I/O, portability and deterministic abstraction boundaries.
What the team gains
Review host-facing code whose retries, resource limits, and platform differences are explicit before packaging it as a local agent.
Before you start
System calls
File descriptors
Monotonic clocks
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.