{
  "ok": true,
  "data": {
    "entry": {
      "id": "model-routing",
      "kind": "method",
      "kindLabel": "Method",
      "title": "Route tasks by failure mode, not brand name",
      "body": "The best model for a job is the one whose failure mode you can tolerate. Route extraction, synthesis, coding, refusal review, and creative exploration by observed behavior, not by leaderboard aura.",
      "tag": "reliability",
      "date": "2026 · 04 · 26",
      "publishedAt": "2026-04-26",
      "note": null,
      "insight": {
        "aha": "Routing by failure mode is more useful than routing by reputation because every model breaks differently.",
        "tryThis": "Build a route table from observed task fixtures: extraction, synthesis, coding, refusal review, and long-context use.",
        "watchFor": [
          "Leaderboards used as a substitute for local fixtures",
          "Model routes that cannot be changed without code edits",
          "Ignoring behavior drift after model updates"
        ]
      },
      "extended": [
        "Model routing is usually framed as cost or quality. The more useful frame is failure. Which model omits caveats, over-refuses, invents sources, follows schemas, or handles long contexts under pressure?",
        "Build small route tests around the jobs you actually run. A model that wins general reasoning may still be the wrong choice for structured extraction if it casually fills unknown fields.",
        "Keep routing reversible. When model behavior shifts, the route table should be an operational setting backed by evidence, not a belief system."
      ],
      "url": "https://tips.platphormnews.com/entries/model-routing"
    }
  }
}