Claims and Scope

Current project record generated from claims.json. Horizon RunMap has an implemented MoE inference architecture, published results and a public app that completed IFEval on another RTX 4060 computer. One full-residency OLMoE 0924 configuration recorded 61.26 post-first-token decode tokens/s at 5.99 GiB whole-worker peak VRAM on the RTX 5070 (source result). How can storage precision, execution precision, residency and data movement be coordinated under a constrained GPU-memory budget?

Implemented and measured claims

• Selective INT4 compression of routed experts with a separate FP16 non-routed path. Status: implemented-in-recorded-paths. Source
• Compact expert GPU execution with FP16 activations and recorded scalar/grouped executors. Status: implemented-in-recorded-paths. Source
• Partial residency observations under the selected campaign contract. Status: measured. Experiment: residency39.
• OLMoE c64 full residency observations with Grouped T3. Status: measured. Experiment: residency39.
• Complete IFEval instruction-following evaluation of retained Horizon responses. Status: measured. Experiment: ifeval541.
• Public desktop app for running the architecture and IFEval. Status: available. Source
• The public app completed the full IFEval process on another computer with an RTX 4060. Status: completed. Source

Scope of the recorded results

The published numbers retain their model, executor, hardware and workload. The app and external RTX 4060 execution are project milestones in the same architecture, recorded separately from the three original scored evidence editions. The machine record keeps the formal claim boundaries for technical inspection.

Reading the evidence

• Compare residency within an executor family: OLMoE c30-c60 use PRODUCT-core scalar, while c64 uses Grouped T3.
• IFEval 541 and the earlier 120-pair behavioral study are separate experiments.
• The public app enables external execution; each historical evidence edition retains its own stated verification and reproduction status.
• Read ADR 0009 invariants as the documented immutable-cache contract and each historical executor under its recorded contract.

Runtime source access: private by author decision. The public app provides an execution path, while evidence and verification identifies the original experiment artifacts.