Root Legitimacy for Machine-Executable Institutional Authority

Draft — pre-specification. Companion to Paper 5, "Bounded Contextual Authority." Not NOMOS-SPEC-007.

Abstract

NOMOS provides mechanisms for making institutional authority machine-executable and independently verifiable. Its existing trust primitives include cryptographic sealing, third-party attestations, artifact revocation, and chain-of-trust key certificates (published as NOMOS-SPEC-007, Draft). These mechanisms, however, share an assumption: the relying system already has a reason to trust the root key against which an authority chain is evaluated. That assumption exposes a deeper problem: who, or what, gives a machine reason to recognize a root of institutional authority in the first place? This is not simply a cryptographic question. It is a question of institutional legitimacy.

A conventional PKI hierarchy establishes trust in identities through certificate authorities and root programs. Machine-executable institutional authority introduces a different claim: not merely that a key belongs to an organization, but that the organization has standing to issue or represent a particular form of authority.

This note explores a candidate governance model built around four mechanisms: threshold-controlled roots rather than a single signing authority; mandatory time limits and periodic re-legitimation; public transparency records with independent observation; and multiple sector- and jurisdiction-scoped roots rather than one universal root. The proposal is deliberately red-teamed against existing trust systems, including web PKI, DNSSEC, RPKI, Certificate Transparency, accreditation, professional licensing, treaty recognition, and federated trust.

The result is not a finished trust architecture. Several elements survive as promising mechanisms for reducing unilateral control and increasing auditability. Others do not survive intact. In particular, threshold signing does not solve the initial bootstrapping problem; mandatory expiry introduces renewal and availability risks; transparency does not automatically provide effective split-view protection; and sector-scoped roots create difficult boundary and recognition problems. The resulting recommendation is deliberately narrower: define the reusable technical primitives, run a constrained institutional experiment, measure what fails, and only then consider standardization.

1. The Problem

Institutional authority is increasingly being consumed by software. Policies, regulations, procedures, contracts, licenses, permissions, and organizational rules increasingly influence automated decisions and autonomous systems. NOMOS addresses one part of this problem by representing institutional authority as a machine-executable artifact that can be cryptographically sealed and independently verified. But portability creates another question.

Suppose an agent arrives at a system operated by an institution that has never interacted with the agent before. The agent presents a .nomos authority artifact, a cryptographic signature, and a chain showing which keys authorized the signing key. The receiving system can verify the mathematics. But eventually it reaches the top of the chain. It needs to answer:

Why should I recognize this root?

NOMOS-SPEC-007 (Draft) deliberately leaves that question to the relying party. The verifier requires a root public key to be supplied explicitly. There is no default root and no assumption that NOMOS itself is the universal trust anchor. That is useful technically, but it exposes the deeper governance problem. The question is no longer:

Can this signature be verified?

It is:

Who has legitimate standing to establish the authority that the signature represents?

That distinction matters. A cryptographic system can prove that a particular key signed a statement. It cannot, by cryptography alone, prove that the institution controlling that key legitimately possesses the authority it claims. The latter is an institutional question.

2. Why Conventional PKI Is Not Enough

PKI provides the obvious technical precedent. A certificate chain allows a relying system to establish something like: this certificate was signed by this intermediate, which was signed by a root that I trust. This is extraordinarily useful. But institutional authority introduces a different semantic claim. Consider two statements:

"This key belongs to Hospital A."

and:

"Hospital A has standing to issue this healthcare authority."

The first is primarily an identity question. The second is a legitimacy question. The distinction becomes even more important when the authority being represented is regulatory, financial, medical, educational, or governmental. The relevant question may not be:

"Who owns this key?"

but:

"Who authorized this institution to speak with this authority, within this scope, in this jurisdiction?"

The cryptographic machinery may look similar. The governance model cannot simply be assumed to be identical. This note therefore treats PKI as a technical precedent, but not as an automatic governance answer.

3. A Candidate Model

The initial proposal is intentionally simple. A root of institutional trust would be governed through four mechanisms.

3.1 Threshold-controlled roots

A root would not be controlled by one private key. Instead, authority would require an M-of-N threshold among named institutions. For example:

7 recognized institutions

3-of-7 required to authorize a root action

No individual participant could act alone. The objective is not to make the root mathematically stronger than a single Ed25519 key. The objective is governance:

No single participant should be able to unilaterally establish or alter recognized institutional authority.

The closest important operational precedent is the DNSSEC root key-signing process, where root-signing authority is distributed among designated keyholders and operated through controlled ceremonies. But this precedent also exposes a problem examined later: distributing signing power does not automatically distribute accountability.

