# Integration name

State the product problem this integration solves in one sentence.

## Identity and support

- Primary contract: RoomAgent, DelegationAdapter, ToolHandler, MediaAdapter,
  VoiceAdapter, or a named purpose-built service boundary.
- Package/source revision:
- Runtime contract and RMC revision tested:
- Provider/model/service version, if relevant:
- Maintainer and support route:
- Status: example, maintained integration, deprecated, or proposed.

## Behavior

- Trigger and required capabilities:
- Input schema and a synthetic example:
- Output schema and a synthetic example:
- Ordering, duplicate handling, and retry identity:
- Timeout, cancellation, and shutdown behavior:
- Restart behavior and any replay/checkpoint responsibility:
- Bounds: payload, concurrency, queueing, and expected workload:

## Authority and data

- Required action/resource grants:
- Data received from RMC and why it is needed:
- External destinations and data sent to each:
- Credential configuration (names/references only; never credential values):
- Visibility of derived outputs:
- Deployment policy or residency requirements and how they are enforced:
- Execution trust: in-process reviewed code or separate service boundary:

## Adoption

- Source and complete runnable example:
- Host registration/configuration steps:
- Required provider/service setup:
- Validation evidence, with tested versions and known gaps:
- Upgrade, rollback, and deprecation guidance:

This is a documentation template. RMC does not parse it as an installation
manifest or enforce claims solely because they appear here.