research(optix): E6600 board chapters prove compatibility, not slots - TMB2DMS is mirror-only #2022

Merged
jaylouisw merged 1 commit from catalogue/1118-1922 into main 2026-11-18 19:37:33 +00:00
Owner

Refs #803 (research only - no catalogue entry is added by this pull request).

Walks the exact next step the previous pass named: a Huawei board chapter naming TMB2PD1 / TMB2DMS / TMB2TPS, on the e-file route that produced (6)-UXCME and (21)-TMB3AUX. Five queries, no Huawei-hosted asset for any of the three; the only copies are reseller reprints of the board chapters.

New evidence, research/optixtrans-e6616x-2m-pair-chapter-format.md:

  • https://www.szhuaxunjia.com/product/2298.html (TMB2DMS) prints 接口规格: 支持32路75Ω/120Ω的E1接口或者100Ω的T1接口 and a 配套关系 table listing E6616X with TM65UXCL from V100R022C10SPC010; .../2297.html (TMB2PD1) carries the same rows and states the PD1 has no panel ports - the DMS presents all 32.
  • Correction to the ledger's standing criterion: E6600 board chapters have no Valid Slots table at all (zero occurrences in (6)-UXCME and (21)-TMB3AUX too); compatibility is a 配套设备 table, unlike the E9600 chapters. Asking for "a Valid Slots table naming E6616X" asks for a section this family never prints, so research/open-device-requests.json is re-aimed at the TMB2DMS chapter itself (EDOC1100558549, any of the six editions).
  • No spec is written: the numbers above are on a re-hosted page, and the chapter states no slot cost, so a fourteen-slot complement still cannot be derived. devices/ is untouched.

Near-miss recorded so it is not re-walked: actfornet.com/solutions/solution/OptiXtrans_E66000_Boards_Overview is titled as the gated boards-overview document, but its content index is a stub, its indexed PDH section is the TMB1 generation, and its title covers E6608T/E6608/E6616 - not the X.

Gates: node scripts/syntax-check.js 421 files OK; node scripts/audit-port-types.js "No port contradicts its declared type"; node test/hardware-invariants.test.js 26 passed, 0 failed; node scripts/regen-registry-doc.js --check current (2,357 models / 258 vendors / 29,726 sockets / 972 shapes); importer dry run "Would add: 0".

Refs #803 (research only - no catalogue entry is added by this pull request). Walks the exact next step the previous pass named: a Huawei board chapter naming `TMB2PD1` / `TMB2DMS` / `TMB2TPS`, on the e-file route that produced `(6)-UXCME` and `(21)-TMB3AUX`. Five queries, no Huawei-hosted asset for any of the three; the only copies are reseller reprints of the board chapters. New evidence, `research/optixtrans-e6616x-2m-pair-chapter-format.md`: - `https://www.szhuaxunjia.com/product/2298.html` (TMB2DMS) prints `接口规格: 支持32路75Ω/120Ω的E1接口或者100Ω的T1接口` and a 配套关系 table listing **E6616X with TM65UXCL from V100R022C10SPC010**; `.../2297.html` (TMB2PD1) carries the same rows and states the PD1 has no panel ports - the DMS presents all 32. - Correction to the ledger's standing criterion: E6600 board chapters have **no Valid Slots table at all** (zero occurrences in `(6)-UXCME` and `(21)-TMB3AUX` too); compatibility is a 配套设备 table, unlike the E9600 chapters. Asking for "a Valid Slots table naming E6616X" asks for a section this family never prints, so `research/open-device-requests.json` is re-aimed at **the TMB2DMS chapter itself** (EDOC1100558549, any of the six editions). - No spec is written: the numbers above are on a re-hosted page, and the chapter states no slot cost, so a fourteen-slot complement still cannot be derived. `devices/` is untouched. Near-miss recorded so it is not re-walked: `actfornet.com/solutions/solution/OptiXtrans_E66000_Boards_Overview` is titled as the gated boards-overview document, but its content index is a stub, its indexed PDH section is the `TMB1` generation, and its title covers E6608T/E6608/E6616 - not the X. Gates: `node scripts/syntax-check.js` 421 files OK; `node scripts/audit-port-types.js` "No port contradicts its declared type"; `node test/hardware-invariants.test.js` 26 passed, 0 failed; `node scripts/regen-registry-doc.js --check` current (2,357 models / 258 vendors / 29,726 sockets / 972 shapes); importer dry run "Would add: 0".
research(optix): the E6600 board chapters prove compatibility, not slots - TMB2DMS is mirror-only
All checks were successful
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 4s
CI / Classify the change (pull_request) Successful in 5s
CI / Server smoke test (pull_request) Successful in 8s
CI / Docker build (pull_request) Successful in 24s
CI / Test (Node 20) (pull_request) Successful in 51s
CI / Test (Node 22) (pull_request) Successful in 55s
CI / Test (Node 18) (pull_request) Successful in 1m0s
CI / Arm auto-merge (pull_request) Successful in 32s
d684bd4cc7
Refs #803. The candidates the last pass named (TMB2PD1/TMB2DMS/TMB2TPS) are
hosted by nobody but resellers: five queries on the e-file route that yielded
(6)-UXCME and (21)-TMB3AUX return no Huawei asset for any of them. The reprints
state 32 x E1/T1 on the DMS panel and list E6616X with TM65UXCL from
V100R022C10SPC010, but a re-hosted page is not a source - so no spec, and the
ledger's unblock criterion is corrected: E6600 chapters carry a 配套设备 table,
never a Valid Slots one, so the artifact to ask for is the TMB2DMS chapter.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-18 19:30:24 +00:00
jaylouisw deleted branch catalogue/1118-1922 2026-11-18 19:37:35 +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!2022
No description provided.