4. Mandatory Expiry

A root should not necessarily be trusted indefinitely. Instead, a root could have a defined validity period. For example:

Root established
      ↓
valid for a defined period
      ↓
expiration
      ↓
new recognition process
      ↓
new or reconstituted root

The objective is to make continued legitimacy an explicit event rather than an assumption. This creates a mechanism for dealing with institutional change, compromised participants, obsolete governance arrangements, changes in jurisdiction, and changes in the composition of the trust community. However, expiry introduces a new risk. A root that cannot be renewed can stop functioning. Therefore:

Mandatory expiry transforms long-term trust from a static assumption into a recurring governance event, but it also makes renewal itself a critical dependency.

This is not a solved problem.

5. Transparency and Independent Observation

Root actions should be publicly auditable — for example, issuing an intermediate authority, revoking an intermediate, changing root membership, or changing root governance parameters. A transparency log could record these actions in an append-only structure, potentially using Merkle commitments. The objective is straightforward:

A root should not be able to make important trust decisions invisibly.

But transparency creates a second question: what prevents a log operator from presenting different histories to different observers? A possible answer is independent observation. Relying parties could periodically compare observed log state with other independent observers. Conceptually:

              Transparency Log
              /       |       \
             /        |        \
        Observer A  Observer B  Observer C
             \        |        /
              \       |       /
                compare state

If observers disagree about the history, the inconsistency becomes detectable. This is related to the broader transparency and gossip literature surrounding systems such as Certificate Transparency. However, an important lesson from that history is that specifying a gossip mechanism is not equivalent to achieving widespread operational deployment of one. Therefore this note does not treat gossip as a solved component. It treats it as a hypothesis requiring experimentation.

6. Parallel Roots Rather Than One Universal Root

A final design choice is to avoid assuming that every form of institutional authority should ultimately terminate at one universal root. Consider:

                 Trust ecosystem

        ┌──────────┼──────────┐
        │          │          │
   Healthcare   Finance   Education
      Root        Root       Root
        │          │          │
    Hospitals     Banks    Institutions

A healthcare system could recognize healthcare roots. A financial system could recognize financial-service roots. An education system could recognize education roots. A jurisdictional regulator could establish its own root. This reflects an important property of real institutional systems:

Different institutions have different sources of legitimate standing.

A medical regulator does not normally derive its authority from a banking regulator. A financial institution does not normally derive its licensing authority from an educational accreditation body. Parallel roots therefore allow a relying system to define its own recognition boundary. They also create a difficult problem:

What happens when an authority crosses boundaries?

For example, a financial service may simultaneously implicate banking regulation, data protection, consumer protection, sanctions, and identity regulation. There may be no single root capable of answering the entire question. Cross-root recognition may therefore become a governance relationship between institutions rather than a purely technical mechanism. That may be a feature rather than a flaw. It makes the boundary explicit instead of hiding it inside a universal trust hierarchy.

7. NOMOS's Position

There is an important conflict-of-interest question. If NOMOS creates the protocol, should NOMOS also control the root? The proposed answer is no. NOMOS could define the certificate format, the ceremony format, validity rules, transparency structures, verification procedures, and interoperability requirements. But NOMOS should not automatically become a root keyholder. The purpose is to separate:

the machinery for recognizing authority

from:

the institutions whose authority is being recognized.

This distinction is structural, not merely commercial. NOMOS should not need to be trusted as the ultimate authority for the system to function. Its role would instead resemble that of a protocol designer: define the rules by which independently constituted authorities can be represented and verified. However, excluding NOMOS from the signing keys does not eliminate its influence. The protocol author still influences terminology, defaults, technical requirements, reference implementations, interoperability, and ecosystem adoption. Therefore:

Not holding a root key is necessary to avoid becoming the authority. It is not sufficient to make the protocol politically neutral.

That influence must remain visible.

8. Red-Team: What Existing Systems Teach Us

The proposal becomes more useful when treated as something to break. The relevant question is not “what was each existing trust model designed to accomplish,” it is:

Where did each model fail once exposed to real institutional incentives?

8.1 Web PKI

Web PKI demonstrates that certificate hierarchies can operate globally at enormous scale. It also demonstrates that technical controls do not eliminate institutional failure. CA compromises and failures in certificate issuance have repeatedly resulted in distrust events, with browser vendors ultimately deciding which roots remain trusted. The lesson is uncomfortable:

A technically distributed certificate ecosystem can still depend on a relatively small group of actors with enormous practical power over trust.

Lesson: auditing and certification do not eliminate governance concentration.

