LUMA is a 36-month hardware-software research programme built around one measurable chain: a defined inference service becomes a physically qualified machine state, then progressively stronger compute, memory, control and integration mechanisms are accepted only when they improve the same service/resource boundary.
The consortium PDF carries the full task register. This public-safe view shows the same technical direction without partner budgets, private repository paths or unconfirmed institutional commitments.
Compound Pulse freezes model, workload, quality/SLO and economics. The compute-characterization lane returns operation/precision/expert/state demand; the memory lane returns traffic/reuse/bandwidth constraints; the physical-backend lane returns measured FPGA-node bandwidth, latency, power and toolchain evidence.
NEXT → WP2 mechanism teams + WP3 backend/controlMechanism owners return bounded low-bit/MoE, sparse/event-driven, near-memory or configurable compute packages. Each package carries executable RTL/HLS or an implementation-ready architecture, golden tests, interface/state map, build constraints and QoR evidence.
NEXT → physical backend build/run; DFX transition framework where persona-compatible; runtime-control descriptors; Compound Pulse qualificationThe runtime-control lane applies, observes, verifies and retains or rolls back. The DFX lane owns state-safe partial reconfiguration. The physical-backend lane owns admitted FPGA build/run and synchronized timing, bandwidth, latency, power, temperature and service evidence.
NEXT → Compound Pulse same-service qualification + measured corrective feedbackThe physical-integration lane converts endpoint traffic, clock, power and interface requirements into PITV/SI/PI/PDN/thermal evidence. A semiconductor/implementation lane returns a named target/toolchain artifact with timing, resources/PPA, power and reproducibility.
NEXT → WP5 integrated qualificationCompound Pulse closes TTFT/TPOT, accepted goodput, device/server provision, wall power, J/accepted output and cost/accepted output. A failed gate returns only to the responsible result owner with the measured deficit.
NEXT → accepted state to WP6; rejected state to its named ownerCompound Pulse integrates the deployable bundle and Resource Boundary Report. Technical partners contribute only the foreground and reproducibility package for the artifact they own; there is no generic all-partners WP6 task.
NEXT → customer/operator/design partner + evidence-based post-project hardening decisionNamed upstream team and exact artifact/version you receive.
One bounded technical task with a hands-on builder and a 36-month sequence.
Executable or physical artifact, evidence record and reproducibility material.
Named downstream team that consumes your output and the interface it expects.
Measured FOMs that connect the artifact to accepted service, energy, resource provision or cost.
The M12 customer gate is a defined physical/software bundle, while the RIA remains technically active through M36.
Workload cells, node profiles, early physical-interface exploration, first architecture decisions and R1-v0.
First RTL/PIM/persona implementations; one qualified FPGA backend path; L0 apply/observe/verify; synchronized service/power evidence; first RBR.
Second mechanism generation; at least two qualified paths; state-safe A↔B DFX; measured switch cost, rollback and service continuity.
PITV/board integration, power/thermal/interface evidence and corrective technical iteration.
Broader workloads, recovery stress, second backend and repeated integrated evidence.
Final reproducibility, TRL4 evidence, customer/operator release and result-owner handoffs.
The public execution model is intentionally role-based. Exact workload traces, R1 records, test vectors, source modules and black-box specifications move only after institutional confidentiality/cooperation alignment and are limited to the recipient's role.
Public execution model + current programme roadmap + your role-specific interface summary.
Exact role inputs, test vectors, backend/interface records and relevant source modules.
Artifact identity, tool/build provenance, measured FOMs, acceptance result and downstream handoff.