Nishi FamilyCompare › Frontier Radar

Frontier Radar — Living Documentation, Wiki and Developer Portal

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: 4194304 bytes. Generated by nx_swcompare_gapmap over a data-only domain spec (livingdocs.q + livingdocs.axes) — zero domain-specific code.
Envelope declared. The banked corpus FILLED the loader cap (4194304 bytes) and was truncated — momentum counts for late .q banks are a floor, not exact. Trim the .q bank set or raise the cap.
Top research opportunities (the 2025/26 frontier is active here and Nishi has no organ yet):

Capability axes

Capability axisNishi organFrontier momentum (2025/26)Signal
Dependency knowledge graphpresent
19 mentions
COVERED
Roots-to-god lineage and provenancepresent
18 mentions
COVERED
Executable and literate docsabsent
12 mentions
OPPORTUNITY
GraphRAG over the doc graphabsent
6 mentions
OPPORTUNITY
Organ cards (doc == unit)present
6 mentions
COVERED
Doc staleness and drift detectionabsent
3 mentions
OPPORTUNITY
LLM doc authoring assistabsent
3 mentions
OPPORTUNITY
Auto-generated architecture diagramspresent
0 mentions
COVERED
Content-addressed versioned storepresent
0 mentions
COVERED
Semantic and vector doc searchpresent
0 mentions
COVERED
Sovereign research fetchpresent
0 mentions
COVERED
Semantic doc diffabsent
0 mentions
dormant
Auto-recombination discoveryabsent
0 mentions
dormant

Opportunities 4 · covered 7 · dormant 2

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.