Document the IPC boundary for a future isolated provider
The local child-process harness is about to be mistaken for a production candidate-code sandbox.
- Focused work estimate
- 2h 30m + prerequisites
- Priority in the scenario
- Medium
- Engineering practice
- Provider interfaces · Security boundaries · Documentation
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 document converter launches local sandbox substitutes as child processes. Its prototype parses newline-delimited output, leaks descriptors, and retries requests after ambiguous worker exits. Create a Rust supervisor and deterministic worker fixtures; no document content or production sandbox is supplied.
Setup prerequisites
- File descriptors
- Framing
- Process signals
Preceding work
Complete these dependencies, or supply their agreed outputs before taking this ticket.
- SIPC-102 · Close inherited descriptors before executing the worker
- SIPC-101 · Frame worker messages without treating newlines as boundaries
- SIPC-103 · Correlate out-of-order worker replies to the right caller
- SIPC-106 · Classify worker exit before deciding whether to retry
- SIPC-107 · Terminate a process tree without signaling unrelated work
- SIPC-104 · Separate protocol output from worker diagnostics
- SIPC-105 · Apply backpressure when a worker stops reading
- SIPC-108 · Restart crashed workers without retry storms
- SIPC-109 · Reconcile pending operations after supervisor restart
Acceptance criteria
- Document framing, resource limits, process identity, shutdown, and unresolved outcomes
- State which isolation guarantees the local supervisor does not provide
- Define the provider contract a hardened external executor must satisfy
Implementation constraints
- Do not claim namespace, secret, network, or host isolation from ordinary child processes.
Verification to include
- Reproduce the local crash and restart drill from the guide.
- Attempt to select the local adapter under a production configuration and require fail-closed behavior.
Deliverables
- IPC contract and explicit production boundary note
Rollout and recovery
Keep the local supervisor restricted to synthetic development fixtures.
Value of the work
For the engineer: Practice IPC contracts, resource inheritance, process supervision and ambiguous completion.
For the team: Review a local worker boundary that contains crashes and preserves request outcomes before connecting an isolated execution provider.
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.