Our conclusions are bounded by official documentation. Unknown data stays unknown and physical tests are never implied.
Evidence hierarchy
| Level | Meaning | How it is shown |
|---|---|---|
| L1 | Official manufacturer, platform or standards documentation | Documented field or conditional path |
| L2 | Official support or release note | Dated support change; firmware and rollout must be checked |
| L3 | Reproducible hands-on test | None in this data pack |
| L4 | Community report | Never promoted to official confirmation by itself |
Verdict rules
| Status | When we use it |
|---|---|
| Conditional | An official route exists but requires a matching model, region, controller, firmware or feature. |
| Not verified | The needed claim or exact combination is not established in the research. |
| Specific path unavailable | Official evidence shows a required radio or role is absent for that direct path. |
| Partial features | Connection is documented but a requested function is missing or separately unverified. |
Data boundaries
The seed registry contains 78 brand or brand-group entries and 296 original model candidates. The original detailed pack held 143 researched product or model-family records and 170 connection paths. Dated official-source additions bring this site to 158 records and 184 paths; the 78 original hub-child edges are unchanged. No physical pair test was performed. Unmapped candidate names stay separate from documented model pages.
How a result is computed
The checker first matches the exact product ID and target ecosystem to a recorded path. It then checks only the hub role and feature fields actually documented in the pack. A missing path returns “not verified”; it never guesses from a shared Matter logo. Device-to-device results require a separately recorded hub-child edge.
Publication and corrections
A product page may publish documented fields with explicit uncertainty. A regional specification conflict is held from the product catalog. We update a claim only after reviewing its official source and retain the original route where possible. Source retrieval dates and content-change dates are different.