8.2 DNSSEC

DNSSEC provides a particularly relevant precedent for distributed root key management. It demonstrates that highly sensitive signing authority can be operated through controlled ceremonies involving multiple keyholders. It also demonstrates the difficulty of changing a global trust anchor. The planned DNSSEC root key rollover was delayed after operational measurements indicated that a meaningful number of systems might fail to recognize the new trust anchor.

Lesson: cryptographically sound rotation can still become operationally difficult once millions of independent systems depend on the result. Mandatory expiry therefore cannot simply assume that the date arrives and everyone moves.

8.3 RPKI

RPKI demonstrates another important property of roots: once a technical trust system governs scarce resources, it can become politically significant. The system's trust hierarchy is tied to the allocation and certification of Internet number resources, placing technical authority inside a broader institutional and geopolitical environment. Lesson: a root does not become apolitical merely because the object being certified is technical.

8.4 Certificate Transparency

Certificate Transparency demonstrates the value of making trust decisions publicly observable. It also exposes an important distinction:

Transparency is not the same as consistency.

A public log can make actions visible while still leaving questions about whether every observer is seeing the same state. Independent observation and comparison therefore remain relevant. But the history of transparency systems also suggests caution about assuming that a theoretically specified gossip layer will automatically become an operationally universal defense. Lesson: detection mechanisms must be evaluated by deployment, not merely by specification.

8.5 Accreditation

Accreditation demonstrates the institutional analog of delegated trust. Institutions recognize other institutions as meeting defined standards. But accreditation systems can also become slow, expensive, difficult for new entrants, and protective of incumbent structures. Lesson: having multiple institutional signers does not automatically create pluralism. A group can become a cartel.

8.6 Professional Licensing

Professional licensing provides an even closer analogy to institutional standing. A licensing authority does not merely certify that someone possesses a cryptographic identity. It determines whether that person has legitimate standing to practice within a defined jurisdiction. But licensing is also highly fragmented. Recognition in one jurisdiction does not necessarily imply recognition in another, and professional boards can create barriers to entry. Lesson: sector- and jurisdiction-specific legitimacy is realistic, but fragmentation and incumbent protection are persistent costs.

8.7 Treaty Recognition

Treaty and mutual-recognition regimes demonstrate what happens when independent authorities need to recognize one another. Recognition depends on continuing institutional relationships. Those relationships can weaken, change, or collapse. Technical interoperability cannot force political recognition. Lesson: cross-root recognition is ultimately a governance relationship, not merely a protocol feature.

8.8 Federated and Web-of-Trust Models

The alternative is to remove the root altogether. Trust can instead propagate through a network of peer relationships. PGP provides the classic example. This model is attractive because there is no single root. It is also difficult to operate at general-purpose scale. Users must understand and maintain trust relationships, and the system must solve onboarding and path-selection problems. Lesson: eliminating the root does not eliminate governance. It moves governance into the trust graph.

9. What Breaks

Applying those lessons to the proposed model produces several failures.

9.1 Threshold signing does not solve bootstrapping

M-of-N answers how many participants must agree. It does not answer who chooses the participants. If seven institutions constitute the root, who selected those seven? And who selected the people who selected them? The bootstrapping problem has moved upward. It has not disappeared.

9.2 Threshold signing may weaken accountability

Suppose four of seven institutions approve an intermediate authority that later causes serious harm. Who is accountable? A threshold structure distributes authority. It does not automatically distribute liability in a useful way. Indeed, it may make accountability harder by allowing participants to point toward the collective decision. This is an unresolved problem.

9.3 Expiry creates a new failure mode

Expiry prevents perpetual authority. But it also creates the possibility that no one could agree on renewal, so the trust system stopped working. An attacker may not need to compromise a root. They may only need to prevent sufficient agreement at renewal time. Mandatory expiry therefore trades one class of risk for another.

9.4 Transparency does not guarantee prevention

A public record can reveal that a bad authorization occurred. That does not necessarily prevent the authorization from being used. For high-consequence actions such as financial transfers, medical decisions, or regulatory actions, post-event detection may be insufficient. Transparency is therefore an accountability mechanism, not automatically an execution-time safety mechanism.

9.5 Sector roots create boundary problems

Parallel roots reduce universal concentration. But they create more boundaries. A real transaction may cross several sectors. The relying system must then determine which roots must be recognized and how conflicting authorities interact. The problem has not disappeared. It has become explicit. That may be preferable, but it remains a design problem.

9.6 Excluding NOMOS does not eliminate influence

