[
  {
    "id": "claude-20260114-bfb83b21",
    "date": "2026-01-14",
    "source": "claude",
    "chat_title": "Hiring — Sam vs Alex for the senior backend role",
    "question": "Weighing two candidates for the senior backend opening",
    "chosen": "Alex",
    "rejected": [],
    "trade_offs": [],
    "confidence": "high",
    "snippet": "assistant: For a team of 8 where you already have distributed-systems depth in other hires, the marginal utility of Alex's shipping habit and communication is probably higher. Systems skill compounds; communication unblocks.\nuser: Yeah that's the argument I'd been circling. Decided on Alex. Writing up the offer now.",
    "tags": []
  },
  {
    "id": "claude-20260203-d7cf9e98",
    "date": "2026-02-03",
    "source": "claude",
    "chat_title": "Kubernetes or Fly.io for the next deploy",
    "question": "kubernetes vs fly.io",
    "chosen": "kubernetes",
    "rejected": [
      "fly.io"
    ],
    "trade_offs": [],
    "confidence": "medium",
    "snippet": "assistant: If the rest of infra is on k8s and CI is wired, the marginal cost of adding one more service is tiny — the cognitive and ops burden is amortised. Fly's nice-to-haves (scale-to-zero, simple UX) don't offset two new things to learn.\nuser: Agreed. Sticking with kubernetes. The scale-to-zero thing was cool but it's a tiebreaker not a deciding factor.",
    "tags": [
      "infra"
    ]
  }
]