Nishi FamilyCompare › Frontier Radar

Frontier Radar — NishiLang and Compiler Toolchain

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: 3196215 bytes. Generated by nx_swcompare_gapmap over a data-only domain spec (lang.q + lang.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
LLM-assisted compiler testing and repairabsent
145 mentions
OPPORTUNITY
SSA optimization pipelinepresent
74 mentions
COVERED
Memory safety / ownership typesabsent
40 mentions
OPPORTUNITY
Type systems (inference / exhaustiveness)present
34 mentions
COVERED
Language server / IDE integrationabsent
20 mentions
OPPORTUNITY
Compiler fuzzing / random test generationpresent
13 mentions
COVERED
Verified compilation / translation validationabsent
11 mentions
OPPORTUNITY
Diagnostics / error-message qualityabsent
9 mentions
OPPORTUNITY
Auto-vectorizationabsent
8 mentions
OPPORTUNITY
Register allocation (linear scan)present
3 mentions
COVERED
Energy-efficient language runtimespresent
3 mentions
COVERED
Differential / EMI compiler testingpresent
2 mentions
COVERED
Test-case reduction / bisectionpresent
1 mentions
COVERED
WebAssembly backendpresent
0 mentions
COVERED
Equality saturation / superoptimizationpresent
0 mentions
COVERED
Incremental compilation / build cacheabsent
0 mentions
dormant

Opportunities 6 · covered 9 · dormant 1

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.