{
  "ok": true,
  "data": {
    "entry": {
      "id": "source-ledger-habit",
      "kind": "tool",
      "kindLabel": "Tool",
      "title": "Build a source ledger before the answer",
      "body": "A source ledger names each source, what it can prove, what it cannot prove, and when it was checked. It is the simplest way to stop a model from blending evidence, memory, and assumptions.",
      "tag": "verification",
      "date": "2026 · 06 · 30",
      "publishedAt": "2026-06-30",
      "note": null,
      "insight": {
        "aha": "A source ledger gives every source a job before the model starts blending evidence into prose.",
        "tryThis": "Create a four-column ledger: source, what it proves, what it cannot prove, checked-at date, then write the answer from the ledger.",
        "watchFor": [
          "Links collected without claim-level purpose",
          "Old sources used for facts likely to drift",
          "Background sources treated as direct proof"
        ]
      },
      "extended": [
        "A ledger is smaller than a report and more useful than a pile of links. It turns sources into jobs. One source may prove a date, another may prove a route contract, and another may only give background.",
        "For research trends, the ledger prevents overclaiming. A lab blog can support what the lab announced. A paper can support its tested claim. A local platform route can support current contract shape only after it is inspected.",
        "The AHA is that evidence becomes stronger when each source has a job description."
      ],
      "url": "https://tips.platphormnews.com/entries/source-ledger-habit"
    }
  }
}