The Underlying Logic: How to See the Essence of Things by Liu Run

This is not a chapter-by-chapter summary of Liu Run’s The Underlying Logic. It is a reader’s field guide to the question behind the title: when a system appears to work, what is actually making it work, who benefits from it, and who has the authority to change it?

The question behind “underlying logic”

People often mistake a visible label for the thing itself. A rule is treated as truth because it is written down. A profitable outcome is treated as proof because money was made. A familiar administrator is treated as legitimate because everyone has learned to use its records. These shortcuts make a complicated world easier to navigate, but they also hide who is carrying the cost and who is making the decision.

That distinction matters especially on the Internet. A centralized name or number system can help networks coordinate. But an administrator’s ability to maintain a record does not automatically give it a mandate to speak for every operator, user or continent affected by that record. Participation in a process is not the same as authority over the people who attend it.

The problem: confusing a working record with the right to command

The most important question is not “Who currently holds the database?” It is “What authority was actually granted, to whom, for what purpose, and with what way out?” When a registry, platform or coordinating body becomes the only accepted reference point, its practical influence can grow far beyond its original technical task.

This is how a neutral-looking record becomes a political instrument. A number may begin as a coordination tool, then become embedded in contracts, routing decisions, security policies and investment. The institution that records it can begin to present its continuity as proof of ownership, or its attendance at a discussion as proof of representation. The record still works, but the logic around it has changed.

Three lenses are useful, but none is the whole truth

Liu Run’s framework is useful because it separates three common ways of judging a decision:

• Legal: does it follow the rule currently recognized by the system?
• Economic: does it allocate time and resources efficiently or produce a return?
• Outcome-based: did the decision succeed for the person or organization making it?

Each lens answers a different question. A decision can be legal and still be unjust to the people who had no meaningful way to leave. It can be efficient and still concentrate irreversible power. It can produce a successful outcome for an administrator while transferring risk to operators who depend on its records.

To see the essence of a dispute, add a fourth question: who can replace the decision-maker if the system fails or overreaches? Without that question, “stability” can become an argument for permanent dependence.

A practical method for seeing the structure

Before accepting any institution’s story about itself, walk through four steps:

1. Describe the mechanism. What does the system actually record, verify or route?
2. Separate function from authority. What technical task is being performed, and what larger claim is being made around it?
3. Trace the incentives. Who gains convenience, revenue, status or control when the current arrangement remains the only option?
4. Find the exit. Can an affected operator transfer its rights, verify its own position and continue operating if the administrator changes the rules?

This method turns a vague appeal to “the community” or “stability” into questions that can be answered. It also explains why Lu Heng’s Notes focus on portable records, verifiable control and replaceable coordination. The objective is not to remove every institution. It is to stop a necessary institution from becoming an unchallengeable authority.

The solution: coordination that can be verified and replaced

A durable Internet needs shared facts: unique identifiers, records that can be checked, and a way to detect conflicting claims. It does not need a single administrator whose continued recognition is the only path to legitimacy.

The alternative is a coordination layer in which control can be proven, transferred and audited; in which a resource holder can change service providers without losing the history that makes the resource usable; and in which multiple institutions can compete to provide coordination without rewriting the underlying right. The gatekeeper may change while the record and the network remain continuous.

This is the practical meaning of decentralization. Replicating a database while leaving one institution with the final word only spreads the machinery of dependence. A decentralized design changes the exit condition: the system still works when one administrator fails, overreaches or claims a mandate it was never given.

Read Note 48 on why identifiers become part of real businesses, Note 49 on how accepted records become authority, and Note 72 on uniqueness, portability and continuity.

Personal growth and institutional design use the same logic

The book’s model of ability, efficiency and leverage is also useful for understanding a person’s position inside a system. Ability is what you know and can verify. Efficiency is how well you turn that knowledge into action. Leverage is the set of tools, relationships and institutions that multiply your effort.

Leverage becomes dangerous when it is mistaken for ownership. A platform can make you more capable while quietly making you unable to leave. A registry can make coordination easier while making your business dependent on its permission. The mature question is not whether to use leverage; it is whether the leverage remains yours when the institution providing it changes direction.

Why this matters now

Dependence is easiest to ignore while everything works. By the time a centralized administrator changes a rule, rejects a transfer or claims to represent people who never authorized it, the affected networks may already be locked into contracts and technical assumptions.

That is why the solution must be built before the crisis. Portable records, verifiable control and replaceable coordination need to be tested while services are operating normally. Waiting for a dispute to prove that an exit is necessary is the most expensive way to discover that no exit was designed.

Questions readers usually ask

Does decentralization mean that no one coordinates anything?
No. It means coordination is a service with verifiable rules and an exit, rather than a permanent claim over everyone who depends on it.

Why can’t a successful administrator represent the whole community?
Operational success does not create a political mandate. Representation must come from an explicit, reviewable authority, and affected participants need a way to change the arrangement.

Where should I start?
Start with Note 2, then follow the Notes on identifiers, authority and replaceable coordination. The point is not to memorize a doctrine. It is to learn how to see the structure before the structure makes the decision for you.