research(optix): the board chapter names M05/M12/M24, so the E96xx join stays an inference (#810) #1949

Merged
jaylouisw merged 1 commit from catalogue/1118-0656 into main 2026-11-18 07:05:20 +00:00
Owner

Refs #810 (E9600 family: #807, #808, #810). Does not close: no spec is added, because the one artifact these rows need is still behind the account wall.

What was measured today (2026-11-18, crawler UA)

  1. The census exists, and the chapter's own table is now readable in a reprint: TNG1N210 — 10 x ODU2 <-> 10 x OTU2, 10 x ODU2e <-> 10 x OTU2e, all-SFP+ pluggables, 64 W typical / 67 W max — with Valid Slots: OSN 9800 M24 IU1-IU24 (1:1) / IU1-IU5, IU8-IU17, IU20-IU24 (1:3); M12 IU1-IU13; M05 IU1-IU5 (https://www.thunder-link.com/tng1n210.html, 200, 659,498 B). A reprint is a lead, not a source, so nothing is written from it.
  2. The naming split: the board chapter prints the carrier subracks, the vendor-hosted TNG2DAP frame chapter prints OptiXtrans E9605/E9612/E9624. The ranges agree slot for slot (5 / 13 / 24; the M24 1:3 set 5+10+5 = 20 is the E9624 footnote minus IU6/IU7/IU18/IU19), so the chapter supplies the port census and the placement rule but not the sentence pairing the two names.
  3. https://e.huawei.com/en/products/optical-transmission/osn-9800 (200, 348,972 B) prints the twin's slot count for the first time: M12 = 13, M24 = 12/24, at 347.2 / 747.2 mm.
  4. documents/products/<family>/<hash> pages carry the asset path in id="attachmentUrl", so scripts/huawei-material-fetch.js resolves them from a full URL. Fetched the OSN 9800 M Series 26H2 brochure (20,242,639 B docx): TNG1N 0, TNG1M 0, TNV 0, TMB 0. A brochure is not a census.

research/optixtrans-board-chapters-name-m-series.md records all four, verbatim; the three rows in research/open-device-requests.json carry the narrowed blocker and the cheapest unblock (the requester's build in one line), and docs/DEVICE_REGISTRY.md was regenerated, not edited.

Gates: node scripts/syntax-check.js 406 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 test/request-queue.test.js 32 passed / 0 failed; node scripts/check-doc-citations.js 3 suspects, all pre-existing drift.

Refs #810 (E9600 family: #807, #808, #810). Does not close: no spec is added, because the one artifact these rows need is still behind the account wall. **What was measured today (2026-11-18, crawler UA)** 1. The census exists, and the chapter's own table is now readable in a reprint: `TNG1N210` — *10 x ODU2 <-> 10 x OTU2*, *10 x ODU2e <-> 10 x OTU2e*, all-`SFP+` pluggables, 64 W typical / 67 W max — with **Valid Slots: OSN 9800 M24 IU1-IU24 (1:1) / IU1-IU5, IU8-IU17, IU20-IU24 (1:3); M12 IU1-IU13; M05 IU1-IU5** (`https://www.thunder-link.com/tng1n210.html`, 200, 659,498 B). A reprint is a lead, not a source, so nothing is written from it. 2. The naming split: the board chapter prints the **carrier** subracks, the vendor-hosted `TNG2DAP` frame chapter prints `OptiXtrans E9605/E9612/E9624`. The ranges agree slot for slot (5 / 13 / 24; the M24 1:3 set 5+10+5 = 20 is the E9624 footnote minus IU6/IU7/IU18/IU19), so the chapter supplies the port census and the placement rule but not the sentence pairing the two names. 3. `https://e.huawei.com/en/products/optical-transmission/osn-9800` (200, 348,972 B) prints the twin's slot count for the first time: M12 = 13, M24 = **12/24**, at 347.2 / 747.2 mm. 4. `documents/products/<family>/<hash>` pages carry the asset path in `id="attachmentUrl"`, so `scripts/huawei-material-fetch.js` resolves them from a full URL. Fetched the OSN 9800 M Series 26H2 brochure (20,242,639 B docx): `TNG1N` 0, `TNG1M` 0, `TNV` 0, `TMB` 0. A brochure is not a census. `research/optixtrans-board-chapters-name-m-series.md` records all four, verbatim; the three rows in `research/open-device-requests.json` carry the narrowed blocker and the cheapest unblock (*the requester's build in one line*), and `docs/DEVICE_REGISTRY.md` was regenerated, not edited. **Gates:** `node scripts/syntax-check.js` 406 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 test/request-queue.test.js` 32 passed / 0 failed; `node scripts/check-doc-citations.js` 3 suspects, all pre-existing drift.
research(optix): the board chapter names M05/M12/M24, so the E96xx join stays an inference (#810)
All checks were successful
CI / Classify the change (pull_request) Successful in 4s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 4s
CI / Server smoke test (pull_request) Successful in 5s
CI / Docker build (pull_request) Successful in 21s
CI / Test (Node 20) (pull_request) Successful in 48s
CI / Test (Node 18) (pull_request) Successful in 54s
CI / Test (Node 22) (pull_request) Successful in 52s
CI / Arm auto-merge (pull_request) Successful in 8s
9ca7422cd6
The client-board census the E9600 family is waiting for exists: the TNG1N210 chapter prints
10 x ODU2<->OTU2 and its Valid Slots table. A reseller reprint shows both, and the table names the
carrier subracks (OSN 9800 M05/M12/M24) at IU1-IU5 / IU1-IU13 / IU1-IU24 - the same ranges the
vendor-hosted TNG2DAP frame chapter prints against OptiXtrans E9605/E9612/E9624. So the chapter
supplies the port census and the placement rule, but not the sentence pairing the two names.

The carrier product page now prints the twin's slot count for the first time (M12 = 13, M24 =
12/24, 347.2 / 747.2 mm), and the OSN 9800 M Series 26H2 brochure was fetched through the
documents/products attachment route: TNG1N/TNG1M/TNV/TMB occur zero times in it.

Nothing is added to devices/; #807, #808 and #810 stay open with the unblock restated as the
requester's own build. Refs #810
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!1949
No description provided.