{
  "ok": true,
  "data": {
    "entry": {
      "id": "integration-contract-cards",
      "kind": "tool",
      "kindLabel": "Tool",
      "title": "Use integration cards instead of vague platform links",
      "body": "A cross-site link should explain what the target service owns, what public data is safe to read, what requires PLATPHORM_API_KEY, and what the current page does not do.",
      "tag": "integration",
      "date": "2026 · 06 · 27",
      "publishedAt": "2026-06-27",
      "note": "A link without a contract is just navigation.",
      "insight": {
        "aha": "A cross-site link is safer when it says what the target owns and what this page will not do.",
        "tryThis": "Write each integration card with owner, public reads, protected actions, and handoff links before adding buttons.",
        "watchFor": [
          "Buttons implying a write happened when only navigation occurred",
          "Protected actions presented as public workflows",
          "Generic platform links without a product-specific handoff"
        ]
      },
      "extended": [
        "Dictionary owns public definitions and concept lookup. Notes owns learning capture, term detection, and note analysis previews. This notebook owns walkthroughs, entries, and framing flows.",
        "A good integration card states the handoff in plain language: open the definition, capture a note, preview term detection, or review a workflow template.",
        "It should also name the boundary. If this site is not posting to Dictionary or Notes, the UI should not imply that a write happened."
      ],
      "url": "https://tips.platphormnews.com/entries/integration-contract-cards"
    }
  }
}