# Starting point: entangled-port track from issue #24

The learner is a frontend engineer picking up MessageChannel after the related tracks already exist as *labels* in [issue #24](https://github.com/ayv4zyan/teach/issues/24): window `postMessage` + origin (#15), structured clone / transfer (#13), BroadcastChannel (#12), and dedicated/shared workers. This workspace was not seeded from those folders. Goal is durable judgment for minting a pair, transferring one end, `start`/`close`, and choosing a private pipe over addressing a window or a named bus — plus light hands-on, not a multiplayer architecture. First ZPD lesson: what two entangled ports *are*, versus a window handle, a BroadcastChannel, and a same-context EventTarget.