We are evaluating a custom Node.js/V8 build packaged in an OCI image on Vercel. Before implementation, we need clarification of the supported process and IPC boundaries.

For Container Functions, is a supervisor with separate producer and resolver child processes supported such that the resolver can retain an already-held, sealed in-memory result after only the producer exits?

Please clarify:

• Which local IPC or mapping facilities are supported (for example shared memory, Unix sockets or pipes), and their relevant limits/access controls.
• Whether producer-child exit, supervisor exit, request timeout or memory enforcement can terminate the whole instance.
• If this arrangement is supported only with Daemons, which process is monitored and how the liveness policy affects sibling survival.

I know that whole-instance destruction loses volatile state. The question is about producer-only failure while the supervisor and resolver remain alive. I also know that Daemon liveness-triggered restarts use immediate SIGKILL and that Daemons do not accept inbound HTTP/TCP traffic.

The support AI supplied differing answers about local IPC, so we would appreciate confirmation from a Vercel engineer with the applicable documentation or platform constraints.