Removing NOMOS from the root keyholders prevents one obvious conflict. It does not make NOMOS neutral. The organization defining the protocol inevitably influences the system. Therefore neutrality cannot be claimed simply because NOMOS does not hold a key.

10. What Survives

The red-team does not invalidate the entire direction. It changes what can honestly be claimed. The strongest surviving observation is:

There is a meaningful difference between a single commercial entity being the trust anchor and a trust anchor constituted through an explicit, auditable institutional process.

Threshold signing can make unilateral control harder. Transparency can make actions more observable. Independent observation can make inconsistent histories detectable. Expiry can make continued legitimacy an explicit event. Sector-scoped roots can prevent unnecessary concentration of authority. None of these guarantees legitimacy. But they can change the cost and visibility of capture. That distinction matters. A system that makes institutional misuse harder, more observable, more attributable, and more contestable may be preferable to one that simply makes misuse technically possible and leaves the governance assumptions implicit.

11. A Narrower Recommendation

The evidence does not justify proposing a universal global root architecture today. The more defensible approach is experimental.

1. Define the reusable technical primitives

Specify only the parts that are genuinely protocol-shaped: root action format, certificate format, validity and expiry representation, transparency record format, and verification rules.

2. Run one constrained experiment

Choose a single sector. Use a small number of publicly accountable participants. Define a review date from the beginning. Treat the root as an experiment rather than a permanent settlement.

3. Treat liability as unresolved

Do not imply that threshold governance solves accountability. Make the question explicit:

Who bears responsibility when collective authorization produces harmful authority?

4. Test transparency before standardizing gossip

Measure who observes, how often observers compare, what inconsistencies are detected, and what operational cost is introduced. Do not assume the theoretical mechanism will become a practical one.

5. Let implementation precede standardization

The chain-of-trust primitive (NOMOS-SPEC-007, Draft) demonstrates the lower-level mechanism:

root
 ↓
intermediate
 ↓
signing key
 ↓
.nomos artifact
 ↓
independent verification

The next step should be to test the institutional governance layer around that mechanism. Only after that experiment should a standardized root-governance protocol be considered.

12. The Deeper Question

The technical problem began with a simple requirement:

How can an independent system recognize authority without calling the authority's issuer?

The chain-of-trust mechanism provides one answer. An artifact can carry evidence of its own authorization:

.nomos artifact
      ↓
signing key
      ↓
certified by intermediate
      ↓
certified by root
      ↓
root recognized by relying system

But this exposes the deeper question:

Why does the relying system recognize the root?

That question cannot be answered by Ed25519, hashing, certificates, or Merkle trees. It requires an institutional process. This is therefore the boundary between cryptographic trust and institutional legitimacy. Cryptography can make a legitimacy decision portable, tamper-evident, machine-checkable, and independently verifiable. It cannot manufacture the legitimacy itself. That distinction should remain explicit in any future NOMOS architecture.

13. Conclusion

The purpose of this note is not to declare a universal root of trust solved. It is to identify the next layer of the problem. NOMOS can make institutional authority executable. It can make that authority cryptographically verifiable. A chain of trust can make that authority portable between systems that do not share a live relationship. But portability eventually exposes the question of recognition: who gets to establish that an institution has standing to issue machine-executable authority?

The initial proposal — threshold roots, mandatory expiry, transparency, independent observation, and sector-scoped trust — provides several mechanisms for making that process more distributed and auditable. The red-team also shows their limits. Bootstrapping remains unresolved. Liability remains unresolved. Renewal remains unresolved. Cross-sector recognition remains unresolved. The practical value of gossip remains to be demonstrated. And protocol authors retain influence even when they do not hold signing keys.

These are not reasons to discard the direction. They are reasons not to standardize it prematurely. The appropriate next step is therefore not a universal trust architecture. It is a controlled experiment.

Build the governance mechanism. Put it in front of real institutions. Try to break it. Measure what fails. Then standardize only what survives.

That is the same principle that led to the chain-of-trust key-certificate primitive in the first place. The objective is not to create another authority. It is to make authority portable, machine-verifiable, and independently recognizable without making the protocol operator the source of legitimacy.

Status

Design note / research draft. Not itself a specification, and not part of NOMOS-SPEC-007’s normative text — but SPEC-007 §9 cites this note’s open question, root governance, as deliberately unresolved. This note does not resolve it either.

• Companion research: Paper 5 — Bounded Contextual Authority (R-08)
• Companion research: NOMOS-SPEC-007 (Draft) — Chain-of-Trust Key Certificates

Author

NOMOS Protocol — Infrastructure for Machine-Executable Institutional Authority.