Leumas API
One backend kernel serving every role This page lists everything the Leumas graph records about how it relates to the rest of the system.
What Leumas API is
One backend kernel serving every role It is recorded in the Leumas graph as a core in the architecture grain.
What Leumas API relates to
The graph records 62 relationships for it, across 4 kinds. It contains Game Server, Games adapter and Institution adapter, and 10 more.
What it depends on, and what depends on it
Leumas API depends on Identity & trust, Data & schemas, AI & agents, Devices & fabric and Automation, and 5 more. It is used by Leumas Studio, Leumas Admin, Leumas Web, Leumas iOS and Leumas Docs, and 33 more.
Why it is shaped this way
@notes/api.md
How to read this
Every relationship here is one of nine shared kinds, mapped from the source graph rather than invented. A kind that a source uses and this model does not express is dropped and counted rather than turned into "related to", so what you see understates the source rather than embellishing it.
- Contains: Game Server, Games adapter, Institution adapter, Value Resolver, Body engine and Artwork, and 7 more.
- Part of: Leumas.
- Depends on: Identity & trust, Data & schemas, AI & agents, Devices & fabric, Automation and React kits, and 4 more.
- Used by: Leumas Studio, Leumas Admin, Leumas Web, Leumas iOS, Leumas Docs and Imperium, and 32 more.
Questions
What does Leumas API depend on?
Identity & trust, Data & schemas, AI & agents, Devices & fabric, Automation and React kits, and 4 more.
What uses Leumas API?
Leumas Studio, Leumas Admin, Leumas Web, Leumas iOS, Leumas Docs and Imperium, and 32 more.