research(ubiquiti): UDW-PRO - a SKU-keyed register that really 404s, and a forum reprint demoted #2076

Merged
jaylouisw merged 1 commit from catalogue/1119-0252 into main 2026-11-19 03:08:09 +00:00
Owner

Refs #130 — no spec was added and the request stays open.

Three measurements on the Dream Wall Pro, none of which publishes a census.

1. A sub-tree of techspecs.ui.com that really 404s. The Next.js build manifest
(/_next/static/O4loEueJJ_fzZc5I2r7Ta/_buildManifest.js, 200, 3,349 B) shows every product path is a
dynamic route over 13 sortedPages, so there is no static route list to enumerate — but it exposed
/compliance/chile/[[...sku]], a SKU-keyed SUBTEL register:

URL result
.../compliance/chile/udw 200, 615,226 B — names Dream Wall, UDW, UDW-EU
.../compliance/chile/udw-pro 404, 512,657 B — 404 - This page could not be found
.../compliance/chile/udwpro 404, 512,657 B
.../compliance/chile (index) 200, 549,642 B; trailing slash → 308
.../compliance/udw (no locale) 307 → /

This is the first sub-tree on that host that answers a real status for a SKU it lacks, so the
standing "a 200 here is meaningless, the negative is unfalsifiable" caveat does not reach it. The
Pro is absent from it, as it is from the marketing tree.

2. The UDW census from a non-techspec vendor surface. Archived collection page
store.ui.com/us/en/collections/unifi-dream-wall/products/udw @ 20230603042814 (200, 124,982 B):
navigation prints the family as Dream Wall / Dream Machine / Dream Router only, and the box as
(17) LAN GbE RJ45, (1) WAN 2.5 GbE RJ45, (1) LAN + (1) WAN 10G SFP+, PoE (4)/(4)/(4). Zero hits for
Dream Wall Pro, udw-pro, Coming Soon. It agrees with devices/ubiquiti/udw.json exactly (20
interfaces), so no spec change — the file was already right and stays safe to point a requester at.

3. Correction. The sentence the ledger attributes to "Ubiquiti's early-access copy" — "the Dream
Wall and Dream Wall Pro", "Dream Wall Pro - Coming Soon" — has no Ubiquiti URL; its only citation is
the third-party forum ubiquiti-networks-forum.de/board/thread/4925-.... Wayback holds no 2022
capture of any store.ui.com udw page (earliest 2023-06-03) or any ui.com dream-wall page
(earliest 2023-10-18), so that EA page was never crawled. It is recorded as a reprint, and it can no
longer carry the "not a shipping product, therefore closable" inference — docs/RESOLUTIONS.md
keeps such a request open.

Files: research/ubiquiti-udw-pro-absent-from-vendor-catalogue.md,
research/open-device-requests.json, regenerated docs/DEVICE_REGISTRY.md.

Gates: syntax-check 435 files OK; audit-port-types no port contradicts its declared type;
hardware-invariants 26 passed, 0 failed; registry doc regenerated (2,357 models).

Refs #130 — no spec was added and the request stays open. Three measurements on the Dream Wall Pro, none of which publishes a census. **1. A sub-tree of `techspecs.ui.com` that really 404s.** The Next.js build manifest (`/_next/static/O4loEueJJ_fzZc5I2r7Ta/_buildManifest.js`, 200, 3,349 B) shows every product path is a dynamic route over 13 `sortedPages`, so there is no static route list to enumerate — but it exposed `/compliance/chile/[[...sku]]`, a SKU-keyed SUBTEL register: | URL | result | |---|---| | `.../compliance/chile/udw` | **200**, 615,226 B — names `Dream Wall`, `UDW`, `UDW-EU` | | `.../compliance/chile/udw-pro` | **404**, 512,657 B — `404 - This page could not be found` | | `.../compliance/chile/udwpro` | **404**, 512,657 B | | `.../compliance/chile` (index) | 200, 549,642 B; trailing slash → **308** | | `.../compliance/udw` (no locale) | **307** → `/` | This is the first sub-tree on that host that answers a real status for a SKU it lacks, so the standing "a 200 here is meaningless, the negative is unfalsifiable" caveat does not reach it. The Pro is absent from it, as it is from the marketing tree. **2. The UDW census from a non-techspec vendor surface.** Archived collection page `store.ui.com/us/en/collections/unifi-dream-wall/products/udw` @ 20230603042814 (200, 124,982 B): navigation prints the family as Dream Wall / Dream Machine / Dream Router only, and the box as (17) LAN GbE RJ45, (1) WAN 2.5 GbE RJ45, (1) LAN + (1) WAN 10G SFP+, PoE (4)/(4)/(4). Zero hits for `Dream Wall Pro`, `udw-pro`, `Coming Soon`. It agrees with `devices/ubiquiti/udw.json` exactly (20 interfaces), so **no spec change** — the file was already right and stays safe to point a requester at. **3. Correction.** The sentence the ledger attributes to "Ubiquiti's early-access copy" — "the Dream Wall and Dream Wall Pro", "Dream Wall Pro - Coming Soon" — has no Ubiquiti URL; its only citation is the third-party forum `ubiquiti-networks-forum.de/board/thread/4925-...`. Wayback holds no 2022 capture of any `store.ui.com` udw page (earliest 2023-06-03) or any `ui.com` dream-wall page (earliest 2023-10-18), so that EA page was never crawled. It is recorded as a reprint, and it can no longer carry the "not a shipping product, therefore closable" inference — `docs/RESOLUTIONS.md` keeps such a request open. Files: `research/ubiquiti-udw-pro-absent-from-vendor-catalogue.md`, `research/open-device-requests.json`, regenerated `docs/DEVICE_REGISTRY.md`. Gates: `syntax-check` 435 files OK; `audit-port-types` no port contradicts its declared type; `hardware-invariants` 26 passed, 0 failed; registry doc regenerated (2,357 models).
research(ubiquiti): UDW-PRO - a SKU-keyed register that really 404s, and the forum reprint the ledger called vendor copy
All checks were successful
CI / Classify the change (pull_request) Successful in 8s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 7s
CI / Server smoke test (pull_request) Successful in 15s
CI / Docker build (pull_request) Successful in 25s
CI / Test (Node 20) (pull_request) Successful in 57s
CI / Test (Node 22) (pull_request) Successful in 1m0s
CI / Test (Node 18) (pull_request) Successful in 1m6s
CI / Arm auto-merge (pull_request) Successful in 3s
8e074143da
Refs #130.
jaylouisw deleted branch catalogue/1119-0252 2026-11-19 03:08:12 +00:00
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!2076
No description provided.