A fictional company, fully modelled.
Open it and look for yourself.

Start from a name you already know. Every typed node is indexed, and the results come back typed — so two things that share a name arrive as two different kinds of thing, not as one ambiguous hit.

Fig. 1.1

Type into the search box, and see how rich the result already is.

Fig. 1.2

Click the information icon to expand a result.

Fig. 1.3

Click the result you want, and the node page opens.

Open any node and walk out from it. The plexus shows the shape of what surrounds it before you read a single field — how much is attached, in which directions, and where it thins out.

Open a node and a plexus icon appears in its header. That is the way into the graph, centred on the node you were reading.

Fig. 2.1

Fig. 2.2

Click a node in the plexus and its information drawer opens.

Then try the plexus in 3D, and move the camera yourself.

Navigation

DragRotate cameraScrollZoom in/outShift+ScrollPan verticalCtrl+ScrollPan horizontalClick nodeSelect

Whatever has a place on Earth is on one: a person, a work centre, a supplier, a sales territory. The same nodes, read by geography instead of by relationship.

Open a node that carries geographic data — or whose related nodes do — and a globe icon appears in its header. That is the way into the map explorer.

Fig. 3.1

Fig. 3.2

Click a pin and the same information drawer opens, on the same node.

Ask in plain language. It translates the question into a traversal, runs it, and reports the path it walked. Every answer comes back with that path — so if you disagree with one, you disagree with an edge, which is a different kind of argument than disagreeing with a paragraph.

If a blank box is its own kind of wall, start anywhere: if a supplier fails today, which customers are affected; which critical tasks rest on a single person; what happens to purchasing when one buyer leaves; who can actually run an operation rather than who is certified for it. Then ask the one you actually came for.

Fig. 4.1

Ask which objects a report needs, then ask who can explain them. The answer names the people, by role.

Fig. 4.2

Ask what one person's departure would reach. Same model, a different traversal.

Switch the language and watch what happens. It is not only the interface that changes: the metamodel's own vocabulary — the type names, the categories, the lifecycle statuses — is translated with it, so the model reads natively to whoever is reading it. Twenty languages are available.

Fig. 6.1

Pick another language, then go back to any node you have already read.