{"_comment":"EXAMPLE profile declarations for the com.provecart.conformity extension, following the declaration shape in UCP's contributing guide: a vendor extension is self-hosted under its publisher's namespace and declared in each side's profile with {version, extends, spec, schema}. Illustrative, not normative; capability version strings for the parent capabilities are placeholders for the versions a deployment actually negotiates.","business_profile":{"_comment":"The Business (or its checkout provider) runs or relays the conformity check and emits the conformity object and messages on its checkout responses.","capabilities":{"dev.ucp.shopping.checkout":[{"extensions":{"com.provecart.conformity":[{"extends":["dev.ucp.shopping.checkout","dev.ucp.lodging.booking"],"schema":"https://provecart.com/standards/acf-v0.2.schema.json","spec":"https://provecart.com/standards/correction-format","version":"0.2.0"}]},"version":"<negotiated>"}]}},"platform_profile":{"_comment":"The Platform (agent side) declares that it understands the conformity code vocabulary and will act on the extension fields: apply in-authorization repairs, escalate requires_buyer_review messages to the buyer, and stop on the retry budget.","capabilities":{"dev.ucp.shopping.checkout":[{"extensions":{"com.provecart.conformity":[{"extends":["dev.ucp.shopping.checkout","dev.ucp.lodging.booking"],"schema":"https://provecart.com/standards/acf-v0.2.schema.json","spec":"https://provecart.com/standards/correction-format","version":"0.2.0"}]},"version":"<negotiated>"}]}}}