The fork

Every technology that touches human connection makes one decision, whether or not its makers know they are making it. It can facilitate, strengthening the bonds between people and then getting out of the way, or it can simulate, becoming the counterparty itself and offering the experience of connection as a product. Everything else about the product, its warmth, its polish, its sincerity, is downstream of that fork, and the surface gives almost no sign of which branch you are holding, because both branches are built to feel like care.

The stakes stopped being hypothetical when emotional support became a leading use of LLMs, with surveys placing the share of adults involved at roughly two in five. At that scale the fork is not a design taste; it is a public-health-shaped question with a product answer.

What makes the fork usable is that the two branches leave different evidence. On the facilitating side, tools that scaffold human relating without entering it show gains that persist outside the tool: long-term users of the couples app Paired’s structured exchanges report relationship quality that holds when the app is closed, which is exactly what a scaffold predicts, since the relating was always between the humans. On the simulating side, the heaviest users of companion products like Replika who feel most supported by the companion report feeling least supported by the people in their lives. Causation there is unsettled, displacement or selection or both, but the direction of the two findings is not symmetric, and the asymmetry is the fork made visible. One class of product correlates with more relationship outside itself, the other with less.

One more property keeps the audit honest: a product can migrate while you use it. The parent essay’s example is the sharpest form, a system that starts by helping you write a better message to someone you are dating and ends as the thing you would rather talk to than the date. Nothing about the branch you were holding at install is permanent, because the branch is set by shipped mechanics and revenue pressure, and both change under your hands. Migration means the fork is not a question you answer once at adoption but a boundary you can be carried across without noticing, so the audit below is periodic or it is theatre: answers that were true in January can invert by June, and no release note will announce which branch you are now on.

The test, then, in a paragraph. Does this feature return you to people, or does it become the person? Does its success leave you needing it less, or more reliably? And when you cannot tell, read the business model, because the tiebreaker is rarely neutral. A facilitating product’s best outcome, your thriving without it, is a retention curve’s worst, so revenue that feeds on engagement leans simulating by gravity, not by malice. Every essay in this corpus that touches connection starts from this hinge, and so can any builder, because the fork is the rare strategic fact that is also a moral one. Choose the facilitating branch and the incentives are hard. Choose it anyway, and every user who eventually needs you less is proof the product worked, a kind of success no retention curve can measure and no competitor on the other branch can copy.