{
  "ok": true,
  "data": {
    "entry": {
      "id": "latency-budget",
      "kind": "tip",
      "kindLabel": "Tip",
      "title": "Spend latency where uncertainty is highest",
      "body": "Do not add slow verification everywhere. Spend extra model calls, retrieval, self-consistency, or human review only where the first pass shows low confidence, high impact, or weak evidence.",
      "tag": "reliability",
      "date": "2026 · 05 · 09",
      "publishedAt": "2026-05-09",
      "note": null,
      "insight": {
        "aha": "Careful does not have to mean slow everywhere. Verification can wake up only where risk wakes it up.",
        "tryThis": "Escalate to extra checks when confidence is low, evidence is weak, impact is high, or an action is protected.",
        "watchFor": [
          "Uniformly expensive checks on low-risk tasks",
          "Fast paths that ignore missing evidence",
          "Latency budgets without explicit escalation triggers"
        ]
      },
      "extended": [
        "Reliable AI systems are often cascades. Cheap checks run first; expensive checks wake up only when the situation deserves them. This keeps the product fast without pretending every answer has equal risk.",
        "A practical budget has triggers: low logprob margin, missing receipt, protected action, high-dollar decision, policy boundary, or user-visible publication.",
        "The aha is that latency can be evidence-driven. You do not need to choose between always fast and always careful."
      ],
      "url": "https://tips.platphormnews.com/entries/latency-budget"
    }
  }
}