{
  "id": "page:process-gaps-GAP-L2-P1-mcptransport-status-attribute-undeclared",
  "_kind": "Page",
  "_file": "wiki/process/gaps/GAP-L2-P1-mcptransport-status-attribute-undeclared.md",
  "_cluster": "wiki",
  "attributes": {
    "nodeKind": "Page",
    "title": "GAP-L2-P1-mcptransport-status-attribute-undeclared",
    "displayName": "GAP-L2-P1-mcptransport-status-attribute-undeclared",
    "slug": "process/gaps/GAP-L2-P1-mcptransport-status-attribute-undeclared",
    "articlePath": "wiki/process/gaps/GAP-L2-P1-mcptransport-status-attribute-undeclared.md",
    "article": "# GAP-L2-P1-mcptransport-status-attribute-undeclared\n\n| Field | Value |\n|---|---|\n| id | gap:mcptransport-status-attribute-undeclared |\n| title | MCPTransport.status / specVersion fields used in examples but not declared in NodeKind |\n| level | 2 |\n| priority | P1 |\n| discoveredAt | 2026-04-28T00:00:00Z |\n| source | grep MCPTransport in ontology-schema.yaml vs examples |\n| status | closed |\n| owner | tbd |\n\n## Current state\n`ontology-schema.yaml` defines `MCPTransport` with attributes: `id, displayName, kind, specUrl`. The example `streamable-http.yaml` uses **two extra fields**: `specVersion: \"2025-03-26\"` and `status: live`. These are not declared in the NodeKind. This breaks V-12.5 (NodeKind ↔ examples must be consistent).\n\n## Desired state\nAdd `specVersion: string` and `status: enum<live,deprecated,community,draft>` to the `MCPTransport` NodeKind definition, OR remove them from the examples.\n\n## Evidence\n- C:/work/v6/graph/schema/ontology-schema.yaml lines 139-152\n- C:/work/v6/graph/schema/examples/compute/mcp-transports/streamable-http.yaml\n\n## Propagation status\n- Level 2: open\n\n## Propagation chain\n- Level 2: 1 attribute addition each on NodeKind + transport.md update.\n\n## Notes\nSame root cause as GAP-L1-P2-mcp-stdio-vs-http-sse-deprecation but framed as Level 2 internal-consistency.\n\n## Resolution (2026-04-28)\nClosed. `MCPTransport` NodeKind in `ontology-schema.yaml` now declares `specVersion: string`, `specRevisions: list<string>`, `currentSpecRevision: string`, `streaming: enum<none,partial,full>`, and `status: enum<live,deprecated,community,draft>`. All four example YAMLs (stdio, streamable-http, http-sse, websocket) conform.\n",
    "documents": []
  },
  "outgoingEdges": [],
  "incomingEdges": []
}