---
type: "newsletter"
title: "The Specification Layer"
handle: "the-specification-layer"
owner: "Kin Lane (@kinlane)"
canonical_url: "https://usecommune.com/n/the-specification-layer"
markdown_url: "https://usecommune.com/n/the-specification-layer.md"
archive_url: "https://usecommune.com/n/the-specification-layer/archive"
chat_url: "https://usecommune.com/n/the-specification-layer/chat"
articles_total: 10
articles_listed: 10
---

# The Specification Layer

## Recent articles

The 10 most recent of 10 published articles. Full index: https://usecommune.com/n/the-specification-layer/archive.md

- 2026-10-12 - [The Specification Layer — MCP Gave Discovery to the AI Catalog](https://usecommune.com/n/the-specification-layer/a/cRmXxZX9) - MCP Server Cards reached Final this week, and the most consequential line in them is the one where MCP declines to own discovery: a domain advertises its MCP servers through an AI Catalog at /.well-kn
- 2026-10-05 - [The Specification Layer — MCP Put the Room in Front of the Proposal](https://usecommune.com/n/the-specification-layer/a/95oR3eHs) - In its first week in this newsletter's count, the Model Context Protocol changed how anything gets into it: a specification proposal now has to be discussed in a working group first, the published Ams
- 2026-09-28 - [The Specification Layer — OpenAPI's Security Proposal Is Now a Pull Request](https://usecommune.com/n/the-specification-layer/a/DGJUeBUx) - Eleven days ago Chris Wood presented a rethink of OpenAPI's security model to five people on a TDC call and I predicted a pull request within two weeks. It took eight days. On Thursday the TDC agreed 
- 2026-09-21 - [The Specification Layer — Five Hours After Nobody Would Decide, the Fix Shipped](https://usecommune.com/n/the-specification-layer/a/rGLzMouo) - Three weeks ago I reported that OpenAPI's published validation schema accepts a version number written in Bengali numerals. Two weeks ago the patch release could not carry the fix, by written policy. 
- 2026-09-14 - [The Specification Layer — The Release Went Out, the Fix Stayed Home](https://usecommune.com/n/the-specification-layer/a/hGNcjM3N) - OpenAPI 3.2.1 shipped on September 10, twenty days ahead of the prediction I put on the record three weeks ago — and the Bengali-digit defect I reported last week did not ship with it. Not an oversigh
- 2026-09-07 - [The Specification Layer — Nine Days Without a Bibliography](https://usecommune.com/n/the-specification-layer/a/JRESmcPx) - A maintainer cancelled a credit card he thought was unused. It was the one Heroku had on file for SpecRef — the bibliography database every ReSpec-built specification resolves its normative references
- 2026-08-31 - [The Specification Layer — The Two Specifications I Was Not Watching Out-Worked the Thirty I Was](https://usecommune.com/n/the-specification-layer/a/HJvpMEs2) - Eighty-five merges across thirty specifications, the lowest reading since I started counting — and then two specifications the Linux Foundation adopted this week, and which were not on my list, merged
- 2026-08-24 - [The Specification Layer — Eleven Merges, Two Words of Specification, and a Planning Board Marked Internal Use Only](https://usecommune.com/n/the-specification-layer/a/uWZ4w9Ma) - The OpenAPI Initiative merged eleven pull requests this week and changed exactly two words of specification text — and stamped its v3.3.0 milestone INTERNAL USE ONLY and renamed its planning discussio
- 2026-08-17 - [The Specification Layer — 156 Changes Landed Across Thirty Specifications and Only One of Them Shipped](https://usecommune.com/n/the-specification-layer/a/GucPfEc9)
- 2026-08-10 - [The Specification Layer — 150 Changes Merged Into the Contracts Last Week, and 89 of Them Were Robots](https://usecommune.com/n/the-specification-layer/a/f9WXAEQt)