Silicon Peninsula #026 — The CXL pilot needs a workload agreement before a memory order

Monday, November 9, 2026 · For AI-infrastructure evaluation and memory-sourcing teams · Dated-source follow-up, reviewed November 9

The judgement and the tape

Write the service acceptance conditions before adding pooled memory to a purchasing forecast. Today we revisit the NAVER Cloud CXL proof of concept covered in issue 015 and turn it into a proposed evaluation brief. The reviewed documents remain dated October announcements. We have not recovered a new production-service acceptance or a customer purchase commitment in this review. This is a follow-up framework, not an overnight launch, a benchmark we performed or a claim about market-wide absence.

Signal 1 — a named workload is a test boundary

SK hynix's October 16 report describes PoC validation with NAVER Cloud involving agentic-AI KV-cache sharing and OmniServe embedding sharing. It identifies service contexts; it does not describe those demonstrations as a generally available production service. Original company account.

Why it matters: Ask the application owner to name the repeated operation the trial should improve. Freeze the model and software revision, request mix, concurrency, context-length distribution and comparison configuration. Choose an acceptance metric and a guardrail together: for example, response behavior under the same service requirement, alongside error handling and resource use. These are our proposed fields, not published trial conditions. Without a stable comparison, a better-looking run may answer a different question from the one procurement needs.

The decision sheet

Signal 2 — capacity is a configuration, not acceptance

The same October 16 report specifies a second-generation 256GB CMM-DDR5 product based on CXL 3.2. Those supplier-reported specifications identify hardware to discuss; they do not identify a customer order quantity. Module source.

Why it matters: A useful trial brief records the complete supported configuration, the software owner and the expected support period. Ask who supplies an alternative if the chosen configuration changes. Keep the bill of materials separate from the acceptance record. The trial may justify a larger deployment, a narrower application or no purchase at all. An evaluator should record which result would change the decision before observing the result. That reduces the temptation to turn a component specification into a service-economics conclusion.

Signal 3 — the integration owner belongs in the buying process

The OCP report also describes pooled-memory and hybrid-memory demonstrations with multiple partners. Separately, SK hynix's October 22 infrastructure explanation places compute, memory, storage, networking, power and cooling in early co-design. These are architecture and collaboration descriptions. System demonstrations; dated co-design explanation.

Why it matters: Procurement needs a responsibility map as well as a performance sheet. Our proposed review asks who owns configuration changes, incident triage, rollback and recovery after maintenance. Record an operator and an application contact, rather than assuming every question belongs to the memory vendor. A partner appearing in a demonstration does not establish the commercial contract or revenue allocation. The useful supplier opportunity is a specific unresolved integration task that a customer agrees matters, followed by evidence of acceptance and a defined delivery route.

What changed, Korea-only radar and the watch number

Issue 015 introduced the workload demonstration. This follow-up adds a draft evaluation agreement: baseline, acceptance owner, configuration boundary and operating responsibility. Issue 025's early-design power partnership raised a similar ownership question. The watch number is 256GB, the dated module specification, not validated service capacity. The reviewed material is already in English, so no exclusivity or measured lead is claimed. Specification source.

The next seven days

Our editorial checks are November 10 for foundry continuity and CXMT, November 11 for optics and earnings boundaries, November 12 for equipment and trade evidence, November 13 for power collaboration, and November 16 for this CXL evaluation framework. These are our review dates, not company events. A customer-issued service acceptance, a supported deployment guide or attributable purchasing evidence would change the commercial assessment. Until then, mark the missing field and its owner instead of treating an open question as a negative result.

Silicon Peninsula reads Korean semiconductor filings and company sources, separates documented facts from interpretation, and records the next evidence to check. Reply with a company you want tracked. Our 30-day Korea Watchlist Pilot covers an agreed watchlist; scope is confirmed before payment.