A short piece of fiction, written by API Evangelist. The reader is imagined; the post, and every number and quotation from it, is real: "A Listing Is Not A Certification," Kin Lane, October 20, 2026, https://apievangelist.com/2026/10/20/a-listing-is-not-a-certification/
Dolores works as a platform engineer at a regional logistics firm, and she opened the post on a Tuesday while a vendor shortlist sat unfinished in the next tab. Her team had to choose a Kubernetes platform for a regulated workload. Four of the five candidates called themselves standards-aligned in their sales decks. She had been treating that phrase as if it meant something.
The post's first claim was easy to accept. A listing is cheap and a certification is not. She had seen the CNCF landscape many times and had never asked what a logo on it proved. The post says plainly that it proves participation. She read that line twice, a little stung, because her shortlist spreadsheet had a column called Standards, and she had filled it from landscape pages.
Then came the sentence she copied into her notes: "A certification says someone outside the company checked." She looked at her column again. Not one cell recorded who had checked what.
She did not agree with all of it. The part about ceilings bothered her. Each register's cap comes from the widest current vendor in that register, and she thought that made a score depend on one company's catalogue. The post says BACnet caps at eighteen because Siemens holds eighteen listed device profiles. If Siemens dropped a profile, every other vendor's depth would shift, and she doubted that was fair. She also thought 17.2 for a listing alone was blunt. Some members of those landscapes ship serious software. The post even concedes that 52 cloud native providers reached standard on a single listing, naming Helm, Linkerd and K3s among them, and says the authors chose to keep them there. She read that as honest, and still felt it was a little cold toward projects she respected.
What she kept returning to was the bug. The depth code kept the last record it saw, skipped it because it was report-only, and so certified vendors lost their certification. The post says 1WorldSync, Salsify and Siemens read 17.2, the same as a company that only joined a member list. She recognised the kind of mistake. She had once shipped a dashboard where a join dropped half the rows, and nobody noticed for a month. The post says it well: "Nobody notices a score that is wrong in a plausible direction." She felt uncomfortable, because her own spreadsheet was a scoring system too, and she had no idea which direction it was wrong in.
She did not rebuild anything. She did not even decide the Kin Score was right. She opened the shortlist and renamed the Standards column to Claimed. Beside it she added a second column and headed it Checked by. For the Kubernetes candidates she went to the Certified Kubernetes register, which the post says publishes 1,579 conformance submissions from 185 vendors, and searched each product by name and version. Two of her four found their entry in under a minute. For the third she found a submission for an older version only. She typed that into the cell as it was.
The fourth she left blank. She stopped there and sent her manager a short message asking whether the blank was a reason to ask the vendor a question or a reason to cut them. Then she closed the post tab and went back to work.