Nishi Family › Compare › Frontier Radar

Frontier Radar — Authorization and Permissions

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: 290529 bytes. Generated by nx_swcompare_gapmap over a data-only domain spec (authz.q + authz.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
Relationship tuples object relation subjectpresent
11 mentions		COVERED
Horizontal scale distributed cacheabsent
3 mentions		OPPORTUNITY
OPAQUE identity bindingabsent
2 mentions		OPPORTUNITY
Consistency tokens snapshot readsabsent
1 mentions		OPPORTUNITY
Block and consent axispresent
0 mentions		COVERED
HR role operator overridepresent
0 mentions		COVERED
Nested group subgroup usersetspresent
0 mentions		COVERED
Write authority no self escalationpresent
0 mentions		COVERED
Multi tenant wall live apppresent
0 mentions		COVERED
Bounded check with cycle terminationpresent
0 mentions		COVERED
Field level attribute maskingpresent
0 mentions		COVERED
Capability path prefix ACLpresent
0 mentions		COVERED
Deny-by-default tombstone revocationpresent
0 mentions		COVERED
Admin authored schema languageabsent
0 mentions		dormant
Reverse index list objectsabsent
0 mentions		dormant
Userset rewrites computed relationspresent
0 mentions		COVERED

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