M · Markets
Tech resale/scrap · automated arbitrage · prediction-market research This page lists everything the Leumas graph records about how it relates to the rest of the system.
What M · Markets is
Tech resale/scrap · automated arbitrage · prediction-market research It is recorded in the Leumas graph as a revenue in the architecture grain.
What M · Markets relates to
The graph records 4 relationships for it, across 2 kinds. It contains M · Tech resale and scrap, M · Automated arbitrage and M · Prediction markets.
What it depends on, and what depends on it
Nothing is recorded as a dependency of M · Markets. Nothing is recorded as depending on it, which for a leaf is normal and for a shared unit is worth checking.
Why it is shaped this way
Admin-led market operations cover resale, arbitrage, and prediction research. Studio may collect and model data, but Admin controls capital limits, jurisdictions, approvals, reconciliation, and execution authority.
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: M · Tech resale and scrap, M · Automated arbitrage and M · Prediction markets.
- Part of: Accounts.
Questions
What does M · Markets depend on?
This graph records no dependencies for M · Markets.
What uses M · Markets?
Nothing in this graph is recorded as depending on M · Markets.