The architecture graph

Every product, service, engine, domain and revenue stream Leumas runs, and the ownership, dependency and governance edges between them — the same graph the control plane draws.

What the edges mean

Four relationships appear here and each maps onto one shared kind: owns becomes contains, consumes becomes depends on, governs becomes depends on, and exposes becomes flows to. That mapping is what lets a question about this graph and a question about anatomy be answered by the same code.

Why this grain is published and the others are not

This graph is ours, written by hand, and licence-clean, so publishing it costs nothing and answers a real developer question. The other three each have a reason not to be here, and /datasets states each one rather than leaving a gap for you to guess at.

One model, two doors

The control plane draws this same graph for operators of an install. This is its public face. They read one model rather than two, which is why the two can never disagree about what the ecosystem contains.

Questions

Is this the whole system?

It is every unit that has been registered in the graph. A node that exists in code and was never registered is missing here, which is a gap in the registration rather than in the system — and it is the reason registration is part of adding a unit.