> 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.md).

# The Split

Capital markets, digital assets and real-world spending have never shared a ledger — not for lack of pipes, but for lack of a common language of value.

> Same value. Three languages that were never designed to meet.

A position in a brokerage account, a token in a wallet and a real cross-border payment are all value. Nobody disputes that. What is harder to see is that they have never once sat on the same ledger. Each lives in a system with its own clock, its own unit of account and its own border, and the three systems were built without any expectation of meeting.

The usual way to say this is that capital markets, digital assets and real-world spending have long been independent of one another. That is true, and it explains nothing. Independence is the outcome. If the cause were simply that nobody had laid a pipe between them, the problem would have been solved long ago, because there is no shortage of pipes. Chains are bridged to chains. On-chain balances are spent through cards. Real-world assets are registered as tokens. The three markets remain as separate as before.

## The cause is a missing language

Look at what each market means by value and the separation stops being a mystery.

In capital markets, value means ownership and a claim on future cash flow. It moves on a quarterly rhythm, settles on a lag, and stops at the edge of a jurisdiction. In digital assets, value means liquidity and composability. It moves every hour of every day, settles in seconds and recognizes no border — but it has almost no way to act on anything outside itself. In real-world spending, value means the right to use something: an itinerary on a given date, a table on a given evening, a good that arrives. It is measured in time, place and availability, and it ends where a supplier's inventory ends.

Three definitions of value. Three clocks. Three borders. None of them is wrong, and none of them can be read by the other two. That is why the markets are split: not because nobody connected them, but because they do not share a language in which a connection could be expressed. A pipe between two of them carries the value across and leaves its meaning behind, and someone — always a person — has to supply the meaning again on the far side.

## Why this matters now

For as long as software could only move value, that arrangement was tolerable. Moving value was the hard part, and the translation at each end was a cost that people absorbed without naming it. Software can now read what a request means. The moment it could, the cost stopped being invisible, and the split stopped being a fact of life and became a problem with a shape.

This Part describes that shape. It proposes nothing. It explains the name this paper is written under, sets out the three languages, follows one ordinary request across all of them, and examines what each existing solution has actually solved. The proposal begins in Part II.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Why NEXON</strong></td><td>A tie that exists in its own right, witnessed in public, switched on. What the name fixes before anything is built.</td><td><a href="/nexon-docs/part-i-the-problem/01-the-split/why-nexon.md">Why NEXON</a></td></tr><tr><td><strong>Three Value Languages</strong></td><td>Ownership, liquidity, right of use. Three grammars side by side, and one cross-border payment that still takes a week.</td><td><a href="/nexon-docs/part-i-the-problem/01-the-split/three-value-languages.md">Three Value Languages</a></td></tr><tr><td><strong>Why Bridges Failed</strong></td><td>Bridges, stablecoin rails and tokenization each solved something real. What every one of them leaves out.</td><td><a href="/nexon-docs/part-i-the-problem/01-the-split/why-bridges-failed.md">Why Bridges Failed</a></td></tr></tbody></table>

Everything that follows in this paper is an attempt to justify one sentence, and it is worth stating before a single mechanism has been described.

This is the opening problem in the NEXON thesis: capital may create value, digital networks may move it, and consumer markets may realize it, but the user still experiences three separate worlds. A new-generation value connection network starts by preserving those differences, then making the transitions explicit.

**Three markets. One language.**

*Spine:* [*The Translator*](/nexon-docs/part-ii-the-connection-thesis/02-the-translator.md) *· Next:* [*Why NEXON*](/nexon-docs/part-i-the-problem/01-the-split/why-nexon.md)

*Turning what you mean into what gets settled.*


---

# 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.md?ask=<question>&goal=<endgoal>
```

`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.
