research(optixtrans): the E6616X page is a shell in every locale, and the archive kept the shell (#803) #2304

Merged
jaylouisw merged 1 commit from catalogue/1120-1922 into main 2026-11-20 19:39:25 +00:00
Owner

Refs #803 - no closing keyword: no spec file is added, because the census is still unpublished.

Three surfaces measured this pass, all negative and all previously unrecorded.

  1. Every locale of the product page is the /cn/ soft-200 shell. https://e.huawei.com/<locale>/products/optical-transmission/optixtrans-e6616x vs a control slug optixtrans-e6699 in the same locale: es/de/tr/fr answer 200 byte-identically (325,313 / 323,642 / 328,556 / 328,984 B), ru/ja answer 301, 165 B, identical for both slugs, and none of the twelve bodies contains E6616X. So a 200 on any e.huawei.com product path is not evidence a page exists.

  2. Wayback kept the shell, not the payload. Three captures of support.huawei.com/enterprise/en/optical-transmission/optixtrans-e6616x-pid-257173887; the two pre-gate ones (2024-03-02, 356,312 B; 2024-12-13, 641,154 B) contain zero occurrences of TMB, TM65, TMK, B1L, EDOC, Slot, 100G - the document list is client-side.

  3. The hardware-description pages were never archived at all. CDX returns [] for .../doc/EDOC1100456166, EDOC1100558549 and EDOC1100625826.

So the "find an older edition" and "another locale" routes are closed by measurement, not assumption. Both blockers stand: a build (E6616X DC (n x TMB2TPS), 32x E1/T1 per assembly; no vendor source states the slot cost or the per-board census) and an E1/T1 port type in engine/media.js, which polices as a V.35 socket today.

Written up in research/optixtrans-e6616x-locale-and-archive-shells.md so the next pass does not spend a fire on either route. Gates on this branch: syntax-check 494 files OK, audit-port-types 0 gated, check-doc-citations unchanged drift.

Refs #803 - no closing keyword: no spec file is added, because the census is still unpublished. Three surfaces measured this pass, all negative and all previously unrecorded. 1. **Every locale of the product page is the `/cn/` soft-200 shell.** `https://e.huawei.com/<locale>/products/optical-transmission/optixtrans-e6616x` vs a control slug `optixtrans-e6699` in the same locale: es/de/tr/fr answer **200 byte-identically** (325,313 / 323,642 / 328,556 / 328,984 B), ru/ja answer **301, 165 B, identical** for both slugs, and none of the twelve bodies contains `E6616X`. So a 200 on any `e.huawei.com` product path is not evidence a page exists. 2. **Wayback kept the shell, not the payload.** Three captures of `support.huawei.com/enterprise/en/optical-transmission/optixtrans-e6616x-pid-257173887`; the two pre-gate ones (2024-03-02, 356,312 B; 2024-12-13, 641,154 B) contain **zero** occurrences of `TMB`, `TM65`, `TMK`, `B1L`, `EDOC`, `Slot`, `100G` - the document list is client-side. 3. **The hardware-description pages were never archived at all.** CDX returns `[]` for `.../doc/EDOC1100456166`, `EDOC1100558549` and `EDOC1100625826`. So the "find an older edition" and "another locale" routes are closed by measurement, not assumption. Both blockers stand: **a build** (`E6616X DC (n x TMB2TPS)`, 32x E1/T1 per assembly; no vendor source states the slot cost or the per-board census) and **an E1/T1 port type** in `engine/media.js`, which polices as a V.35 socket today. Written up in `research/optixtrans-e6616x-locale-and-archive-shells.md` so the next pass does not spend a fire on either route. Gates on this branch: `syntax-check` 494 files OK, `audit-port-types` 0 gated, `check-doc-citations` unchanged drift.
research(optixtrans): the E6616X page is a shell in every locale, and the archive kept the shell (#803)
All checks were successful
CI / Classify the change (pull_request) Successful in 15s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 13s
CI / Server smoke and Docker build (pull_request) Successful in 28s
CI / Test (Node 22) (pull_request) Successful in 1m1s
CI / Test (Node 20) (pull_request) Successful in 1m4s
CI / Test (Node 18) (pull_request) Successful in 1m8s
CI / Arm auto-merge (pull_request) Successful in 4s
bb89b67a90
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-20 19:28:31 +00:00
jaylouisw deleted branch catalogue/1120-1922 2026-11-20 19:39:26 +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!2304
No description provided.