Week of November 1 – November 8, 2026
MCP Closes Its Pull Requests to Members
By Kin Lane · Sent November 9, 2026
This is the fourteenth issue of The Specification Layer.
This newsletter window: November 1 through November 8. Fifty-two specification repositories and twenty-five feeds, all read clean. 312 pull requests merged. 11 releases cut. 28 posts published.
The core series of forty-six merged 232, 72 by bots (31%), against 255 and 30% last week, and cut 9 releases. 15 of 46 did not move. Reported alongside, not inside: the six added specifications merged 80, 13 by bots, with x402 alone at 51. Of the two release-path dependencies, SpecRef merged one change and OAI build-infra none.
Predictions from last week, graded:
| Prediction | Result |
|---|---|
The AI Catalog changes or explains its #kind syntax in light of RFC 8141 before tagging 0.9 |
Right. The group agreed on ; on November 5, and #137 proposes the change. It isn’t merged, and a competing proposal arrived the next day (see below). |
| The AI Catalog tags 0.9 before the end of November | Open. No tag yet. |
| A2A 1.1 is not final by the end of November | Open. One docs merge this week. |
Arazzo adopts a step type for 1.2, and 1.2 misses mid-November |
Open, and on track. Arazzo merged nothing. |
| MCP publishes the transition calendar confirming March 30 by year end | Open. |
The features default is fixed before a 3.3 release candidate |
Open. On v3.3-dev the prose still says 1.0.0 and the schema 1.1.0. |
| ORD 1.18 by the end of the year | Open. ORD shipped a patch, v1.17.1. |

The Lead: MCP Closes Its Pull Requests to Members
On November 8, MCP merged a new contribution policy, #3514. Two rules change how anyone outside the project takes part:
- A specification proposal needs working-group approval first. It must be discussed in, and explicitly approved by, the relevant working group before a SEP pull request is opened.
- Only members of the
modelcontextprotocolGitHub organization may open pull requests. Membership is requested in the access repository. Everyone else contributes by opening an issue from the templates or by joining a working group.
The submission order is now working-group approval, org membership, push, pull request, then a Core Maintainer review booked through the voting site. The pull request itself lists what is still out of line: the website’s contributing page still describes direct pull requests for small changes and the old sponsor flow, and the README’s license section still says MIT while LICENSE describes the move to Apache-2.0 and CC-BY-4.0.
Why it matters. It’s the strictest contribution rule among the specifications I track. I read it as a response to volume, not a closing of the door: the working groups are open, and an issue is still a way in. But it moves where the work happens. If you want to change MCP, the room now comes before the repository, so the working-group notes are the place to watch, not the pull request list.
Agent Skills adopted governance the same week. On November 4 the Agent Skills repository added GOVERNANCE.md and MAINTAINERS.md as part of its donation to the Agentic AI Foundation. The project will be established as a Series of LF Projects, LLC, with Apache-2.0 for code and specifications and CC-BY-4.0 for documentation. Its structure of Lead Maintainers, Core Maintainers, Maintainers and Contributors is modeled, in its own words, on MCP’s. In the same window MCP pointed its Skills specification links at specification/beta/, because under the new extension lifecycle Skills over MCP is Beta, not Stable.

🎙 AI & Agents, and From the Room
The AI Catalog changed its identifier separator, and now has two proposals. Last week I flagged a commenter’s point that RFC 8141 ignores a URN’s fragment when deciding equivalence, so #mcp and #skill couldn’t tell two entries apart. On the November 5 call the group agreed on a semicolon, and #137 proposes urn:air:{publisher}{:namespace+}:{name}{;kind}. A day later #138 proposed a different shape: urn:air:{publisher}:{name}[:{kind}], with slash-separated namespaces inside the name, such as urn:air:acme.com:engineering/code-review:skill. Neither is merged. An identifier is the one thing a catalog cannot change after release, so I’d rather see this settled slowly than tagged quickly.
The catalog also proposed recording that its objects are open to members the specification does not define, as ADR-0028. The prose always said so, and an earlier decision record calling them closed never reached the text. It also removed a W3C copyright notice from the rendered spec. Nothing is tagged.
MCP’s schema restored optional _meta on input requests and responses, and closed a oneOf type-check bypass. The MCP Registry shipped v1.8.8. Nearly all of its 28 merges were deployment and capacity work, but #1806 now allows remote URLs to be shared across server names.
OASF split its server and Helm chart into a separate repository, leaving the schema, the proto definitions and the docs. A2A published a Client ID Metadata Document for its CLI, so authorization servers that support the draft can accept it without registration. ONNX extended Gemm to rank-one and higher inputs in opset 29. Its other 16 merges were reference implementation and tooling.
OpenTelemetry’s GenAI conventions merged 32, the most of any core specification this week. They include exception events for each client operation, realtime sessions, and requiring structured content attributes. The repository still has no release.
In the working groups. The Skills over MCP group published its November 3 notes. Skills over MCP is now Beta under the extension lifecycle, and its format is delegated to the Agent Skills specification, so future revisions there apply automatically. The open question is what a skill version should mean. The notes record that semantic versioning may not fit something driving a non-deterministic system, and that versioning belongs with the Agent Skills specification, not the extension. That makes the new Agent Skills governance the place it will be decided. A2A’s technical steering committee treated 1.1 as largely settled on November 3 and turned to a timeline and to how it runs votes. The AI Catalog’s November 5 call is where the semicolon was agreed.

