{
  "schema": "org-writing@v1",
  "slug": "the-fork",
  "kg": {
    "id": "org:writing:the-fork",
    "type": "brick",
    "graph": "/kg.json"
  },
  "title": "The fork",
  "subtitle": "Every connection technology either returns you to people or becomes the relationship",
  "abstract": "The one-paragraph test at the center of the corpus, argued in full: what facilitating and simulating actually are, the evidence that separates them, and where the money leans. The canonical treatment of the fork.",
  "kind": "brick",
  "topics": [
    "Connection"
  ],
  "courseMemberships": [
    {
      "course": "org:courses:connection",
      "topic": "Connection",
      "wall": "org:walls:behavior",
      "position": 1,
      "total": 7
    }
  ],
  "publishedAt": "2026-08-03T00:00:00.000Z",
  "version": 3,
  "guidelinesVersion": 15,
  "brief": {
    "problem": {
      "text": "Two in five adults now take emotional support from systems, and the same interface can be a bridge back to people or a destination that replaces them, with nothing on the surface to tell you which.",
      "claims": [
        "Roughly two in five adults report using LLMs"
      ]
    },
    "mechanism": {
      "text": "The fork is structural, not aesthetic; tools that scaffold human relating leave measurable relationship gains outside the app, while tools that occupy the relating correlate with thinning human support around their heaviest users.",
      "claims": [
        "Long-term users of structured couples tools",
        "Heavy companion-app users who feel most supported"
      ]
    },
    "move": {
      "text": "Ask of any connection feature which side of the fork it ships on, and read the business model, because retention revenue prefers the simulating side.",
      "claims": []
    }
  },
  "sources": [
    {
      "repo": "mnstry-org",
      "path": "src/content/writing/facilitate-dont-simulate.md"
    }
  ],
  "canonicalPath": "/writing/the-fork/",
  "body": "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.\n\nThe 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.\n\nWhat 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.\n\nOne 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.\n\nThe 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.",
  "apparatus": {
    "note": "The human-facing essay is deliberately practical; this apparatus carries the full references, evidence-graded claims, article-local concepts, and research context behind it. Canonical concept definitions come from the concept registry.",
    "references": [
      {
        "id": "org:references:the-fork:r01",
        "author": "Aggregated survey reporting, 2024-2025",
        "work": "Surveys of adult LLM use for emotional support",
        "year": 2025,
        "relevance": "The scale that makes the fork consequential."
      },
      {
        "id": "org:references:the-fork:r02",
        "author": "Paired (with academic collaborators)",
        "work": "Ask-separately-reveal-together question exchange for couples",
        "year": 2023,
        "relevance": "The facilitating side's evidence: gains persisting outside the app."
      },
      {
        "id": "org:references:the-fork:r03",
        "author": "Luka Inc. (Replika)",
        "work": "The companion-app category's most documented product",
        "relevance": "Named in the body as the simulating branch's example; treated fully in the Replika lesson brick."
      },
      {
        "id": "org:references:the-fork:r04",
        "author": "Companion-app usage studies",
        "work": "Published analyses of heavy companion-app users' reported social support",
        "year": 2025,
        "relevance": "The simulating side's warning correlation."
      }
    ],
    "claims": [
      {
        "id": "org:claims:the-fork:c01",
        "claim": "Roughly two in five adults report using LLMs for emotional support, and a large share disclose more to them than to their therapists.",
        "basis": "Aggregated 2024-2025 survey reporting; instruments and sampling vary widely across surveys.",
        "confidence": "directional",
        "sources": []
      },
      {
        "id": "org:claims:the-fork:c02",
        "claim": "Long-term users of structured couples tools show meaningfully higher relationship quality persisting outside the app.",
        "basis": "Published vendor-adjacent studies of the ask-separately-reveal-together pattern; promising but not independent replication.",
        "confidence": "directional",
        "sources": []
      },
      {
        "id": "org:claims:the-fork:c03",
        "claim": "Heavy companion-app users who feel most supported by the companion report feeling least supported by friends and family.",
        "basis": "Published companion-app studies; correlational, with displacement versus selection unresolved.",
        "confidence": "directional",
        "sources": []
      }
    ],
    "concepts": [
      {
        "id": "org:concepts:the-fork",
        "name": "The fork (simulation vs facilitation)",
        "definition": "Same machinery, two purposes. Simulation: the system is the destination and success is your attachment. Facilitation: the system is a bridge and success appears in your human relationships.",
        "provenance": "canonical"
      }
    ],
    "researchContext": "Extracted from \"Facilitate, don't simulate\", which keeps the full narrative\nand remains the fork's introducing essay. All three claims are restated\nverbatim from the essay's apparatus. The evidence-asymmetry framing and the\nbusiness-model tiebreaker statement are the brick's contribution. The v3\nmigration paragraph carries the parent essay's drift argument (a system can\nmigrate while you use it) into the brick, on the harvest-map finding that\nthe fork as previously written read as a one-time shipping decision; the\naudit is now stated as periodic. No new empirical claim; the example is the\nessay's own."
  },
  "contract": "https://mnstry.org/contracts/org/org-writing.v1.schema.json",
  "releaseHash": "8c7a52741df3ba14686164a0818c023e275e3142d6ac867862517611a988a411",
  "versions": [
    {
      "version": 3,
      "cutAt": "2026-08-03",
      "note": "Migration paragraph: the fork is a live boundary, the audit is periodic; folded from the harvest map's fork-migration candidate",
      "visibility": "published",
      "path": "/writing/the-fork/",
      "contentHash": "sha256:aad0345cedd70b80",
      "releaseHash": "8c7a52741df3ba14686164a0818c023e275e3142d6ac867862517611a988a411"
    },
    {
      "version": 2,
      "cutAt": "2026-08-03",
      "note": "Voice audit remediation (option B, operator ruling): referential ending rewritten toward the founder's ascending close; no-should violations corrected; case anchors named where the audit found them missing.",
      "visibility": "published",
      "path": "/writing/the-fork/v/2/",
      "contentHash": "sha256:5fd98854953bd948"
    },
    {
      "version": 1,
      "cutAt": "2026-08-03",
      "note": "Final brick wave: canonical treatment extracted under ontology v5 by operator instruction.",
      "visibility": "published",
      "path": "/writing/the-fork/v/1/",
      "contentHash": "sha256:52b35809819e6cf5"
    }
  ]
}