Nishi Family › Compare › Frontier Radar

Frontier Radar — GPU Worker Mesh and Distributed Inference

Where the 2025/26 research frontier is moving, and where Nishi should test, deepen, or research next.

How this works. The nishi researcher banked the current (2024-2026) frontier for this domain over sovereign TLS (keyless OpenAlex/arXiv). For each capability axis this radar measures frontier momentum = how often the frontier corpus mentions it, times our organ presence (probed on disk). Absent + hot = a research opportunity / where to test. Corpus measured: 3256786 bytes. Generated by nx_swcompare_gapmap over a data-only domain spec (workermesh.q + workermesh.axes) — zero domain-specific code.
Top research opportunities (the 2025/26 frontier is active here and Nishi has no organ yet):
Capability axisNishi organFrontier momentum (2025/26)Signal
Capability-scoped job dispatchpresent
120 mentions		COVERED
Streaming responsesabsent
72 mentions		OPPORTUNITY
Worker health probepresent
69 mentions		COVERED
Cross-host GPU worker routingpresent
49 mentions		COVERED
Push results to consumable storagepresent
43 mentions		COVERED
Multi-worker load balancingpresent
40 mentions		COVERED
Dynamic request batchingpresent
38 mentions		COVERED
Model load and unloadpresent
37 mentions		COVERED
Autoscaling scale-to-zeropresent
26 mentions		COVERED
Native GPU container governancepresent
23 mentions		COVERED
Multi-model multiplexing on one GPUabsent
14 mentions		OPPORTUNITY
Content-addressed model registrypresent
11 mentions		COVERED
Sovereign end-to-end actuationpresent
9 mentions		COVERED
Request queue admission controlpresent
4 mentions		COVERED

Opportunities 2 · covered 12 · dormant 0

frontier momentum is a mechanical keyword count over real 2024-2026 works; our presence is probed on disk. A discovery signal, not a ranking of importance. Zero JS, zero trackers.