docs(registry): #130 - the EU store, the FCC grant index and Wayback are all empty #1864

Merged
jaylouisw merged 1 commit from catalogue/1117-1525 into main 2026-11-17 15:34:33 +00:00
Owner

Refs #130 - this does not close it. No spec is added: no vendor surface publishes a UDW-PRO port layout.

Three surfaces that could still have hidden a real product, all checked 2026-11-17 and all empty:

  1. Regional SKU. https://eu.store.ui.com/eu/en/category/all-cloud-gateways - 200, 487,282 B, server-rendered. The cloud-gateway grid publishes one Dream Wall: udw-eu, the 420 W UDW. udw-pro occurs zero times in those bytes.
  2. Certification. Ubiquiti's grantee prefix is SWX. https://fccid.io/SWX-UDW answers 200 (83,318 B, "Digital Transmission Radio"); SWX-UDWPRO, SWX-UDW-PRO and SWX-UDW2 all answer 303 (no grant). An uncertified radio cannot have shipped - that is the mechanism behind the empty techspecs and store surfaces. fccid.io is a mirror, so this is strong evidence rather than the Commission's own index (fcc.report answers 403 to a crawler).
  3. A withdrawn page. http://archive.org/wayback/available returns "archived_snapshots": {} for techspecs.ui.com/unifi/cloud-gateways/udw-pro, store.ui.com/us/en/products/udw-pro, store.ui.com/products/udw-pro and ui.com/unifi/cloud-gateways/udw-pro. Nothing was ever crawled.

The one vendor-authored sentence that names a Pro is Ubiquiti's early-access store copy: "The Dream Wall and Dream Wall Pro (UDW/UDW Pro) are wall-mounted UniFi OS Consoles..." - and the feature list printed under it is the UDW's (17 GbE RJ45 with 4 PoE++/4 PoE+/4 PoE, 2.5 GbE WAN, 10G SFP+ WAN and LAN), beside "Dream Wall Pro - Coming Soon". So the product was announced, never listed, and has no census anywhere.

research/ubiquiti-cloud-gateway-catalogue.md gains the section recording all of this; research/open-device-requests.json carries it into the #130 row of docs/DEVICE_REGISTRY.md (regenerated, not hand-edited) so the next pass does not re-check the EU storefront, the grant index or Wayback.

Gates: syntax-check 389 files OK; audit-port-types no contradiction; hardware-invariants + catalogue-hygiene + doc-catalog-counts 26 assertions, 0 failed; check-control-bytes clean; regen-registry-doc --check current at 2,348 models / 29,235 sockets / 966 shapes.

No device spec changed, so the importer's capability tripwire is not exercised by this PR.

Refs #130 - this does not close it. No spec is added: no vendor surface publishes a UDW-PRO port layout. Three surfaces that could still have hidden a real product, all checked 2026-11-17 and all empty: 1. **Regional SKU.** `https://eu.store.ui.com/eu/en/category/all-cloud-gateways` - 200, 487,282 B, server-rendered. The cloud-gateway grid publishes one Dream Wall: `udw-eu`, the 420 W UDW. `udw-pro` occurs zero times in those bytes. 2. **Certification.** Ubiquiti's grantee prefix is `SWX`. `https://fccid.io/SWX-UDW` answers 200 (83,318 B, "Digital Transmission Radio"); `SWX-UDWPRO`, `SWX-UDW-PRO` and `SWX-UDW2` all answer 303 (no grant). An uncertified radio cannot have shipped - that is the mechanism behind the empty techspecs and store surfaces. fccid.io is a mirror, so this is strong evidence rather than the Commission's own index (`fcc.report` answers 403 to a crawler). 3. **A withdrawn page.** `http://archive.org/wayback/available` returns `"archived_snapshots": {}` for `techspecs.ui.com/unifi/cloud-gateways/udw-pro`, `store.ui.com/us/en/products/udw-pro`, `store.ui.com/products/udw-pro` and `ui.com/unifi/cloud-gateways/udw-pro`. Nothing was ever crawled. The one vendor-authored sentence that names a Pro is Ubiquiti's early-access store copy: *"The Dream Wall and Dream Wall Pro (UDW/UDW Pro) are wall-mounted UniFi OS Consoles..."* - and the feature list printed under it is the UDW's (17 GbE RJ45 with 4 PoE++/4 PoE+/4 PoE, 2.5 GbE WAN, 10G SFP+ WAN and LAN), beside *"Dream Wall Pro - Coming Soon"*. So the product was announced, never listed, and has no census anywhere. `research/ubiquiti-cloud-gateway-catalogue.md` gains the section recording all of this; `research/open-device-requests.json` carries it into the `#130` row of `docs/DEVICE_REGISTRY.md` (regenerated, not hand-edited) so the next pass does not re-check the EU storefront, the grant index or Wayback. Gates: `syntax-check` 389 files OK; `audit-port-types` no contradiction; `hardware-invariants` + `catalogue-hygiene` + `doc-catalog-counts` 26 assertions, 0 failed; `check-control-bytes` clean; `regen-registry-doc --check` current at 2,348 models / 29,235 sockets / 966 shapes. No device spec changed, so the importer's capability tripwire is not exercised by this PR.
docs(registry): #130's last three surfaces are empty - EU store, FCC grants, Wayback
All checks were successful
CI / Classify the change (pull_request) Successful in 9s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 14s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 26s
CI / Test (Node 20) (pull_request) Successful in 52s
CI / Test (Node 18) (pull_request) Successful in 1m0s
CI / Test (Node 22) (pull_request) Successful in 58s
CI / Arm auto-merge (pull_request) Successful in 7s
9deec506d0
The Dream Wall Pro is not a regional SKU, holds no FCC grant under any Pro
variant of Ubiquiti's SWX prefix, and was never crawled by the Wayback Machine,
so there is no withdrawn page to recover. Ubiquiti's early-access copy names
"the Dream Wall and Dream Wall Pro (UDW/UDW Pro)" and then lists only the UDW's
ports, beside "Dream Wall Pro - Coming Soon".

Records the three checks in research/ubiquiti-cloud-gateway-catalogue.md and
carries them into the open-request row so the next pass does not re-walk them.
Refs #130 - the request stays open; no port census exists to model from.
jaylouisw force-pushed catalogue/1117-1525 from 9deec506d0
All checks were successful
CI / Classify the change (pull_request) Successful in 9s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 14s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 26s
CI / Test (Node 20) (pull_request) Successful in 52s
CI / Test (Node 18) (pull_request) Successful in 1m0s
CI / Test (Node 22) (pull_request) Successful in 58s
CI / Arm auto-merge (pull_request) Successful in 7s
to 2a5d438b9a
All checks were successful
CI / Classify the change (pull_request) Successful in 11s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 9s
CI / Server smoke test (pull_request) Successful in 9s
CI / Docker build (pull_request) Successful in 23s
CI / Test (Node 20) (pull_request) Successful in 48s
CI / Test (Node 22) (pull_request) Successful in 51s
CI / Test (Node 18) (pull_request) Successful in 55s
CI / Arm auto-merge (pull_request) Successful in 17s
2026-11-17 15:32:25 +00:00
Compare
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
jaylouisw/packetforge!1864
No description provided.