{
  "schema": "org-writing@v1",
  "slug": "subordinate-model-position",
  "kg": {
    "id": "org:writing:subordinate-model-position",
    "type": "brick",
    "graph": "/kg.json"
  },
  "title": "The subordinate model position",
  "subtitle": "Frontier models as interchangeable engines under a consent runtime they do not control",
  "abstract": "Why the defensible position in an era of collapsing model prices is the consent runtime above the model, not the model itself. The canonical treatment of the subordinate model position.",
  "kind": "brick",
  "topics": [
    "Safety"
  ],
  "courseMemberships": [
    {
      "course": "org:courses:safety",
      "topic": "Safety",
      "wall": "org:walls:engineering",
      "position": 9,
      "total": 11
    }
  ],
  "publishedAt": "2026-08-03T00:00:00.000Z",
  "version": 1,
  "guidelinesVersion": 15,
  "brief": {
    "problem": {
      "text": "Frontier capability is compounding and its price is collapsing, which makes any product built as a thin surface over one lab's model a commodity waiting for its supplier's roadmap.",
      "claims": [
        "2023-2025 capability timelines collapsed"
      ]
    },
    "mechanism": {
      "text": "The labs are structurally unlikely to build consent friction, context minimization, quarantined outputs, real revocation, because friction taxes what their business rewards; whoever does build it holds the position they cannot occupy.",
      "claims": [
        "Frontier labs are structurally unlikely to build consent friction"
      ]
    },
    "move": {
      "text": "Keep the model subordinate: route every frontier engine through a consent runtime you own, so capability stays swappable and the trust stays with the layer that earned it.",
      "claims": []
    }
  },
  "sources": [
    {
      "repo": "mnstry-org",
      "path": "src/content/writing/structural-not-behavioral.md"
    }
  ],
  "canonicalPath": "/writing/subordinate-model-position/",
  "body": "Between 2023 and 2025, capability timelines that had been measured in decades collapsed to single digits, and the price of frontier intelligence fell by orders of magnitude. Both trends have one strategic implication for anyone building on top of the models: whatever advantage lives in the model itself is a depreciating asset you do not own. A product that is a thin surface over one lab's engine inherits that lab's roadmap, that lab's pricing, and that lab's outages as its own, and its differentiation shrinks with every release that makes the engines more alike.\n\nSo the question is where, above the commodity layer, a durable position exists. The answer this corpus argues for is the consent runtime: the layer that holds a person's context under structural guarantees, domain locks, typed consent, quarantined outputs, real revocation, and feeds frontier models only what a task requires, only for the task's duration. In that architecture the model is subordinate. It executes against minimized context it does not retain, through an interface it does not define, and it is interchangeable by construction, because nothing about the person's trust attaches to it. Swap the engine and the guarantees hold, which means the trust was never the engine's to lose.\n\nWhat makes the position defensible rather than merely nice is who cannot take it. The frontier labs are structurally unlikely to build consent friction, because every element of it, context minimization, outputs that cannot be retained, revocation that actually deletes, taxes exactly what their business rewards: more context, more retention, more coupling between the user and the model. This is counter-positioning in the strict sense. The incumbent sees the position, understands the position, and cannot occupy it without defecting from its own economics, the same bind that kept active managers from copying the index fund for decades.\n\nThe move follows for any builder handling human context. Keep the model subordinate. Own the runtime, encode the guarantees structurally so they survive your own growth pressure, and treat every frontier engine as a vendor of a collapsing-price input. The models will keep getting better, which under this architecture is purely good news, since the layer people trust was never the layer that changed.",
  "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:subordinate-model-position:r01",
        "author": "Capability-forecast retrospectives and frontier pricing reports",
        "work": "2023-2025 timeline collapse and per-token price declines",
        "year": 2025,
        "relevance": "The commoditization pressure that makes the model layer a depreciating position."
      },
      {
        "id": "org:references:subordinate-model-position:r02",
        "author": "Hamilton Helmer",
        "work": "7 Powers (counter-positioning)",
        "relevance": "The strategic frame: a position the incumbent sees and cannot occupy without self-injury."
      }
    ],
    "claims": [
      {
        "id": "org:claims:subordinate-model-position:c01",
        "claim": "2023-2025 capability timelines collapsed years ahead of forecasts and frontier intelligence prices fell by orders of magnitude.",
        "basis": "Published forecast retrospectives and per-token pricing histories across providers.",
        "confidence": "verified",
        "sources": []
      },
      {
        "id": "org:claims:subordinate-model-position:c02",
        "claim": "Frontier labs are structurally unlikely to build consent friction (context minimization, quarantined outputs, real revocation) because it taxes what their business rewards.",
        "basis": "A structural-incentive argument from the labs' business models; consistent with observed product choices, not a measured finding.",
        "confidence": "directional",
        "sources": []
      }
    ],
    "concepts": [
      {
        "id": "org:concepts:subordinate-model-position",
        "name": "Subordinate model position",
        "definition": "The frontier model as an interchangeable execution engine behind a consent runtime that owns every boundary; swapping models changes nothing about the guarantees because the guarantees were never in the model.",
        "provenance": "canonical"
      }
    ],
    "researchContext": "Extracted from \"Structural, not behavioral\", which keeps the three-move arc.\nThe labs claim is restated verbatim from the essay's apparatus; the timelines\nclaim is restated verbatim from the fork essay's apparatus (cross-parent\ncitation, graded identically). The depreciating-asset framing and the\npurely-good-news closing inversion are the brick's contribution."
  },
  "contract": "https://mnstry.org/contracts/org/org-writing.v1.schema.json",
  "releaseHash": "3f2f1f6908c8be9c618ece3700f259293b5aa852803c6c1eeab7c31bffbfbcda",
  "versions": [
    {
      "version": 1,
      "cutAt": "2026-08-03",
      "note": "Final brick wave: canonical treatment extracted under ontology v5 by operator instruction.",
      "visibility": "published",
      "path": "/writing/subordinate-model-position/",
      "contentHash": "sha256:6816cfdaa7792efd",
      "releaseHash": "3f2f1f6908c8be9c618ece3700f259293b5aa852803c6c1eeab7c31bffbfbcda"
    }
  ]
}