nx_nishios_net.nx

nx_nishios_net.nx -- BROWSER-ON-ALL-OS arc, rung N3: the Nishi browser FETCHES over a NishiOS NIC. N1 rendered a disk page on NishiOS; N2 navigated by click; N4 wrote the window with executed x86. The remaining NishiOS gap is the network. This rung builds the hardware-up NIC path: a MODELED network interface (TX/RX descriptor registers + a doorbell) lives in the x86 RAM; the kernel driver programs the TX descriptor and RINGS THE DOORBELL via EXECUTED x86 STORE instructions on the sovereign mini-emu; the emu intercepts the doorbell store and runs the device, which reads the request out of the TX buffer and delivers an HTTP 200 into the RX buffer. Crucially the response body is DERIVED FROM the request (it echoes the requested path), so a hardcoded constant response cannot pass -- the liar-kill. The browser then parses the HTTP headers and lays out the fetched body into the NishiOS desktop. KAT: T1 booted off the persisted image; T2 LONG mode + banner; T3 the executed x86 rang the doorbell (device fired exactly once); T4 the device delivered (RX_STATUS==1) AND the x86 read that status back (scratch==1); T5 the response is a real HTTP 200; T6 the body is CONTENT-DERIVED (contains the exact requested path, and a decoy path is absent -- not a constant); T7 the browser laid out the fetched body (ok, boxes); T8 the browser rendered it into the desktop (h1 bar pixels); T9 BMP exported at the exact expected size. NEG/liar-kill: T10 a driver that programs the descriptor but NEVER rings the doorbell gets NO delivery (RX_STATUS stays 0 -- delivery is caused by the executed doorbell store, not a constant); T11 a 0-sector-load sibling image never reaches long mode. HONEST SEAM (stated, not hidden): the boot chain + the doorbell store execute as real x86 on the sovereign emu; the device's peer is a HERMETIC loopback (it answers from the request) so the gate is deterministic -- bridging the NIC's TX to the live sovereign TLS/HTTP stack for the REAL internet is the named next rung (nx_nishios_net_wire). What this rung proves: the NIC descriptor/doorbell driver path is real + executed, and the browser renders whatever the device delivers. NEVER-BRICK (Rule 26): writes FILE artifacts only; models INT 13h *reads* + a loopback NIC; no /dev. expect_exit: 0 license_tier: ORIGINAL