Companion to the week-40 architecture report · 2026-10-05
EAGLE4 Roadmap Review Pack
What to read before and during the roadmap session, grouped by the decision each item feeds. Site pages are public links on this research site. Lab files are internal paths on the build server; we can publish any of them as a page on request. Order within each group is the suggested reading order.
0 · Start here
EAGLE4 V80 Architecture (week 40): block diagram, 17 milestones, widths and memories per block, utilisation and timing. The baseline for every discussion below.
Companion chip product page: the product framing (1.33× vanilla H200 on HumanEval, 331 tok/s MT-Bench, measured).
RTL onboarding: repo layout, build and gate flow, for anyone who will read RTL with us.
Lab file: full audit with evidence excerpts /shared/rnd_hq/2026-10-05/tracks/arch_audit/ARCH_AUDIT.md and evidence/.
1 · Where the time goes today (per-level budget)
Lab file CEILING_AND_PIVOT.md: what limits batch-1 tok/s on a 2-card pair and where the ceiling sits. /shared/rnd_hq/2026-10-01/tracks/ceiling/
Discuss Is the remaining gap clock-bound (fmax of the drafter fabric) or latency-bound (host relay, verify)? Where would a hardened block or an ASIC change the answer?
2 · Compute array and memory
Array architecture: weights resident per lane, cross-die activation broadcast (123 of 128 lanes fed from another SLR).
Weight residency: 41.58 MiB on-chip per card, about 5× across 4 cards.
Lab file BIG_ARRAY.md: wider arrays (K_PAR32, HX2/HX3), and why they failed timing or exactness. /shared/rnd_hq/2026-10-02/tracks/big_array/
Lab file hx2q_timing/REPORT.md: cross-SLR broadcast as the binding constraint for a 32-wide array. /shared/rnd_hq/2026-10-03/tracks/hx2q_timing/
Discuss Activation broadcast across SLRs limits array width. How would your fabric or NoC (or a 2.5D/3D memory stack) change the weight-resident vs streamed trade-off?
3 · Scaling out: 4 cards and card-to-card links
Lab file ARCH_4CARD.md: the 4-card single-stream options compared. /shared/rnd_hq/2026-10-03/tracks/four_card_pipeline/
Lab files LINK_TOPOLOGIES.md, LINK_DMA_V2.md, CAPACITY_ACCEPT.md: link options and capacity vs accept. /shared/rnd_hq/2026-10-01/tracks/four_fpga_research/
Lab files CL4_SPEC.md, CL4_INTEG_REPORT.md, CABLING_CL4.md: the CL4 ring (HEAD↔HEAD merge), projected 366–368 tok/s. /shared/rnd_hq/2026-10-03/tracks/four_card_pipeline/cl4/
Lab file D2_CARD_LOOP.md: moving the level loop onto the cards. /shared/rnd_hq/2026-10-01/tracks/card_loop/
Lab file HOSTLESS_RING.md: removing the host from the data path. /shared/rnd_hq/2026-10-02/tracks/hostless_ring/
Lab file sibxe_silicon/RCA.md: first 4-card silicon run (50.00 vs 96.95 tok/s, KV-bound) and what it taught. /shared/rnd_hq/2026-10-03/tracks/sibxe_silicon/
Discuss Every 4-card gain so far depends on keeping KV and control off the host. What is the right interconnect (QSFP, PCIe P2P, a custom die-to-die link) for a product version?
4 · Platform and host path
Lab file slowdown_4card/RCA.md: SMI storm on the lab chassis, 60–78% of CPU samples in SMM. Explains why host latency dominates. /shared/rnd_hq/2026-10-03/tracks/slowdown_4card/
Lab file BIOS_CHECKLIST_BOX1.md: the platform settings that matter. /shared/rnd_hq/2026-10-03/
Discuss A 27B target with hybrid DeltaNet layers moves the bottleneck to GPU verify. Should the companion chip target the drafter only, or part of verify too?
6 · Ideas backlog and history
Lab file INNOVATION_BOARD.md: every idea tried or queued, with verdicts. /shared/rnd_hq/2026-10-02/