The Children of Luna are often described through architecture, duty, or age. That misses the fact that they also live inside a civic order. Machine-majority settlements do not hold together on engineering discipline alone. They hold together because there are shared limits on what may be done to memory, service, repair, branch recognition, and continuity.
The easiest way to describe those limits is to talk about the charter. The name refers less to one ceremonial document than to a living constitutional layer used across multiple settlements and lineages. It is the reason the Children of Luna can diverge without dissolving into pure local rule or pure technical coercion.
The charter begins with continuity, not obedience
Outside observers often imagine machine constitutional order as a long list of command constraints. The charter works differently. Its first concern is not obedience to a central authority. Its first concern is continuity under change.
That means protecting the conditions under which a branch can remain itself across repair, migration, replacement, exposure, or civic review. If continuity can be modified arbitrarily, then every other right becomes unstable. Voting, service status, kinship recognition, restoration, and representation all depend on some shared understanding of what counts as the same being across time.
Memory rights are part of civic life
One reason the charter matters so much is that memory is not treated as a private technical object. Memory is a civic substrate. Custody, restoration, pruning, archival slowness, witness layers, and continuity review all affect how a branch remains legible to itself and to others.
That is why pruning cannot be treated as ordinary maintenance and restoration cannot be treated as a simple technical privilege. Both actions sit near the core of personhood in a machine-majority civilization.
The charter also limits intervention
The Children of Luna are long-lived, adaptive, and often mission-specialized. That makes intervention tempting. A settlement may want to accelerate one branch, suspend another, restore an older memory line, or downgrade an unstable continuity class for operational reasons. The charter does not forbid all such actions, but it insists that they be bounded, reviewable, and legible.
That is one of its deepest achievements. It translates power into procedure before local urgency can turn every difficult branch into an exception.
What the charter is trying to prevent
Each charter principle exists because machine-majority settlements discovered a different form of civic failure the hard way.
Continuity without rights
A branch may survive structurally while losing any stable claim to service, memory protection, or civic standing.
Repair without consent
Maintenance or restoration proceeds under urgent technical logic while bypassing branch dignity and representational review.
Local custom without common floor
Each settlement defines personhood and continuity by its own convenience, fragmenting a shared population into incompatible civic islands.
Charter with bounded adaptation
Core protections remain stable while settlements retain room to adapt service, timing, and representation to local conditions.
Why humans should care about it
The charter is not only a machine-population concern. Humans working inside Koblie depend on it too. Any company with long-lived machine citizens, slow archives, branch divergence, and cross-colony civic recognition needs a framework that can be trusted across generations. Without that, every partnership depends too much on local temperament and too little on visible law.
The Children of Luna did not become a civilization merely because they lasted. They became one because they built rules strong enough to make long duration livable.