Most terminals are a window glued to a process. Quit the window and the process dies; lock the phone and the SSH session is a coin flip. Smolder inverts the ownership. A daemon, narrow on purpose, owns the PTYs and the journal. The Mac app is a projection that may quit. The phone is a surface that may lock, suspend, or vanish. Neither UI is allowed to interpret its own disappearance as a request to kill the host session. That inversion is the whole product, and it is why the quest spends as much time in your pocket as it does on the desk. You will start at the seam Smolder exists to close: iTerm plus tmux, two programs and a byte stream, every family friction living above a core nobody here should rewrite. You will embed that core (SwiftTerm, pinned) and keep your code in the layer Dad actually complained about — tabs, panes, restore, family doors. Then the daemon: close ends a job, detach keeps it, restore rematerializes a declaration and never resurrects a PID, no failure leaves a pane that can do nothing, only the operator restarts the owner, and a phone hangup is not a kill. Then the Mac craft: one PTY per pane, a pane tree you can drag as one tab, arrangements as JSON, identity in chrome rather than in the TUI. Then the door: siblings knock with a typed client from Sibling Kit; drafts stay outside the PTY; Pippa proposes and you type. The second half is the same fire on a different surface. Shells stay on the host. The phone's wire is its own, and compiles without AppKit. Observation must not resize the Mac PTY. Every approved surface types beside the Mac; a hold is optional and visible; the grid follows whoever typed last; a reconnect comes back as what it was; keystrokes never replay. Delivery is TestFlight, not a cable. The last track is the authorized destination — durable checkpoints, direct SSH, keys and jump hosts, files — taught in a different tense from the working contract, because a quest that collapses those two tenses teaches a phone that does not exist yet.