A short piece of fiction, written by API Evangelist. The reader is imagined; the post, and every number and quotation from it, is real: "Where A Score Fits In Your CI Pipeline And Your Developer Portal," Kin Lane, November 6, 2026, https://apievangelist.com/2026/11/06/where-a-score-fits-in-your-ci-pipeline-and-your-developer-portal/
Marisol had the ticket half written before she finished the post. She was a platform engineer, and the ticket was to add the Kin Score to the pipeline so it would show up on every pull request, right beside the coverage badge. Her manager liked numbers that moved, and she liked giving him one.
The post's first answer was against her. Kin Lane wrote, "I lean towards no." She read the paragraph twice, a little annoyed, because it was the exact thing she had been about to build.
The table made it harder to argue with. Pipeline linting looks at one contract and asks whether a change breaks the rules. The score looks at the whole operation around the APIs and asks whether someone can find, understand, pay for and use them. She had to admit that her pull requests never touched most of that. Nobody edits a pricing page, a status page or a changelog in a commit to the orders service. A per-commit score would sit still for weeks, then jump for reasons nobody on the team had caused, and she would be the one explaining it.
The part about the ruler stayed with her longest. Each reading carries the rubric version it was scored with, and the post's example was Atlassian on v0.25.0 and HubSpot on v0.24.0. Her gate would have failed builds over exactly that, because "A number can change because the ruler changed, and that is a poor thing to fail a build over." She winced, because she knew she would have shipped it anyway and apologized later.
She did not agree with all of it. Quarterly felt slow to her. Her team had a habit of agreeing to a goal in January and rediscovering it in March, and a number that only appears every three months is easy to forget. She also felt a small, stubborn disappointment that the Backstage idea was still untested. The author said plainly that he had not run it there yet and that his early prototypes had not gone forward. She would have liked a screenshot to show her manager. Instead she got a request: if you try this, tell me how it goes.
Still, one line matched what she had been looking for. The post said to refresh the score on a slow cadence, "so people do not treat it as an alert." That was the real reason she had been uneasy. Her team already had red, yellow and green for whether things were up, and she did not want a second light that people learned to ignore.
So she deleted the ticket and wrote a smaller one. She would call GET /rules, look at the Spectral rules behind the checks her team cared about, and pick a single one to enforce in the pipeline. She would also put a date in the calendar for the first quarterly reading.
She did not write anything about Backstage. That could wait until someone had tried it.