For platforms whose partners build the connectors buyers install
Connector BadgeA badge is a promise about next quarter, not a record of one review - make it one a buyer can check.
Describe the catalog, paste the criteria, the badged connectors with their latest values, the support lines and the decertification ladder. Your browser runs the go/no-go gate, ranks the tier shape, holds every criterion to metric, threshold, window, minimum volume and measurer, checks a support sentence per tier and the four ladder rungs, evaluates every badged connector against the criteria and its kit and platform pins, and gives every proposal a verdict. Then the charter, and the partner notices.
The catalog, and a short interview free
Criteria, connectors, support and the ladder free
The checks free
What the page flags
The gates
The tier shapes, ranked
Every criterion in its six parts
Every connector against the criteria
Area by area
Your criteria table free
The table the skill prints in the charter - every criterion in its six parts - with the ones to rewrite marked.
Criteria (Markdown)
The certification charter metered
Pricing as soon as the session is ready...
Sign inThe reply could not be read. Here it is as it came back:
Caveats
Caveats
The page's check of this reply
Saved badge reviews
How it works - and what is sourced
The gate follows the skill: certify only when a buyer or procurement reads the label, partner connectors carry a fifth of installs or include the most-installed, and a runnable kit or per-connector telemetry with a fault split is affordable - otherwise ownership labels only, each with its support statement, and a re-check date. One quality tier over ownership labels is the default; a telemetry-gated second tier when buyers compare connectors for one system. A criterion counts only with a threshold, a window, a minimum volume and a measurer; vague, commercial and self-attested criteria, and usage minimums on the tier that unlocks production, are flagged.
Each badged connector is evaluated against the valid criteria: telemetry below the minimum volume reads insufficient, never failed. An unpatched vulnerability blocks new installs on the fast path; no release and no support reply past the abandonment window blocks too, unless volume is above the usage bar, when the connector is offered to a new maintainer first; two failed evaluations in a row suspend the badge, one opens a warning; a badge pinned to an old kit or platform is re-run. On a no-go, every badge reverts to its ownership label.