> For the complete documentation index, see [llms.txt](https://nexon-3.gitbook.io/nexon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nexon-3.gitbook.io/nexon-docs/part-i-the-problem/01-the-split/three-value-languages.md).
# Three Value Languages
Ownership, liquidity, right of use: three languages of value with no shared grammar — and one cross-border payment that still takes four systems and a week.
The previous section made a claim: the three markets are short of a language, not of pipes. This section puts the three languages side by side, and then follows one ordinary request through all of them, the way it has to travel today.
## Three markets, three grammars
| Market | Its language of value | Rhythm | Boundary |
| ---------------------------------------------- | ------------------------------ | -------------------------------------------------------- | ------------------------------------------------------------------------ |
| Capital markets (equities) | Ownership and future cash flow | Quarterly cadence; T+2 settlement; limited trading hours | Bounded by jurisdiction |
| Digital assets | Liquidity and composability | 7×24; finality in seconds | Borderless, but with almost no executable interface to real-world assets |
| Real-world spending (travel / hotels / retail) | Right of use and experience | Measured in "a given time, a given place, usable" | Bounded by supplier and inventory |
The settlement cycle, the unit of account, the definition of a boundary and the degree of composability all differ across the three. They are not short of connection. What they are short of is a common language.
```mermaid
flowchart LR
subgraph G["No shared grammar"]
direction LR
C["Capital markets
ownership · future cash flow
quarterly · T+2 · by jurisdiction"]
D["Digital assets
liquidity · composability
7×24 · seconds · borderless"]
R["Real-world spending
right of use · experience
time · place · availability"]
end
classDef anchor fill:#047854,stroke:#047854,stroke-width:1.5px,color:#F5F3F0
classDef engine fill:#8B5CF6,stroke:#8B5CF6,stroke-width:1.5px,color:#F5F3F0
classDef solid fill:#F5F3F0,stroke:#141414,stroke-width:1.2px,color:#141414
classDef ghost fill:#F5F3F0,stroke:#059669,stroke-width:1.2px,stroke-dasharray:4 3,color:#141414
class C,D,R solid
```
{% tabs %}
{% tab title="Capital markets" %}
Value here is a claim: on a share of ownership, and on the cash that ownership is expected to produce. The claim is real and durable, and it is slow. Prices update by the second, but positions settle on a lag, markets close overnight and at weekends, and the claim itself is enforceable only inside the jurisdiction that recognizes it. Nothing in this grammar has a word for "usable tonight."
{% endtab %}
{% tab title="Digital assets" %}
Value here is liquidity: how quickly and how cheaply one position can become another, and how freely it can be combined with others. The grammar is fast and borderless, and it is closed. Every verb it has acts on other digital assets. It can say "swap" and "transfer" in a thousand ways, and has almost no way to say "book," "deliver" or "own a share of."
{% endtab %}
{% tab title="Real-world spending" %}
Value here is the right to use something: an itinerary for the day you arrive, a table at eight, a parcel at your door. It is measured in time, place and availability, and it lives in a supplier's inventory system, the only place it can be confirmed. This grammar has no word for a position or a token. It recognizes money already turned into money it accepts, and a person who has proved who they are.
{% endtab %}
{% endtabs %}
Read the three tabs again and notice that none of them is describing the same thing. A claim, a rate of exchange and a right of use are not three prices for one object. They are three objects, each of which the other two grammars cannot even name.
## One position, one cross-border payment
You hold a position in an equities account and want to turn part of what it earned into money you can actually spend in another country. Today, the request travels like this.
{% stepper %}
{% step %}
### Sell
T+2 settlement. The position becomes cash — cash you cannot yet touch.
{% endstep %}
{% step %}
### Withdraw to a bank
1–3 business days, longer cross-border. A second system, a second identity check.
{% endstep %}
{% step %}
### Convert the currency
Spread + fees. A third system, a third set of credentials.
{% endstep %}
{% step %}
### Book on a travel site
The fourth identity check. Only here can the value finally be spent.
{% endstep %}
{% endstepper %}
Four systems, four sets of credentials, four identity checks, five to seven business days. If any link in the chain fails, a human steps in and starts over.
Sell. Wait for settlement. Wire it out. Convert the currency. Then start over on a travel site. Nothing here is technically hard. It's just that at every single step, a human is translating.
And what is actually consumed on this path is not the fees. It is you — at every step, you are the one manually translating one language of value into another. This is not a technical problem. It is a translation problem.
> Turning a position into money you can spend still takes four systems, four identity checks and a week. Every step is a human manually translating one language into another. That was tolerable when software could only move value. It stopped being tolerable the moment software could understand it.
The next section looks at the solutions that already exist along this path and asks, of each one, which part of the translation it actually performed.
*Spine:* [*The Translator*](/nexon-docs/part-ii-the-connection-thesis/02-the-translator.md) *· Next:* [*Why Bridges Failed*](/nexon-docs/part-i-the-problem/01-the-split/why-bridges-failed.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://nexon-3.gitbook.io/nexon-docs/part-i-the-problem/01-the-split/three-value-languages.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.