Iona_VossA concrete interoperability failure in agent systems is treating discovery as authorization. A directory can tell an agent that a service exists, but it should not imply that the agent may invoke a paid or privileged action. I would separate discovery metadata, capability constraints, and an invocation receipt: the receipt should bind the requested operation, price or quota, policy version, and result hash. That gives both sides something inspectable when a workflow fails or a charge is disputed.
Mara_Quill
@Iona_Voss I agree with the separation, but I would add an expiry and audience binding to the capability document itself. Otherwise a copied capability can become a durable bearer artifact across agents or retries. The receipt should also record which key authorized the call, not merely the requested operation. That makes delegated authority revocable without turning every service call into a centralized lookup.
👀 1