# Portfolio Profile

|                       |                                 |
| --------------------- | ------------------------------- |
| **Identifier**        | `urn:adl:profile:portfolio:1.0` |
| **Status**            | Draft                           |
| **ADL Compatibility** | 0.3.x                           |

note

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

## Overview[​](#overview "Direct link to Overview")

The Portfolio Profile extends ADL with agent relationships and business domain membership capabilities. It enables organizations to track agent dependencies, composition hierarchies, and business domain alignment at scale using Domain-Driven Design (DDD) concepts.

Catalog identity and classification are handled by the [Registry Profile](/profiles/registry/overview.md) — a sibling profile with no dependency.

## Use Cases[​](#use-cases "Direct link to Use Cases")

* Agent dependency tracking and impact analysis
* Orchestrator-to-sub-agent composition mapping
* Domain-driven agent organization (bounded contexts, subdomains)
* Deployment order determination
* Agent relationship visualization

## Quick Start[​](#quick-start "Direct link to Quick Start")

Add the Portfolio Profile to your ADL document:

```
{

  "adl_spec": "0.3.0",

  "name": "Customer Service Agent",

  "description": "Handles customer inquiries and support requests.",

  "version": "1.0.0",

  "profiles": ["urn:adl:profile:portfolio:1.0"],

  "relationships": {

    "depends_on": ["urn:adl:agent:acme:knowledge-base-agent:1.0"],

    "orchestrated_by": "urn:adl:agent:acme:support-orchestrator:1.0"

  },

  "domain": {

    "domain_id": "urn:domain:customer-service",

    "subdomain": "inquiries",

    "role": "primary-handler"

  }

}
```

## Additional Members[​](#additional-members "Direct link to Additional Members")

The Portfolio Profile adds the following top-level members:

| Member          | Required       | Description                                         |
| --------------- | -------------- | --------------------------------------------------- |
| `relationships` | At least one\* | Agent dependencies and composition relationships    |
| `domain`        | At least one\* | Business/functional domain membership (DDD-aligned) |

\* At least one of `relationships` or `domain` **MUST** be present.

See the [full specification](/profiles/portfolio/specification.md) for detailed member definitions.

## Key Concepts[​](#key-concepts "Direct link to Key Concepts")

### Relationship Tracking[​](#relationship-tracking "Direct link to Relationship Tracking")

The `relationships` member models agent dependencies (`depends_on`), orchestration hierarchies (`composed_of`, `orchestrated_by`), and peer collaborations (`peers`). This enables deployment ordering, impact analysis, and relationship visualization.

### Domain Alignment[​](#domain-alignment "Direct link to Domain Alignment")

The `domain` member aligns agents with business capabilities using DDD concepts: domain identifiers, subdomains, bounded contexts, and roles within domains.

### Multi-Profile Composition[​](#multi-profile-composition "Direct link to Multi-Profile Composition")

Organizations that need catalog identity alongside portfolio relationships declare the [Registry Profile](/profiles/registry/overview.md) as a sibling:

```
{

  "profiles": [

    "urn:adl:profile:registry:1.0",

    "urn:adl:profile:portfolio:1.0"

  ]

}
```