docs(registry): the E6616X's TM65 namespace and the 83-page CC security target carry no board census (#803) #2275

Merged
jaylouisw merged 1 commit from catalogue/1120-0752 into main 2026-11-20 08:07:52 +00:00
Owner

Refs #803 - does not close it. Registry evidence log only; no device spec, no closing keyword.

Three measurements this pass, all negative, recorded in research/open-device-requests.json and regenerated into docs/DEVICE_REGISTRY.md:

  1. Gate probe, re-run 2026-11-20 07:5x UTC: node scripts/huawei-doc-gate-probe.js --group e6600 -> 20/20 documents still 401 NOT LOGIN, "nothing changed since the baseline". The authenticated read of EDOC1100625826 is still the only route to the 配套设备 table.
  2. The TM65* namespace is closed. The 2026-11-18 note corrected the search target from TMB1*/TMK1* to TM65* (the prefix of the X's own TM65UXCL cross-connect). Two web-search queries over that namespace return no board document at all; the only TM65 string on any indexed Huawei host remains the licence footnote in the V100R025C10 brochure.
  3. The 83-page Huawei-authored Common Criteria security target is census-free. HTTP 200, 2,547,313 B, 83 pp, 157,466 extracted characters: it names the chassis and its SCC slots (E6616 UXCME:15,16 = TMK5UXCME, E6608 UXCLE:7,8 = TMK2UXCLE, E6608T TMT1SCC) and no service-board part number at all - zero matches for B1L*, TMB*, TN13*, CFP2, QSFP28.

Blocker unchanged: a TM65* service board whose chapter states frame and front panel, or the authenticated read. It is now also an engine gap - an E1/T1 configuration needs a port type engine/media.js does not have, and this stream does not change engine behaviour.

Gates: node scripts/syntax-check.js (484 files OK), node scripts/audit-port-types.js ("No port contradicts its declared type"), node test/hardware-invariants.test.js (26/26), node test/request-queue.test.js (32/32), node scripts/check-control-bytes.js (clean), node scripts/check-closing-keywords.js (0 at risk).

Refs #803 - does not close it. Registry evidence log only; no device spec, no closing keyword. Three measurements this pass, all negative, recorded in `research/open-device-requests.json` and regenerated into `docs/DEVICE_REGISTRY.md`: 1. **Gate probe, re-run 2026-11-20 07:5x UTC:** `node scripts/huawei-doc-gate-probe.js --group e6600` -> 20/20 documents still `401 NOT LOGIN`, "nothing changed since the baseline". The authenticated read of `EDOC1100625826` is still the only route to the 配套设备 table. 2. **The `TM65*` namespace is closed.** The 2026-11-18 note corrected the search target from `TMB1*`/`TMK1*` to `TM65*` (the prefix of the X's own `TM65UXCL` cross-connect). Two web-search queries over that namespace return no board document at all; the only TM65 string on any indexed Huawei host remains the licence footnote in the V100R025C10 brochure. 3. **The 83-page Huawei-authored Common Criteria security target is census-free.** HTTP 200, 2,547,313 B, 83 pp, 157,466 extracted characters: it names the chassis and its SCC slots (E6616 `UXCME:15,16` = `TMK5UXCME`, E6608 `UXCLE:7,8` = `TMK2UXCLE`, E6608T `TMT1SCC`) and no service-board part number at all - zero matches for `B1L*`, `TMB*`, `TN13*`, `CFP2`, `QSFP28`. Blocker unchanged: a `TM65*` service board whose chapter states frame and front panel, or the authenticated read. It is now also an engine gap - an E1/T1 configuration needs a port type `engine/media.js` does not have, and this stream does not change engine behaviour. Gates: `node scripts/syntax-check.js` (484 files OK), `node scripts/audit-port-types.js` ("No port contradicts its declared type"), `node test/hardware-invariants.test.js` (26/26), `node test/request-queue.test.js` (32/32), `node scripts/check-control-bytes.js` (clean), `node scripts/check-closing-keywords.js` (0 at risk).
docs(registry): the E6616X's TM65 namespace and the 83-page CC security target are both censuses-free (#803)
All checks were successful
CI / Classify the change (pull_request) Successful in 21s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 14s
CI / Server smoke and Docker build (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Successful in 1m3s
CI / Test (Node 20) (pull_request) Successful in 1m6s
CI / Test (Node 18) (pull_request) Successful in 1m9s
CI / Arm auto-merge (pull_request) Successful in 4s
546a23face
Registry evidence log only - no spec, no close. Re-measured 2026-11-20: gate probe 20/20 still 401; TM65* board documents absent from the web-search index; the Huawei-authored CC security target for the E6600 family (83 pp) names chassis/SCC slots but no service-board part number.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-20 07:57:41 +00:00
jaylouisw deleted branch catalogue/1120-0752 2026-11-20 08:07:53 +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!2275
No description provided.