Constraints are contracts

Humanity’s First Agreement

One hundred thousand years ago, someone pointed a finger at something and made a sound. Another person who heard that sound pictured the same thing.

This was the beginning of language.

An agreement to call “that thing over there” a lion. Without this agreement, two people share the same world yet see different ones. With it, one person’s experience can be transmitted to another.

Language is humanity’s first contract.


Writing Is a Contract Across Time

Five thousand years ago, someone in Mesopotamia pressed wedge-shaped marks into wet clay. The purpose was to record grain inventories.

Spoken words vanish; records remain. When records remain, bureaucracy becomes possible, law becomes possible, the state becomes possible.

Writing is a device that carries today’s agreements into the future. For a contract made today to remain valid tomorrow, writing is necessary.

Speech created the tribe. Writing created the nation.


Rule of Law: Agreements Written in Blood

Human society is a problem of density.

In a tribe of 150, everyone knows each other’s faces. When someone breaks an agreement, everyone knows. Social pressure alone maintains order.

In a city of ten thousand, faces are unknown. When someone breaks an agreement, no one finds out. Social pressure stops working.

That is why law became necessary.

Law is the documentation of agreements. “If you do this, these consequences follow.” Everyone is subject to the same rules. Rules can be mechanically verified. Violations are defined. Violations carry consequences.

It took thousands of years for this system to work. Revolution, war, massacre, compromise. Humanity wrote these agreements in blood.

The result: eight billion humans coexist on a single planet. Not perfectly. But it works. Without rule of law, this density would have been impossible.


Three Conditions for Rule of Law

Rule of law works not because the law is clever, but because it satisfies three conditions.

1. It is verifiable. Whether the law was broken can be determined. Not by a judge’s intuition, but by statute and evidence. The procedure for determination is defined.

2. Violations are defined. What is permitted and what is forbidden is explicit. Not “don’t do bad things” but “do not engage in the conduct specified in Article 50, Paragraph 1.” It is discrete. Either a violation or not.

3. It can be enforced. Violations carry consequences. An agreement without consequences is not an agreement — it is a wish.

These three conditions are remarkably universal.


Same Pattern, Different Domains

DomainAgreementVerificationViolation definedEnforcement
Human societyLegislationTrialStatutory textPunishment / damages
ProgrammingType systemCompilerType errorCompile rejection
Code formattinggofmtgofmt -dFormat mismatchCI failure
Code structurefilefuncvalidate22-rule violationERROR
Knowledge representationGEUL specmechanical verificationSpec mismatchContext entry denied

Every system that works has agreements. Agreements are verifiable, have defined violations, and can be enforced.

A system without this is — chaos.


LLM Has No Agreements

In 2026, if you tell an AI coding agent to “improve the code,” the agent changes something.

But:

  • When is it done? Unknown.
  • Is the result sufficient? No criterion exists.
  • Run it again — is the result the same? No.

This is like a society without law. Each party acts on its own judgment, there is no standard for outcomes, and results differ every time.

“Code quality” is a spectrum. A spectrum has no termination condition. Without a termination condition, convergence is not guaranteed.

This is rule by persons. It depends on a wise king — a smart model. When the king is wise it goes well; when not, it doesn’t.


Constraints Converge

filefunc defines 22 agreements.

One file, one function. Depth no greater than 2. Annotations required. Control flow is one of sequence, selection, or iteration.

These agreements are:

  • Verifiable. filefunc validate determines compliance mechanically. No LLM required.
  • Violations are defined. ERROR or pass. Not a spectrum.
  • Enforceable. Code must be revised until the ERROR count reaches 0.

When these three conditions are satisfied, an LLM can converge any codebase into a state where agreements are kept with nothing more than a while ERROR > 0: fix loop.

The LLM’s role is not that of a judge. It is that of an executor. What constitutes a violation is declared by the agreement (validate). Whether a violation has been resolved is also declared by the agreement (validate). The LLM only fixes violations that the agreement has identified.

Not the king, but the law, rules. This is rule of law.


The Golden Ratio of Chaos and Order

Without agreements there is chaos. Code has no structure, functions are tangled, depth grows without limit. AI agents read everything each time and produce different results each time.

With too many agreements there is oppression. When everything is prescribed, flexibility disappears. Forcing a ten-line annotation onto a three-line function inverts means and ends.

filefunc’s 22 rules found the space between. Constrained enough, but not excessive.

The evidence: 1,275 functions converge to three control structures. Sequence, selection, iteration — the three structures Böhm and Jacopini proved sufficient in 1966. That 22 agreements converge to a mathematical classification is evidence that the agreements are neither too many nor too few.

Neither chaos nor oppression. Sufficient order within sufficient freedom. This is the golden ratio.


The Third Language

Speech created the tribe. An agreement between human and human. Writing created the nation. An agreement between present and future.

What will the third language create?

GEUL is an agreement between AI and AI. And a verifiable agreement between AI and human.

SIDX is an agreement of meaning. The same bit pattern carries the same meaning. The 16-bit stream is an agreement of form. Network, storage, and AI share the same unit. Source, confidence, and time are agreements of trust. Metadata is embedded in structure; omission is impossible. Mechanical verification is the enforcement of agreements. Information that violates the spec cannot enter the context.

In natural language there is no concept of an “invalid sentence.” In GEUL there is. The fact that invalidity is defined is evidence that an agreement exists.


Proving It in Code First

The same principle applies to both code and knowledge.

But code comes first.

Code has a compiler. It has an AST. It has a type system. The boundary between “valid code” and “invalid code” already exists. Adding 22 agreements on top of this is natural.

Natural-language knowledge has no such foundation. The very concept of a “valid sentence” does not exist. GEUL must build this foundation from scratch.

Prove it where it is easy, then expand to where it is hard. filefunc proves it in code; GEUL extends it to knowledge.

This is engineering.


A Reminder to Humanity

The problem is simple.

We have already invented rule of law. It is an agreement written in blood. Thanks to that agreement, eight billion humans coexist despite this extraordinary density.

LLMs are no different.

Rational constraints are agreements. Agreements are what allow chaos and order to achieve their golden ratio. When agreements are verifiable, violations are defined, and enforcement is possible, any system converges.

As human society did. As code did. As knowledge will.

No new invention is needed. It is a matter of applying what has already been invented to a new domain.

Design the agreement. Then it converges.