docs(readme): add build-order and binary-anatomy diagrams

README.md

@@ -32,9 +32,15 @@ Monorepo containing:
 - **WASM** - ONNX Runtime and Yoga Layout
 - **ML Models** - Quantized AI models (CodeT5, MiniLM)
 
+The packages stack into four tiers — native libraries at the bottom, the custom Node.js binary at the top:
+
+![Build order: native libraries flow up into the final Node.js binary](docs/images/build-tiers.svg)
+
 ## Core Concepts
 
-If you're new to binary manipulation or Node.js customization, here are the key concepts you'll encounter:
+If you're new to binary manipulation or Node.js customization, here are the key concepts you'll encounter. The diagram below shows how `binject` merges your app with the Node.js runtime to produce a Single Executable Application — solid borders are real files on disk, dashed borders are virtual files embedded inside the binary:
+
+![How a Socket binary is built: binject merges the Node.js runtime with your app's source files into a SEA containing a runtime, an SEA blob, and a VFS section](docs/images/binary-anatomy.svg)
 
 ### Single Executable Application (SEA)
 
@@ -70,6 +76,12 @@ Reducing binary size for distribution. Compressed binaries self-extract at runti
 
 **Example:** 60MB Node.js binary → 23MB compressed binary (saves bandwidth, faster downloads).
 
+### Putting it together: what happens when a user runs the binary
+
+The stub decompresses the zstd payload, the Node.js runtime boots and reads the SEA blob to find the entry point, and the running app reads VFS files via `fs.readFile()` like they were on disk:
+
+![Runtime lifecycle: stub decompresses, runtime executes the SEA blob and reads VFS, your app produces output](docs/images/lifecycle.svg)
+
 ## Quick Start
 
 `binject` / `binpress` depend on a prebuilt LIEF artifact, and `stubs-builder` depends on prebuilt curl+mbedTLS; both are fetched automatically from this repo's GitHub releases on first build. Pass `pnpm --filter <builder> run build -- --force` if you need to compile those libraries from source (e.g. an unsupported platform or a LIEF/curl bump that hasn't been published yet).