diff --git a/specification/ai-catalog.md b/specification/ai-catalog.md
index cbc6c18..696d997 100644
--- a/specification/ai-catalog.md
+++ b/specification/ai-catalog.md
@@ -513,15 +513,16 @@ A Trust Manifest MUST contain:
   DID, SPIFFE ID, or URL; these are illustrative and the set of
   identity schemes is open.
 
-When a Trust Manifest appears within a Catalog Entry, the `identity`
-field's trust domain MUST align with the publisher domain in the
-containing entry's `identifier` field. This binding ensures
-trust claims are associated with the authorized publisher namespace even
-when `identity` and `identifier` use different URI schemes.
-Consumers MUST reject a Trust Manifest whose `identity` domain does not
-align with the publisher domain in the containing entry's `identifier`.
-The `identity` is carried here so domain binding is part of the signed
-payload, rather than inferred only from unsigned entry context.
+When a Trust Manifest appears within a Catalog Entry whose
+`identifier` uses the `urn:air` naming format, consumers MUST
+extract the publisher domain from the identifier and verify that
+the `identity` field's authority or trust domain aligns with it.
+Consumers MUST reject a Trust Manifest whose identity domain does
+not align with the extracted publisher domain. For all other
+identifier formats, the identifier is opaque to the trust
+verification process; consumers MUST NOT attempt to derive a
+publisher domain from it and SHOULD rely on other verification
+instead, such as attestations or signature verification.
 
 When a Trust Manifest appears on a Host Info object, `identity`
 SHOULD match the host's `identifier` field when present.