📐 The Description Layer
OpenAPI fixed a gap between its schema and its text. #5583 and #5584 add a description field to the Media Type Object on the 3.3 and 3.2 lines. The schema has had it since 3.2.0; the specification text never mentioned it. Karen Etheridge authored all seven OpenAPI merges, the rest of them schema test fixes. v3.3.0 is at 19 of 40.
Overlay opened 1.3. #426 seeds the 1.3 branch, and a new Release 1.3 milestone holds three issues. 1.2.0 shipped on September 22. ORD v1.17.1 documents oas-overlay-v1 as a valid definition type for REST and OData APIs, drops case-insensitive ORD ID comparison, and adds correlationIds to vendors.
GraphQL allowed interfaces with no fields and unions with no members, an RFC 1 proposal meant to keep subschemas valid. The GraphQL Foundation also published GraphiQL 6 and a budget report. JSON Schema clarified regular expression requirements for implementations, in the work-in-progress line. gRPC cut five patch releases from 1.78.2 to 1.83.2. Protobuf’s 30 merges were 26 bots.
Adoption this week: no new numbers. Monday’s probe of provider websites didn’t run, so the latest counts are still November 2’s, published last week. I’ll report two weeks of change next issue rather than repeat a table.

📡 Events, Telemetry and the Data Plane
OpenTelemetry’s RPC conventions are now released as stable. Last week #4246 was merged but not tagged. v1.45.0, released November 2, makes RPC spans and call duration metrics stable, including gRPC and Apache Dubbo. It also has a long breaking-change list. RPC metadata attributes split into rpc.request.header.<key>, rpc.response.header.<key> and rpc.response.trailer.<key>, because gRPC and Connect send metadata both before and after the payload. db.client.connection.max becomes db.client.connection.limit, and several cloud entities are removed for the v2 work. Read the notes before you upgrade.
xRegistry merged ten schema and generator fixes, among them emitting Group collection paths in OpenAPI and modeling MQTT content_type as a string. The OpenTelemetry specification merged nine and CloudEvents two. Envoy is reported for releases only and cut none.

🔐 Identity, Policy, Supply Chain
Cedar stabilized RFC 99, variadic isInRange, in its formal specification. Most of its other eight merges were proof and fuzzing work. PDPP merged six, among them describing compound key encoding as RFC 8785 canonical form. The rest were site and test work, and I found no announcement that v0.1.0 is locked.
Elsewhere: OpenFeature merged three, SPIFFE, SLSA and OCI’s runtime spec one each. OSV, Sigstore’s protobuf specs, SPDX and Security Insights merged only bot changes. SPDX 3.1 is at 47 of 114.

💹 Financial Services Data Standards
FDC3 added the 3.0 conformance results, two weeks after 3.0 shipped. The 3.1 candidates milestone has twelve issues and none closed. The Common Domain Model tagged 6.32.0 and 8.0.0-dev.14. x402 merged 51, mostly SDK work, plus preflight and postflight allowlist docs for the Solana exact scheme, and released the Python package 2.27.0. CALM merged one bot change.

🏛 From the Foundations
Two trust announcements from LF Decentralized Trust. TSP 1.0, the Trust Spanning Protocol, was approved by the Trust Over IP Technology Stack Working Group as a compact protocol for any two parties, agents included, to exchange messages. ThunderID, an agent-native identity stack from WSO2, joined as an incubating project. TSP is a specification, not in this newsletter’s registry, and I’ll look at whether it belongs there. LF AI & Data published a piece on nondeterminism in agentic applications. CNCF covered kpt v1.0.0 ahead of KubeCon NA, which runs November 9 to 12.

🤫 The Quiet Ones
Fifteen of forty-six, down from twenty.
Finished, not dead: xDS, Notary Project and TUF. The OCI image and distribution specifications were quiet this week, which is ordinary for them. CloudEvents merged two, so it isn’t on this list for once.
Quiet and worth watching: Arazzo, with the RPC pull request and the step type question still open. AsyncAPI, whose 3.0 cleanup milestone sits at 25 of 28. The OpenAPI security group, two weeks after its objects moved in from the main specification. AGENTS.md, still with no change since September 10. OpenMetrics, in-toto Attestation, OpenVEX and OpenChain also didn’t move.
Silence that is the answer to the question I get asked most: Moonwalk. Fourteenth consecutive week.
📡 Channel Health
All twenty-five working feeds returned. Volume: 28 items, from 25. The OpenAPI Initiative’s feed has now been silent for sixteen weeks. CloudEvents’ last post is from July 2024.
How This Was Made
One harvest run against the GitHub REST and GraphQL APIs and twenty-five feeds, November 1 to November 8, 2026. Merged pull requests are counted by merged_at inside the window. A release is a GitHub Release or a new tag. Bot attribution is by author login; machine accounts with ordinary logins count as people.
Where this issue says what a pull request did, I opened it and read its body or its diff. I read the MCP policy from the merged pull request, the Agent Skills terms from the governance file at the commit, and the OpenTelemetry changes from the v1.45.0 release notes. I checked the features inconsistency against v3.3-dev this morning. From calls I attended, I report only what the repositories or the groups’ published notes confirm.
Standing rules: a merge to a development branch is not a published specification. This week that covers OpenAPI 3.3, Overlay 1.3, the GenAI conventions and JSON Schema. Milestones are project news. Report the dependencies: specinfra/specref merged 1, by a person, and OAI/build-infra none.
Predictions on the record: MCP aligns its website contributing page with the new policy within two weeks. The AI Catalog merges one identifier proposal, not both, before tagging 0.9, and tags 0.9 before the end of November (carried). A2A 1.1 is not final by the end of November (carried). Arazzo 1.2 misses mid-November (carried). MCP publishes the transition calendar confirming March 30 by year end (carried). The features default is fixed before a 3.3 release candidate (carried). ORD 1.18 by the end of the year (carried).
