Next API route inventory
no collectorowner · chat app
A route added after this fixture was written is not in the map, and a missing edge here is a scope boundary rather than a clean result.
Linked surfaces: Next API routes, Chat app (Next.js)
Exposure · declared surface
Most security products open on a map that looks measured. This one starts by naming the difference: every node and edge is a declaration authored for this prototype, and the surfaces the register cannot account for are listed beside the map rather than omitted from it. The gap register is the honest half of an inventory.
Reading rule
A declaration map, not an observation map. An edge means a manifest says one component calls another; no traffic was captured. A missing edge is not evidence of absence.
Nodes
13
Hand-placed fixture surfaces
Declared edges
14
What a manifest says calls what
Unregistered
4
Nodes and edges with no register entry
Gaps
6
Each with an owner and a consequence
Declared surface · select a node
Straight lines join declared callers to declared callees; they are not routed and carry no arrow, so read the detail panel for the declared direction of a call.
Selection
Select a node to see what the register declares about it.
6 gaps · what the map cannot see
Every gap names an owner and the consequence of the missing entry. A gap is not a finding about a control; it is a statement that this register has no account of the surface — and a missing edge is a scope boundary, not a clean result.
owner · chat app
A route added after this fixture was written is not in the map, and a missing edge here is a scope boundary rather than a clean result.
Linked surfaces: Next API routes, Chat app (Next.js)
owner · backend
The register declares intended calls; it records no request, latency or error, so it cannot witness that any edge runs.
Linked surfaces: PolyBackend, Postgres
owner · backend / device auth
A paired device can hold a grant this map does not list; absence from the register is not absence of the grant.
Linked surfaces: Terminal device grants
owner · agent platform
Server names and tool scopes are authored fixtures; a server configured after the fixture was written would not appear here.
Linked surfaces: MCP servers, Stored agents
owner · O09
Company incident handling, identity administration and SOC telemetry belong to O09; this lab refuses to imply it sees them.
Linked surfaces: Cloud providers, Postgres
owner · chat app
What a browser store contains is outside this lab; the map declares that a write path exists, not what it writes.
Linked surfaces: Research IndexedDB, Office store
What this space refuses
This space is not a live asset inventory, and nothing on it is discovered, probed or scanned. It makes no attack-path or exploitability claim: an edge means a manifest says one component calls another, not that anyone did. It is not a traffic capture — no request was recorded to draw it. And it is not a completeness claim: a missing edge is a line in the gap register, never evidence of absence.