Registry Profile

Identifier	urn:adl:profile:registry:1.0
Status	Draft
ADL Compatibility	0.1.x

note

This profile is in draft status. The specification is stable for early adoption, but minor changes may occur before 1.0.

Overview

The Registry Profile extends ADL with agent catalog identity, classification, and federation capabilities. It enables organizations to manage agents across enterprise registries, support multi-path classification, and federate agent definitions across multiple registry instances.

When this profile is declared in an ADL document's profiles array, the document MUST satisfy all requirements defined in this specification.

Use Cases

• Enterprise agent registries and catalogs
• Multi-path agent classification by business domain
• Agent discovery across organizational boundaries
• Multi-registry federation and synchronization
• Access control scoping (private, internal, public)

Quick Start

Add the Registry Profile to your ADL document:

{
  "adl_spec": "0.1.0",
  "name": "Compliance Review Agent",
  "description": "Reviews documents for regulatory compliance.",
  "version": "2.0.0",
  "profiles": ["urn:adl:profile:registry:1.0"],
  "registry": {
    "catalog_id": "urn:acme:agents:compliance-review:2.0.0",
    "catalog_classification": [
      {
        "domain": "compliance",
        "subdomain": "document-review",
        "capability": "soc2-review"
      }
    ],
    "visibility": "internal"
  }
}

Additional Members

The Registry Profile adds the following top-level member:

Member	Required	Description
registry	REQUIRED	Agent catalog identity, classification, and federation information

registry

Field	Type	Required	Description
catalog_id	string	REQUIRED	Unique identifier within the registry catalog
catalog_classification	array	Optional	Multi-path catalog classification entries
visibility	string	Optional	Visibility scope: private, internal, public
federation	object	Optional	Multi-registry publishing configuration

See the full specification for detailed member definitions and validation rules.

Relationship to Other Profiles

The Registry Profile is independent — it has no dependencies on other profiles.

• Portfolio Profile — Tracks agent relationships and domain alignment. Organizations may use portfolio without a formal registry. Declare both as siblings when you need both.
• Governance Profile — Tracks compliance and governance controls. An agent can be governed without being registered, and vice versa.

{
  "profiles": [
    "urn:adl:profile:registry:1.0",
    "urn:adl:profile:governance:1.0",
    "urn:adl:profile:portfolio:1.0"
  ]
}