Extension model

GPARS is designed to be extended without modifying the core specification. The manifest schema includes an extensions field for custom metadata, and the following rules govern how extensions should behave.

Agents MAY declare additional metadata such as domain-specific configuration, advisory classifications, or discovery hints.
Extension points MUST NOT violate the ICS/ES separation.
Extension metadata MUST NOT be treated as an authorization grant.
Extension namespaces SHOULD use reverse-domain notation to avoid collisions.

Example — a research agent declaring custom configuration in its manifest:

{
  "id": "org:example/agent:research-v1",
  "capabilities": [
    {
      "id": "web_research",
      "description": "Can navigate web sources and read retrieved research material."
    }
  ],
  "extensions": {
    "org.example.research": {
      "max_search_depth": 3,
      "preferred_sources": ["arxiv", "scholar"]
    }
  }
}