UCP vendors and extensions
Every UCP capability is governed by a domain, encoded in its reverse-DNS namespace. Grouping the stores we check by that namespace authority shows the core protocol (ucp.dev) and the vendors publishing their own capabilities and extensions on top of it.
Core protocol
The dev.ucp.* namespace, reserved for capabilities governed by the UCP Tech Council. Everything else extends these.
Vendors
Third parties publishing capabilities under their own reverse-DNS namespace. The spec says a vendor's declared schema URL must be served from its own authority domain; the badge shows whether that holds.
Authority binding is a normative MUST in the UCP spec (Namespace Governance, normative in release 2026-08-25): an entity's schema URL must come from its namespace authority domain, so a name can be shown to belong to the party that claims it. UCP Checker runs that check across every store we check, the same way for everyone.
Methodology note (2026-07-28): verdicts follow the spec's host-derived rule as refined by spec PR #627 (merged 2026-07-24): a binding passes when the entity name equals the reversed schema host exactly, or begins with it as a label-aligned prefix. This accepts the exact-match case #627 allowed and, stricter than our earlier check, rejects schemas served from unaligned subdomains (a shared CDN host, for example). Some verdicts changed on that date because of the rule, not because stores changed what they publish.
