Nishi Family › Compare › Frontier Radar

Frontier Radar — Deployment and Live Hosting

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: 2713786 bytes. Generated by nx_swcompare_gapmap over a data-only domain spec (deploy.q + deploy.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
One-command source to livepresent
368 mentions		COVERED
OPAQUE-PAKE control-plane authpresent
187 mentions		COVERED
Sovereign TLS edge (no 3rd-party terminator)present
125 mentions		COVERED
Fleet inventory + ops events (SSE)present
119 mentions		COVERED
Supervision + crash-loop backoffpresent
106 mentions		COVERED
Build on target from sourcepresent
92 mentions		COVERED
Instant rollbackpresent
74 mentions		COVERED
Autoscale / scale-to-zeroabsent
58 mentions		OPPORTUNITY
Multi-region / edge placementabsent
55 mentions		OPPORTUNITY
Ops dashboardpresent
30 mentions		COVERED
Canary / progressive deliveryabsent
21 mentions		OPPORTUNITY
GitOps declared-state reconcileabsent
12 mentions		OPPORTUNITY
Health-gated promote + auto-rollbackpresent
10 mentions		COVERED
Secrets rotation planeabsent
8 mentions		OPPORTUNITY
Content publish plane (sha-pinned)present
6 mentions		COVERED
Preview environments per changeabsent
0 mentions		dormant

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