Expose platform capability instead of silently changing semantics
The Windows fixture cannot provide the same directory-flush guarantee as the Unix adapter, but both report durable replacement.
- Focused work estimate
- 4h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Portability · Capability modeling · Contract testing
Estimated field mix
- Systems programming70%
- Platform engineering30%
Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.
Review it, then add it to your workspace.
The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.
Project context
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.
Setup prerequisites
- System calls
- File descriptors
- Monotonic clocks
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
Acceptance criteria
- Adapter reports exact supported capabilities
- Callers can require a capability and fail before mutation
- Fallback semantics have distinct result codes and documentation
Implementation constraints
- Do not erase platform differences behind a boolean success value.
Verification to include
- Run the shared contract against two declared capability fixtures.
- Require directory durability from an unsupported fixture and confirm no replacement starts.
Deliverables
- OS capability model and cross-adapter contract suite
Rollout and recovery
Gate each deployment profile on its required capability set.
Value of the work
For the engineer: Practice OS error semantics, partial I/O, portability and deterministic abstraction boundaries.
For the team: Review host-facing code whose retries, resource limits, and platform differences are explicit before packaging it as a local agent.
Evidence boundaries
Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.
Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.