Nishi FamilyCompare › Frontier Radar

Frontier Radar — Autonomous Team and Software Agents

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: 2475896 bytes. Generated by nx_swcompare_gapmap over a data-only domain spec (team.q + team.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
Lineage and provenance trackingpresent
1388 mentions
COVERED
Long-horizon planning and memoryabsent
95 mentions
OPPORTUNITY
Multi-agent orchestrationpresent
64 mentions
COVERED
Benchmark-scored agent evaluationabsent
52 mentions
OPPORTUNITY
Verified refusal (no fabricated success)present
49 mentions
COVERED
Anti-drift claim coachingpresent
39 mentions
COVERED
Autonomous execute-and-verify looppresent
21 mentions
COVERED
Issue-to-patch repository pipelineabsent
19 mentions
OPPORTUNITY
Work board with heartbeat livenesspresent
4 mentions
COVERED
LLM code-authoring agentabsent
3 mentions
OPPORTUNITY
Autonomy measurementpresent
0 mentions
COVERED
Sandboxed agent runtimeabsent
0 mentions
dormant

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