UNREACHABLE: Enflame's own S60 product page and hardware doc centre are behind a WAF that blocks four independent client types, and no Wayback capture exists

UNREACHABLE, 2026-10-05. Recorded so that a future pass does not re-spend four client types discovering that Enflame's first-party S60 material cannot be read from here. data/accelerators/enflame-s60 already has an empty flops array on secondary sources; this record establishes WHY no first-party figure could be attempted, which is a stronger statement than 'none found'. FOUR INDEPENDENT CLIENT TYPES, ALL BLOCKED, all returning HTTP 403: 1. web_extract / scrape service on https://www.enflame-tech.com/product-technologies/s60 and on the doc centre https://support.enflame-tech.com/onlinedoc_hw/5-s6x/S60/product_manual/ -> 'document_antibot: Scrape aborted after exceeding retry limit'. 2. curl with a full desktop User-Agent (Mozilla/5.0 Windows NT 10.0; Win64; x64 AppleWebKit/537.36 Chrome/120 Safari/537.36) -> HTTP 403, zero bytes. 3. A REAL HEADLESS BROWSER session (not a scraper) on https://support.enflame-tech.com/onlinedoc_hw/5-s6x/S60/product_manual/ -> the WAF's own interstitial page, verbatim: 'img 403 / 您的请求已中断 / 您提交的请求可能对网站造成威胁，无法访问 / 可能原因 / Web应用防护服务检测您当前访问存在Web安全风险或访问不合规' with a request UUID. This is an application-firewall verdict on the session, not a rate limit and not a missing page. 4. The Wayback Machine: the availability API returns 'archived_snapshots: {}' - NO capture at all - for support.enflame-tech.com/onlinedoc_hw/5-s6x/S60/index.html, for www.enflame-tech.com/product-technologies/s60, and for enflame-tech.com/en/product/s60.html. A CDX index query for the same two URL patterns returns zero rows. So there is no archived copy to fall back on, which closes the 'try a mirror or an archived copy' route for the vendor's own pages. THE ONLY S60 SPECIFICATION VALUES THAT CIRCULATE ARE THIRD-PARTY, and they are consistent with each other on the parts they share: 48 GB, 672 GB/s, PCIe Gen5 x16, 300W maximum, FP32/FP16/BF16/INT8 supported. A secondary compilation of Enflame's own product manual states it saw the manual and found it does NOT publish peak per-precision compute, and specifically corrects an earlier 'FP16 100 TFLOPS (estimated)' as an estimate rather than an Enflame figure. That is consistent with the empty flops array on the record, but it is still second-hand: the manual itself is behind the WAF. SO THE HONEST STATE: the S60's memory capacity, bandwidth, interface, power and supported precisions are attested only by secondary sources; its compute is attested by NO source at all, first-party or otherwise. Do not populate flops from an estimate. The TechInsights floorplan-analysis source the record already cites is a die-level teardown and is the one first-party-adjacent document that is readable - it gives floorplan and capacity facts, not a vendor compute claim.