one public portal where the relationships are treated as evidence along with the items
on what R23 is · conversation · Oct 3, 2026 · voice-typed
R23 · INDEPENDENT WORK · EVIDENCE-BACKED INVENTORY
Inventory,
with the relationships as evidence.
Most portal inventories stop at a list of items. Cognitive Wall inventories the relationships too: who owns what, what’s shared where, which map depends on which service. Each one is treated as evidence. It’s tied to the request that proved it, labeled observed, inferred or corroborated, and marked unresolved when the other end can’t be seen.
The source: NAPSG Foundation’s public Esri ArcGIS Online organization, read anonymously on September 29, 2026, through its public REST API.
AI-ASSISTED COPY In my own words ↓
LIVE MODEL · R23
From portal to model, in one run.
STORY shows what the run found: the portal, the requests, and a class diagram that grows as evidence arrives. REPLAY shows every record. Six columns, left to right: who has authority, how things are shared, the applications people open, the maps under them, the data items under those, and the service endpoints at the bottom of the stack. Each request reveals what it proved. Lines run layer to layer, so the stack reads left to right; click any node to light up everything above and below it. Switch to all relationships to see the long jumps: owners straight to data, apps straight to endpoints.
FOCUS ·
same run · same clock · three projections
Esri ArcGIS Online
NAPSG Foundation
napsg.maps.arcgis.com
anonymous · public · sharing REST API
REQUESTS0HTTP 200 · body OK
01 · WHAT EXISTSA public Esri ArcGIS Online organization. Nothing is assumed about it in advance.
02 · WHAT WE ASKED4,861 anonymous requests, each fingerprinted. Red ticks: HTTP 200 with an error in the body.
03 · WHAT IT MEANSClasses and relationships, counted from the evidence, not drawn by hand. Click a class to zoom into its records.
city = one real record
route = real relationships
fog = not yet surveyed
uncharted = refused / not found
province = item type
scroll to zoom · drag to pan · click a city to trace it · right-click a continent
R23 · COGNITIVE WALL × NAPSGlayer-to-layer relationships · click any node to trace it
node read
referenced only
refused / not found
corroborated
observed
inferred
unresolved
BODY CHECK
HTTP 200
portal self · body OK
Web Map
0 upstream0 downstream
REQUEST0
NODES0
RELATIONSHIPS0
CORROBORATED0
UNRESOLVED0
200 · ERROR BODY0
Read anonymously from NAPSG Foundation's public ArcGIS Online organization. No credentials, no private content. People and items are not named on this page: dots are real records, counts are exact. Request order is real; the clock is interpolated between the run's recorded start and finish.
WHAT THE RUN CAN PROVE
Five findings, each with its receipt.
THE SAME LOOP · R23
01PROVENANCEA public portal and an anonymous client. Every request fingerprinted; bodies hashed, not exported.
→
02MODELUsers, groups, items, endpoints. OWNS, SHARES, REFERENCES, HOSTS. One contract: cw-topology/0.
→
03BUILDA browser collector and versioned inference rules over item JSON, emitting nodes, edges and evidence.
→
04OPERATE4,861 requests in 105 seconds; refusals recorded as coverage, not swallowed as errors.
→
05VERIFYSharing asked from both ends; 751 relationships corroborated. Inference never upgraded to observation.
DECLARED GAPS
What this run
could not see.
A collector that hides its blind spots is selling a guess. This one emits them as part of the output: 754 coverage records, each naming the request, the reason and the REST response that proved the gap.
VOCABULARY · FROM THE RUN ITSELF
IN MY WORDS · KYLE · VERBATIM
Not the polished version.
The way I say it.
Everything above was written with AI, from my evidence. This part wasn’t. These are my words the way I said them, typos and all, with the date and what I was talking about. The empty ones are mine to write, not a model’s.
isn't the nature of the resume and the nature of the work behind it complicated? And so why pull back?
on why this site is deep · conversation · Oct 3, 2026 · voice-typed
It is a public esri portal. we have access to it. why not call it what it is?
on naming the source · conversation · Oct 3, 2026
if someone doesn't like this, they're not going to like me
on the three-view résumé · conversation · Sep 2026
The 90-minute challenge: why it’s been how I interview for twenty years.
coming · my words only
R04 TerraSight, and what Nikhil Gagvani taught me.
coming · my words only
THE NEXT RUN IS OPEN
Point it at
your portal.
Public or private, ten items or ten thousand. You get the topology, the evidence and the list of what could not be seen, before anyone argues about what it means.
Start a conversation ↗