Reconcile pending operations after supervisor restart
The supervisor restarts with requests marked running but no in-memory correlation table and no proof whether workers completed them.
- Focused work estimate
- 6h + prerequisites
- Priority in the scenario
- High
- Engineering practice
- Crash recovery · Journaling · Idempotency
Estimated field mix
- Systems programming60%
- Storage systems40%
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-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-102 · Close inherited descriptors before executing the worker
- 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
Acceptance criteria
- Persist stable operation identity and last acknowledged state before dispatch
- Recovery queries a deterministic worker ledger when supported
- Unresolved operations remain visible and are never silently marked failed
Implementation constraints
- The local ledger contains synthetic identities and bounded metadata, not document bodies.
Verification to include
- Restart after acknowledgement and restore the completed result.
- Restart during an unqueryable effect and retain UNKNOWN for review.
Deliverables
- Pending-operation journal and restart drill
Rollout and recovery
Require reconciliation support before enabling autonomous retry.
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.