sync: record atgbics special-case backfill
This commit is contained in:
parent
b60fb362e8
commit
7f4e7f03ad
@ -1,6 +1,6 @@
|
|||||||
# Current TIP Sync State
|
# Current TIP Sync State
|
||||||
|
|
||||||
Updated: 2026-05-09 16:01 UTC
|
Updated: 2026-05-09 16:05 UTC
|
||||||
|
|
||||||
## Newest Work
|
## Newest Work
|
||||||
|
|
||||||
@ -32,6 +32,36 @@ Updated: 2026-05-09 16:01 UTC
|
|||||||
- run the same hardened custom-worker end-to-end path for `magatamallm` and the next `fo_blogllm` version
|
- run the same hardened custom-worker end-to-end path for `magatamallm` and the next `fo_blogllm` version
|
||||||
- keep Gitea/proxmox mirror work as a separate infrastructure closure item
|
- keep Gitea/proxmox mirror work as a separate infrastructure closure item
|
||||||
|
|
||||||
|
- ATGBICS deterministic special-case backfill on 2026-05-09:
|
||||||
|
- precheck:
|
||||||
|
- after the explicit URL evidence pass, ATGBICS still had `139` near-complete rows
|
||||||
|
- `32` matched safe protocol/product-class cases:
|
||||||
|
- loopback/test modules
|
||||||
|
- 10GBASE-T / RJ45 copper
|
||||||
|
- 10GBASE-LRM
|
||||||
|
- BX60 / BXD-60 / BXU-60
|
||||||
|
- CWDM 10G 60km
|
||||||
|
- CSR rows
|
||||||
|
- DB correction:
|
||||||
|
- loopback/test modules -> `N/A` reach/fiber/wavelength, `Loopback / Test Module`
|
||||||
|
- 10GBASE-T/RJ45 -> `30m`, `Copper`, `N/A`
|
||||||
|
- LRM -> `220m`, `MMF`, `1310`
|
||||||
|
- BX60 -> `60km`, `SMF`, directional BiDi wavelength evidence
|
||||||
|
- CWDM 10G 60 -> `60km`, `SMF`, source wavelength
|
||||||
|
- CSR -> `400m`, `MMF`, `850`
|
||||||
|
- result:
|
||||||
|
- `32` ATGBICS rows detail-verified
|
||||||
|
- `32` additional rows promoted to fully verified
|
||||||
|
- ATGBICS near-complete missing details reduced from `139` to `107`
|
||||||
|
- global `details_verified=12030`
|
||||||
|
- global `fully_verified=10753`
|
||||||
|
- health:
|
||||||
|
- public TIP health stayed `healthy`
|
||||||
|
- load status `ok`
|
||||||
|
- memory used `12%`
|
||||||
|
- truth:
|
||||||
|
- remaining ATGBICS rows need detail-page extraction; they are mostly generic OEM/part-number pages where URL slug does not encode the reach
|
||||||
|
|
||||||
- ATGBICS explicit URL evidence backfill on 2026-05-09:
|
- ATGBICS explicit URL evidence backfill on 2026-05-09:
|
||||||
- precheck:
|
- precheck:
|
||||||
- ATGBICS had `485` price+image+URL-complete rows still lacking detail verification
|
- ATGBICS had `485` price+image+URL-complete rows still lacking detail verification
|
||||||
|
|||||||
@ -0,0 +1,40 @@
|
|||||||
|
# ATGBICS Deterministic Special-Case Backfill - 2026-05-09
|
||||||
|
|
||||||
|
## Precheck
|
||||||
|
|
||||||
|
- After the explicit URL evidence pass, ATGBICS still had `139` near-complete rows
|
||||||
|
- `32` matched safe protocol/product-class cases:
|
||||||
|
- loopback/test modules
|
||||||
|
- 10GBASE-T / RJ45 copper
|
||||||
|
- 10GBASE-LRM
|
||||||
|
- BX60 / BXD-60 / BXU-60
|
||||||
|
- CWDM 10G 60km
|
||||||
|
- CSR rows
|
||||||
|
|
||||||
|
## DB Correction
|
||||||
|
|
||||||
|
- Loopback/test modules -> `N/A` reach/fiber/wavelength, `Loopback / Test Module`
|
||||||
|
- 10GBASE-T/RJ45 -> `30m`, `Copper`, `N/A`
|
||||||
|
- LRM -> `220m`, `MMF`, `1310`
|
||||||
|
- BX60 -> `60km`, `SMF`, directional BiDi wavelength evidence
|
||||||
|
- CWDM 10G 60 -> `60km`, `SMF`, source wavelength
|
||||||
|
- CSR -> `400m`, `MMF`, `850`
|
||||||
|
|
||||||
|
## Result
|
||||||
|
|
||||||
|
- `32` ATGBICS rows detail-verified
|
||||||
|
- `32` additional rows promoted to fully verified
|
||||||
|
- ATGBICS near-complete missing details reduced from `139` to `107`
|
||||||
|
- Global `details_verified=12030`
|
||||||
|
- Global `fully_verified=10753`
|
||||||
|
|
||||||
|
## Health
|
||||||
|
|
||||||
|
- TIP public health stayed `healthy`
|
||||||
|
- Load status stayed `ok`
|
||||||
|
- Memory used `12%`
|
||||||
|
|
||||||
|
## Truth Policy
|
||||||
|
|
||||||
|
Remaining ATGBICS rows need detail-page extraction. They are mostly generic OEM/part-number pages where the URL slug does not encode the reach.
|
||||||
|
|
||||||
Loading…
x
Reference in New Issue
Block a user