Chiplets combine into packages. Packages combine into clusters.
Finished packages are never fused into new packages. That single rule is what keeps a product family from becoming a series of unrelated redesigns.
A catalog, not a chip
The blocks we design are drawn from a fixed catalog: an orchestrator carrying the session state machine and trust root; lean compute for low-precision inference; dense compute for training mathematics; a memory-I/O block carrying the controllers and the transcode engine; a host-attach block; and a licensable core.
Products are combinations
A serving part, a training part, an edge system-on-chip and a licensable IP core are not four programmes. They are four selections from one catalog, sharing one architecture, one compiler target and one software stack.
Software follows the smallest body
Compliance with the licensable subset is enforced in the compiler from the first day, so that software written for the largest part runs on the smallest one.
Empty sockets, budgeted now
The package carries standard-interface sockets that are deliberately left empty in the first generation. Their power, thermal and fabric budget is allocated in the current design, so a future substrate arrives as new hardware dropped into an existing socket, never as a software switch, and never as a redesign.
Neuromorphic wake engine
Event-driven silicon is a natural fit for the one job this architecture does constantly: deciding, continuously and at very low power, which of many thousands of sleeping sessions is about to be needed. A spiking substrate watching hint traffic and idle timers would do that at a fraction of the energy of a conventional controller.
Exploratory · gen-2/3Analog in-memory attention
Attention is dominated by multiply-accumulate over values that tolerate approximation. Analog computation in memory offers a very different energy curve for exactly that shape of work, at the cost of precision that the verification path can absorb.
Exploratory · gen-2/3Photonic interconnect
Session migration between packages and across a fabric is bandwidth the electrical interface has to carry. Optical attach is the credible long-term answer, and the socket is budgeted for it now rather than retrofitted later.
Exploratory · gen-2/3These are reserved design options, not committed products. They are described here because allocating the budget for them now is a present architectural decision with present cost, not because any schedule attaches to them.
The session machine orchestrates whatever arrives
A reserved socket is only useful if something already knows how to use what lands in it. The session state machine is that something. It already schedules work against tiers with different latency, energy and durability characteristics, and it already decides which session should be where.
A neuromorphic wake engine is, from the architecture's point of view, another predictor feeding the same prefetch path. Analog attention is another compute tier with different precision. Photonics is another link with different bandwidth. None of them requires the architecture to change shape, which is precisely why the sockets are worth budgeting for before the parts exist.
What this is and is not
- It is a present decision to allocate package area, power and fabric budget to standard-interface sockets.
- It is not a commitment to develop, source or ship any particular future substrate.
- No date, specification or availability attaches to anything on this page.