# Phase 1.0AP: current-upstream worker feasibility audit

Status: `WORKER_CREATION_SOURCE_CANDIDATE_PREEMPTION_AND_RESULT_CHANNEL_BLOCKED`

Date: 2026-07-29

The current official SDK and shsrv heads were fetched as Git objects without
changing either pinned worktree. The SDK declares `rfork_thread`, and current
shsrv uses it both for forked shell builtins and its raw ELF process path. A
returned PID makes worker creation a strong public-source candidate.

That PID is not a generation-safe identity. There is no bounded worker-start
handshake or birth token. Official source uses `SIGKILL` and `waitpid`, but the
relevant waits are blocking and do not prove that a worker stuck in `mdbg` or
`PT_IO` can be terminated and reaped within a deadline on firmware 9.60. The
state of a separately mutated child after worker termination is also unknown.

Shell pipes are generic byte streams, not the fixed, identity-bound result
record required by Phase 1.0AO. They provide no exact progress/restoration
fields, bounded receive or deadline sealing. Current shsrv code must not be
copied: its broader persistence and lifecycle effects remain rejected by prior
phases.

The next allowed step is a capability-free fixed-result and PID-generation
contract. No target source, build, connection, transfer or execution is
authorized.