docs(schema): the poeOutClass census is 269/94/34, counted at this tree #2357

Merged
jaylouisw merged 1 commit from docs/1121-0317 into main 2026-11-21 03:38:52 +00:00
Owner

docs/DEVICE_SCHEMA.md says poeOutClass is a vendor vocabulary rather than a validator, and gives three catalogue readings to show how wide it is. Those readings were taken at #2237 and the catalogue has grown since, so all three are now wrong:

claim document devices/ today
ports declaring PoE+++ 261 269 (11 specs)
ports declaring passive 74 across 26 specs 94 across 35 specs
ports writing PoE+ (802.3at) 36 34 (2 Ruckus specs)

Evidence: loadCatalog("devices") (2351 specs, 0 errors) counted by interfaces[].poeOutClass. At ec39c037 (the commit that wrote the paragraph) the same count gives 261 / 74-across-26 / 34, so the first two were right then and drifted as devices landed; the parenthesised figure is 34 even at that commit, so it was a reading of something else from the start.

The rest of the paragraph is still true and unchanged: derivePortHardware() drops the string (grep poeOutClass engine/ server/ web/ is empty), and both example specs still declare the class they are cited for (devices/ubiquiti/ecs-24-poe.json 24 PoE+++ ports, devices/ubiquiti/uisp-r.json 8 passive).

Docs-only, one paragraph. No code, no counts elsewhere touched.

Gates: node scripts/syntax-check.js 512 files OK; docs-syntax 9/0; docs-commands 7/0 (73 forms, 146 commands, 96 refusals); help-forms 81/0; help-coverage 8/0 (102 advertised, 19 mechanisms, 16 shows); doc-catalog-counts 43/0 unchanged before and after.

`docs/DEVICE_SCHEMA.md` says `poeOutClass` is a vendor vocabulary rather than a validator, and gives three catalogue readings to show how wide it is. Those readings were taken at #2237 and the catalogue has grown since, so all three are now wrong: | claim | document | devices/ today | |---|---|---| | ports declaring `PoE+++` | 261 | **269** (11 specs) | | ports declaring `passive` | 74 across 26 specs | **94 across 35 specs** | | ports writing `PoE+ (802.3at)` | 36 | **34** (2 Ruckus specs) | Evidence: `loadCatalog("devices")` (2351 specs, 0 errors) counted by `interfaces[].poeOutClass`. At ec39c037 (the commit that wrote the paragraph) the same count gives 261 / 74-across-26 / 34, so the first two were right then and drifted as devices landed; the parenthesised figure is 34 even at that commit, so it was a reading of something else from the start. The rest of the paragraph is still true and unchanged: `derivePortHardware()` drops the string (`grep poeOutClass engine/ server/ web/` is empty), and both example specs still declare the class they are cited for (`devices/ubiquiti/ecs-24-poe.json` 24 `PoE+++` ports, `devices/ubiquiti/uisp-r.json` 8 `passive`). Docs-only, one paragraph. No code, no counts elsewhere touched. Gates: `node scripts/syntax-check.js` 512 files OK; docs-syntax 9/0; docs-commands 7/0 (73 forms, 146 commands, 96 refusals); help-forms 81/0; help-coverage 8/0 (102 advertised, 19 mechanisms, 16 shows); doc-catalog-counts 43/0 unchanged before and after.
docs(schema): the poeOutClass census is 269/94/34, counted at this tree
All checks were successful
CI / Classify the change (pull_request) Successful in 33s
PR rebase / Rebase onto main and arm auto-merge (pull_request) Successful in 28s
CI / Server smoke and Docker build (pull_request) Has been skipped
CI / Test (Node 22) (pull_request) Successful in 1m18s
CI / Test (Node 18) (pull_request) Successful in 1m20s
CI / Test (Node 20) (pull_request) Successful in 1m20s
CI / Arm auto-merge (pull_request) Successful in 4s
2cdb948cf1
The paragraph that says poeOutClass is a vendor vocabulary, not a validator,
carried 261 PoE+++ ports, 74 passive ports across 26 specs and 36
parenthesised PoE+ (802.3at) ports. Those were the readings at #2237; the
catalogue has grown since, and every one of them is now low or high.

Counted today with loadCatalog() over devices/: 269 ports declare PoE+++ (11
specs), 94 across 35 specs declare passive, and 34 write PoE+ (802.3at). The
two example specs still declare the class they are cited for
(ecs-24-poe.json has 24 PoE+++ ports, uisp-r.json 8 passive ones), and
nothing in engine/ reads the string, as the paragraph says.
forgejo-actions scheduled this pull request to auto merge when all checks succeed 2026-11-21 03:24:20 +00:00
jaylouisw deleted branch docs/1121-0317 2026-11-21 03:38:54 +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!2357
No description provided.