It would be very interesting to understand how sockets can move between processes.

We should build a simple process that, using standard POSIX APIs:
1. Listens on a TCP socker
2. Accepts a connection, producing a file descriptor
3. Hands off the file descriptor to another process

The secondary process would implement a simple echo server. IE, it should read bytes, and write them back to the client.

It's "dealers choice" how the listening process communicates with the echo process. Presumably, this could be some form of pipe. But, whether the listening process fork and {{exec}}s the echo server, or whether we can route stdout in Bash is a question we'll have to answer.