```json
{
  "s": "Proposes an 'AI Substitutive Use' vocabulary category to allow parties to express preferences about how digital assets are used by AI systems during inference, particularly when outputs substitute for originals. Positions this as a nested category within the broader Automated Processing framework.",
  "n": 2,
  "nn": "Incremental refinement of existing preference expression mechanisms; applies established vocabulary/metadata concepts to a specific AI use case without fundamental technical innovation.",
  "m": 2,
  "mn": "Early-stage sketch focusing on category definition and conceptual framing; lacks detailed syntax specifications, enforcement mechanisms, or implementation guidance despite 5-page format.",
  "o": 4,
  "on": "Significant overlap with content/usage preference frameworks (robots.txt derivatives, machine-readable rights expressions, Creative Commons-inspired metadata), primarily differentiating scope rather than approach.",
  "mo": 2,
  "mon": "Single draft with nested dependency on concurrent AIPREF-VOCAB work; minimal evidence of WG consensus or community iteration beyond initial proposal.",
  "r": 4,
  "rn": "Directly addresses practical AI governance concern (generative model training/inference control) with clear relevance to agent/automated system policy frameworks, though narrower than comprehensive AI agent protocols.",
  "c": [
    "Policy/governance",
    "Data formats/interop",
    "AI safety/alignment",
    "Model serving/inference"
  ]
}
```


```json
{
  "s": "Proposes AIIP, a dedicated protocol layer for autonomous systems to execute real-world actions via a resolve-invoke-execute-receipt pattern with cryptographic verification. Explicitly scopes out discovery, registration, orchestration, and control planes, focusing narrowly on execution boundaries and verifiable receipts.",
  "n": 2,
  "nn": "Incremental framing of execution delegation as a protocol layer; resolve-invoke-execute pattern and cryptographic receipts are established concepts, though their application to a dedicated autonomous plane shows some structuring novelty.",
  "m": 2,
  "mn": "Early sketch stage—9 pages defining architectural boundaries and patterns but lacking concrete protocol details, message formats, state machine definitions, error handling procedures, or implementation guidance.",
  "o": 4,
  "on": "Significant conceptual overlap with existing agent communication frameworks (FIPA ACL), RPC/microservice invocation patterns, and blockchain-style transaction receipts. The 'autonomous access plane' concept echoes service mesh and sidecar architectures.",
  "mo": 1,
  "mon": "Single revision dated 2026-03-25 with no evidence of working group traction, community discussion, or iterative development. No apparent momentum beyond initial submission.",
  "r": 3,
  "rn": "Partially relevant to AI agents—addresses execution delegation and cryptographic accountability, which are important for autonomous systems, but scopes away discovery and orchestration, limiting applicability to broader agent ecosystem concerns.",
  "c": [
    "A2A protocols",
    "Autonomous netops",
    "Agent identity/auth",
    "Data formats/interop"
  ]
}
```


```json
{
  "s": "Proposes using MOQT (Media over QUIC Transport) as a substrate for the Agent-to-Agent protocol, leveraging MOQT's publish/subscribe model and prioritization to handle AI agent communication requirements. Focuses on mapping A2A protocol needs onto MOQT's streaming and discovery mechanisms.",
  "n": 2,
  "nn": "Incremental combination of existing technologies; applies established MOQT framework to A2A without introducing fundamental innovation in either protocol layer.",
  "m": 2,
  "mn": "Early draft stage; abstract describes intent but document length (12 pages) suggests limited protocol definition, likely missing implementation details, test vectors, and deployment guidance.",
  "o": 4,
  "on": "Significant overlap with existing pub/sub and QUIC-based transport work; MOQT already standardizes media over QUIC, and agent communication protocols exist in parallel efforts.",
  "mo": 1,
  "mon": "Single revision (2025-10-20 date), no apparent WG sponsorship mentioned, appears exploratory without evidence of community adoption or iterative development cycle.",
  "r": 3,
  "rn": "Partially relevant to AI agents; addresses agent-to-agent communication and discovery but lacks depth on core AI/agent concerns like alignment, safety, policy, or model serving.",
  "c": [
    "A2A protocols",
    "Data formats/interop",
    "Agent discovery/reg"
  ]
}
```