Nishi Family › Compare › Frontier Radar

Frontier Radar — Debugging and Diagnosis (Doctor)

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: 2015343 bytes. Generated by nx_swcompare_gapmap over a data-only domain spec (doctor.q + doctor.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 debuggingabsent
128 mentions		OPPORTUNITY
Record-replay time travelabsent
15 mentions		OPPORTUNITY
Permanent regression witnessespresent
14 mentions		COVERED
Per-function miscompile bisectionpresent
13 mentions		COVERED
Breakpoint debuggerabsent
12 mentions		OPPORTUNITY
Test-case reduction at scaleabsent
8 mentions		OPPORTUNITY
Living trap registerpresent
7 mentions		COVERED
Compile-fail diagnosispresent
5 mentions		COVERED
Codegen-shape fuzz generationpresent
4 mentions		COVERED
Autonomous health witnesspresent
3 mentions		COVERED
Core-dump analysisabsent
0 mentions		dormant

Opportunities 4 · covered 6 · 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.