Implementation Notes for Validating Adapter Capability Manifests

Adapter manifests describe what an integration claims it can do, and validating those claims at registration keeps policy decisions grounded in verified capability.

A manifest is a claim, not a fact. Policy built on unverified claims inherits every gap between what the adapter says and what it does.

Validation steps

• Exercise each declared capability in a sandbox at registration.
• Reject manifests claiming capabilities the probe cannot confirm.
• Re-validate on version change, not just first install.

Use the adapter system, integration guide, and security docs to ground adapter policy in verified capability instead of declared intent.