# Phase 0.9E output architecture options

Date: 2026-07-18

No output architecture is selected. The actual bootstrap implementation is
missing, so `output_channel_for_future_rescue=UNKNOWN`.

| Option | Exists now | Changes required | Device file | Cleanup/crash model | Risk / feasibility |
|---|---|---|---|---|---|
| A. same 9020 connection, duplex | unknown | exact server and host protocol may need change; payload result propagation required | not inherently | unknown socket ownership, EOF and abort | potentially low persistent risk, feasibility unknown |
| B. temporary PS5-to-approved-host outbound connection | absent | host receiver and target payload required | no | bounded connect/send/close and deadline required | temporary socket is not automatically brick-relevant; network policy and cleanup unproven |
| C. temporary one-connection listener | absent | target listener and host client required | no | bind/listen/accept deadline and guaranteed close required | listener lifetime/session collision risk; not automatically a brick risk |
| D. caller-owned host buffer | absent | exact loader ABI, buffer ownership, copy-out and post-exit delivery required | no | caller finalization and crash-safe ownership required | Phase-0.9C already shows current elfldr has no such output path |
| E. no usable output | consistent with current evidence | none | no | no recovery result possible | only defensible current operational assumption |

Options A through D are designs, not claims. A generic TCP connection can be
duplex at transport level, but that does not prove that the 9020 listener keeps
the socket, passes it to a payload, accepts response bytes, or returns them to
the host.

No option may:

- create or replace a live device file;
- enable autoload;
- retry automatically;
- combine recovery of both components;
- persist a listener or configuration across sessions.

The missing exact listener source prevents selection and prevents a
source-derived host-only emulator.