The constellation above lives in GIGI as data. Every node
becomes one record — 72 in total, 24 per community — and every
edge becomes a relation between two records. Each node record carries
five fields: id, community (A, B, or C),
degree (how many neighbors it currently has),
x_spec (its coordinate along the graph’s second-quietest
vibration), and bridge_incident (0 = interior, 1 = touches a
cross-community edge).
Because GIGI is a fiber-bundle database, the bundle’s
curvature (κ) and the connectivity gap ride along with every read
— no sidecar service to compute them. When you drag the slider or
hit "Cut every bridge", the layout below is recomputed from the graph
itself, and the readout on the right shows the same connectivity number
the engine’s SPECTRAL verb returns for any live bundle.
Levers & receipts
The number the engine’s SPECTRAL verb reports — how loud that second-quietest hum is, the spectral gap λ₁ — is a connectivity thermometer. λ₁ near zero means "this bundle’s relation graph is about to disconnect" — communities that barely talk — and the same hums that detect it turn out to be good coordinates for seeing it, which is the whole idea of drawing a graph at its own spectral embedding. Watch the moment you drag to one bridge per pair: the rooms
are already visibly separate while λ₁ is still nonzero. The spectrum hears the
wall before the wall is finished.
The same thing in GQL — run it against an engine
Point at the public read-only instance (no key needed) or your own
engine (start with GIGI_CORS_ORIGIN=* — dev only). SPECTRAL
rides along on any bundle; the tetmesh bundle is live right now.
—