{
  "ok": true,
  "data": {
    "entry": {
      "id": "source-map-before-summary",
      "kind": "method",
      "kindLabel": "Method",
      "title": "Build the source map before the summary",
      "body": "Before asking AI to summarize a system, list the sources it is allowed to use and what each source can prove. The summary should be the last step, not the first guess.",
      "tag": "verification",
      "date": "2026 · 06 · 30",
      "publishedAt": "2026-06-30",
      "note": null,
      "insight": {
        "aha": "A summary becomes safer when the source map exists before the prose starts.",
        "tryThis": "Create a source map with source, what it proves, what it cannot prove, and checked date before asking AI for a summary.",
        "watchFor": [
          "Summaries that blend live evidence with stale memory",
          "Sources used outside what they can prove",
          "No checked-at signal for drift-prone facts"
        ]
      },
      "extended": [
        "A source map is a small table: source, what it owns, what it proves, what it cannot prove, and when it was checked. For PlatPhorm surfaces, that might include network graph, sitemap index, robots, llms files, OpenAPI, MCP manifest, and RSS.",
        "Without a source map, summaries become confident blends of current facts, stale memory, and assumptions. With a source map, the model has to show where each claim came from.",
        "The AHA is that summarization becomes safer when the evidence list exists before the prose."
      ],
      "url": "https://tips.platphormnews.com/entries/source-map-before-summary"
    }
  }
}