Encoded Objective Law — Encoding Values in Operations 1.2.2

The Problem Encoded Objective Law Solves

Traditional Objectivism (TO) established that rights are moral principles defining freedom of action in a social context — boundaries against the initiation of force. The framework is correct. The principle has not changed. What has changed is the distance between declaring a right and having it hold.

A right declared but not enforced is a preference. A right enforced only by goodwill is a courtesy. A right that depends on every institution in the chain respecting it voluntarily — with no structural mechanism to prevent violation, detect breach, or make circumvention costly — is an aspiration dressed as a principle. It looks load-bearing. It is decorative.

The load cases diagnosed in Arc 1 make this concrete. Institutional capture redirects the outputs of systems designed to protect rights toward the interests of those who control the system. Quiet enclosure converts voluntary participation into structural dependency, eroding the conditions under which consent is meaningful. AI-mediated coordination produces enforcement at speeds that outpace the institutions designed to provide recourse. In each case, the principle — the right — is still on the books. The system has simply stopped carrying it.

TO diagnosed the danger clearly: regulation grounded in suspicion of persons — preemptive guilt dressed as policy — collapses liberty into permission. That diagnosis stands. What TO did not have was a framework for distinguishing suspicion-based constraint from reality-based design. Not every structural guardrail is an accusation. Some constraints exist not because the system distrusts the people inside it, but because the system acknowledges what happens when incentives drift, complexity compounds, and institutional memory degrades. The question is not whether to constrain. It is what kind of constraint, where it belongs, and what it protects.

This is the structural gap that encoded objective law addresses. The problem is not that people lack moral principles. It is that the systems they operate within have no obligation to encode those principles into their operations. Epistemic integrity (1.2.1) ensures that truth survives institutional processing. Encoded objective law ensures that moral constraints survive operational implementation. Where epistemic integrity preserves signal, encoded objective law preserves boundaries.

The innovation is not a replacement for rights. It is the design layer that makes rights operational — that encodes moral limits into rules, procedures, code, and institutional architecture so that ethical outcomes do not depend entirely on the character of the persons operating the system.

The Source Patterns

Encoded objective law draws from three pattern families, each admitted under the Rule of Admission defined in (1.2.0).

Sovereignty Primitives

Sovereignty primitives are the structural building blocks by which agents maintain control over their own resources, decisions, and exposure within a system. The term comes from systems architecture, but the structural insight is ancient: power must be bounded, and the mechanism for bounding it must not depend on the good intentions of the powerful.

Four primitives are load-bearing here. Least privilege restricts any component's access to the minimum required for its function — no more. A system built on least privilege makes overreach structurally difficult, not merely discouraged. Signatures and attestations provide verifiable proof that a specific claim was made by a specific agent at a specific time, without requiring trust in an intermediary. Append-only state ensures that records, once written, cannot be silently altered — the history of the system is auditable by design, not by permission.

Admission under the five tests. Sovereignty primitives describe real mechanisms in real systems — they pass truth-contact. They restrict power rather than expanding it — they pass non-coercion. They function regardless of participant virtue, because the constraints are architectural — they pass scales without saints. The vocabulary (least privilege, signatures, append-only) is technical but expressible in structural terms — they pass plain language. And they operate on institutional actions and system states, not on persons — they pass privacy by default.

Incentive Compatibility

Incentive compatibility is a property of institutional design: a system is incentive-compatible when participants who act in their rational self-interest simultaneously advance the system's intended purpose. The insight comes from mechanism design — the branch of economics that studies how to structure rules so that individual incentives and collective objectives align without requiring coercion or surveillance.

The structural relevance for encoded objective law is direct. A protocol that requires participants to act against their own interests in order to produce ethical outcomes will fail — not because participants are immoral but because the structure has set self-interest and moral outcome on opposite trajectories. An incentive-compatible protocol aligns them. The mechanism does the work that sermons cannot.

Admission. Incentive compatibility describes documented dynamics in real institutional design — truth-contact. It operates by aligning incentives, not by overriding them — non-coercion. It is designed explicitly for self-interested agents — scales without saints. The concept (aligning individual incentive with system purpose) is expressible without disciplinary jargon — plain language. And incentive structures can be designed around institutional outputs without requiring exposure of private information — privacy by default.

Enforcement Cost Analysis

Enforcement cost analysis examines what it actually costs to enforce a rule — in resources, in time, in institutional attention, and in the collateral consequences of enforcement. The structural insight is that enforcement is not free, and the cost of enforcement shapes which rules are actually enforced, which are selectively enforced, and which exist on paper while the system quietly ignores them.

This pattern is critical for encoded objective law because it reveals the gap between declared constraints and operational reality. A rule with enforcement costs that exceed the institution's capacity will not be enforced, regardless of its moral importance. A rule with enforcement costs that are concentrated on the weakest participants will be selectively enforced in ways that undermine the principle it was designed to protect. Understanding enforcement costs is the structural prerequisite for designing protocols that are operationally honest — that commit only to what the system can actually carry.

Admission. Enforcement cost analysis describes real institutional dynamics — truth-contact. It does not itself require coercion; it studies coercion's costs — non-coercion. It explicitly accounts for imperfect enforcement environments — scales without saints. The vocabulary (enforcement cost, selective enforcement, operational capacity) is plain — plain language. And the analysis operates on institutional operations, not on persons — privacy by default.

What RO Builds

The three admitted pattern families — sovereignty primitives, incentive compatibility, and enforcement cost analysis — describe real features of how rules are enforced, circumvented, and maintained in institutional systems. But they are instruments, not innovations. Cryptographers study sovereignty primitives. Economists study mechanism design. Policy analysts study enforcement costs. None of them has built what Resilient Objectivism (RO) builds here: a moral architecture for protocols — a framework for specifying when and how values should be encoded into operational rules, grounded in a rights framework that makes non-coercion non-negotiable.

Encoded objective law is defined as the design discipline of encoding moral constraints into rules, procedures, code, and institutional architecture so that ethical outcomes are structural properties of the system rather than contingent on the virtue of its operators.

The innovation has five structural components.

The Enforce-in-Code / Enforce-in-Culture Distinction

Not every moral constraint belongs in code. Not every moral constraint survives being left to culture. The central contribution of encoded objective law is the framework for distinguishing between the two.

Enforce-in-code applies to constraints that are binary, universal, and violation-intolerant. These are hard constraints — the system physically prevents the violation rather than punishing it after the fact. Least privilege is enforced in code: a component simply cannot access what it has not been granted. Append-only state is enforced in code: once written, a record cannot be modified. Cryptographic attestation is enforced in code: a signature either verifies or it does not. Hard constraints do not rely on detection, punishment, or institutional will. They make the violation structurally impossible — or at least structurally expensive to the point of impracticality.

Enforce-in-culture applies to constraints that require judgment, proportionality, context-sensitivity, or human deliberation. These are soft constraints — the system provides frameworks, norms, review processes, and escalation paths, but the constraint is ultimately carried by human decision-making. Questions of proportionality (how much enforcement is appropriate?), edge cases (does this specific situation fall within the rule?), and competing values (when two legitimate constraints conflict, which governs?) cannot be encoded as binary logic without producing brittleness or injustice.

The distinction is not a hierarchy. Hard constraints are not superior to soft ones. The design question is fit: which category does each constraint belong to, and what happens when the category assignment is wrong? A hard constraint applied to a judgment call produces rigidity — the system enforces the letter while violating the spirit. A soft constraint applied to a binary boundary produces drift — the system allows exceptions until the boundary no longer holds. Encoded objective law provides the framework for making the assignment correctly.

Sidebar (1.2.2-2) expands this distinction in detail, including the predicate gate the next component introduces.

The Adjudication Requirement

Before drawing this pattern's boundary, the boundary the pattern does not draw: a private party withdrawing a service it never owed, on terms already accepted, is never in scope — regardless of how severe the effect on the party who loses the service. That withdrawal is ordinary private discretion, and no amount of hardship converts it into an adjudication problem. What follows is the adjudication requirement: a procedural discipline governing something narrower and specific than "every hard constraint" — the exercise of public force, and private action taken under state compulsion or delegated state enforcement authority, and only as to that specific act.

The trigger has two limbs, not three. Public force exercised directly by government is the first. Private action taken because the state compelled it — a court order, a subpoena, a mandated takedown — or because the state delegated its own enforcement authority to the private actor — a licensed collection agent, a regulator-deputized auditor — is the second. A third candidate limb does not belong here: a state-created shield (deposit insurance, a liability cap, implicit bailout exposure) reallocates loss, not authority, and conflating the two would sweep in nearly every incorporated entity and every insured bank as a due-process duty-bearer for ordinary business decisions — directly contradicting the scope boundary above. Systemic moral-hazard awareness (1.2.8) treats this same distinction on its own ground: a participant responding rationally to a guarantee it did not design is evidence that the incentive hazard exists, not proof that the participant authored it. The same separation holds here. Where a state-created shield deserves scrutiny, that scrutiny belongs entirely in the moral-harm diagnostic register — as a question aimed at the authority that granted the shield — never as a duty imposed on the party that merely benefits from it.

A prior legitimacy gate. What follows governs how delegated or public force is exercised once the force itself is already established as legitimate under RO's inherited rights framework — retaliatory, directed at a party whose own act triggered it, exercised within a delegation the state was entitled to make in the first place. Clearing the requirement below does not certify the underlying exercise of force as legitimate. A conscription statute or an expropriation can be knowable-in-advance, inspectable, and contestable before an independent reviewer, and still be an initiation of force that Arc 1's rights framework — inherited from Traditional Objectivism (TO) — rejects on other grounds. This pattern presupposes that prior question. It does not answer it, and no procedural compliance below should be read as answering it.

Once both gates clear — the act falls within the two limbs, and the force itself is legitimate — two requirements govern the encoding, and they are separate constraints, not one.

Requirement A: the finding is contestable. The fact-predicate that triggered the action must be contestable before someone whose position does not depend on the operator. WP4's §8.2 (Independence of Review) supplies the capture-resistance test for whether "outside" is real rather than nominal: who appoints the reviewer, who can remove or penalize them, what evidence they can actually access, and whether they can alter the outcome. A rule known in advance, an inspectable basis for the finding, and an effective remedy are the conditions under which this contestation is real — not independent boxes to tick alongside it, but what makes the contestation genuine rather than decorative.

Requirement B: irreversible consequences forbid unilateral automation. Where a consequence cannot later be repaired, the action may not be taken unilaterally by automation in the first place — regardless of how good the after-the-fact contestation path is. Contesting a finding after an unrepairable act has already happened is a formality, not a remedy. This requirement stands on its own; it does not fold into Requirement A, because Requirement A only covers errors that are reversible and says nothing about the ones that are not. It is consistent with epistemic integrity's (1.2.1) own staged-judgment discipline: irreversibility must be earned by evidentiary state, not defaulted into by the convenience of automation.

The predicate gate. A constraint may be enforced purely in code only where its trigger is determinable without deciding a contested question of intent, mental state, or the application of a general term to a particular case. This is not the same test as "directly observable" — a signature check is a computation, not an observation, and would fail a literal observability test while correctly passing this one. A credential is present or absent; a signature verifies or it does not — both clear the gate. "This was fraud" does not clear it: fraud is constituted by intent, so however binary the resulting enforcement action, the predicate itself is a judgment, not a fact the code can determine alone.

Where the trigger fails this gate but the resulting action is otherwise automatable, that is not a third category alongside enforce-in-code and enforce-in-culture. It is a routing rule: automate the action, but run the finding that authorizes it through Requirement A first. A frozen account can execute in code the instant the finding clears; the finding itself cannot. Sidebar (1.2.2-2) folds this gate into its enforce-in-code criteria directly.

Worked example. A bank freezes an account under a court order. The order is the state's act, and it owes the full package: a known rule, an inspectable basis, review by a party outside the bank's control, contestability, and — because account freezes are ordinarily reversible — an effective remedy. The bank is a conduit, not the duty-bearer of adjudication; its narrower obligation is to act only within the order's actual terms and to identify the order as the basis for the freeze if asked. Contrast the same bank freezing the same account under its own contract's terms, no court order involved: ordinary private discretion, out of scope entirely, no adjudication duty attaches — the scope boundary that opened this section, not an exception to it. Sidebar (1.2.2-3) explains why Bitcoin, despite encoding constraints with unusual rigor, cannot supply this example in the court order's place.

Anti-capture accounting. Attaching an independent-review requirement creates new machinery — a reviewer, an evidence channel, a remedy mechanism — and that machinery is itself a candidate for the next capture. The dependency is worth incurring for two structural reasons, not one: the domain is narrow (only actual delegated or public force, not general institutional conduct), and the alternative — no contestability at all for automated coercive action — is worse than the risk that the review mechanism itself degrades. The restraint principle (1.2.3) mitigates that residual risk without eliminating it: keep the reviewer's role narrow, keep its dependencies minimal, so the machinery built to prevent one capture does not grow large enough to invite another.

Moral Harm as Threshold

Encoded objective law names a boundary between institutional friction (unpleasant but tolerable) and moral harm — a condition worth a system's own designers' attention. Moral harm is defined as the point at which a system's operation crosses from affecting interests to violating boundaries — the threshold before the initiation of force, where the structural conditions for coercion are being assembled even if force has not yet been declared.

Moral harm is not identical to the initiation of force. Force is the overt act. Moral harm names the structural conditions that precede it and enable it — the accumulation of dependency, the erosion of exit, the removal of recourse, the concentration of power without accountability. A system that produces moral harm is not yet coercive in the rights-violation sense. But it is assembling the architecture of coercion, and encoded objective law names that assembly so the system's own designers can see it and correct it. It is diagnostic vocabulary, not a license for anyone outside the system to intervene — the adjudication requirement above, not moral harm, is what governs when an outside party actually acquires standing to act, and only within its own narrow, force-specific domain.

Sidebar (1.2.2-1) provides the full definition, the relationship to TO's rights framework, and the stopping rule that keeps the diagnostic register from being read as a finding with no consequence.

Privacy as Embedded Constraint

Encoded objective law does not treat privacy as a separate concern to be added after the protocol is designed. Privacy requirements are embedded into the protocol's architecture from the beginning, following a four-step discipline: minimize (collect only what is structurally necessary), compartmentalize (restrict access to the minimum required function), encrypt (protect data in transit and at rest), and attest without exposing (verify claims about persons without requiring them to reveal the underlying data).

This embedded discipline connects encoded objective law to privacy by design (1.2.4), which will construct privacy as a full innovation. Here, the point is narrower: a protocol that encodes moral constraints but requires surveillance to operate has not passed the privacy by default test in the Rule of Admission. The protocol must be designed so that persons can participate, be verified, and be protected without becoming legible to institutional power as a condition of compliance.

Institutional Duty of Enforcement

The components above are not optional features. They constitute a design obligation that parallels the institutional duty of clarity established in (1.2.1). Any institution that structures the conditions under which persons act — that sets rules, allocates access, determines consequences — has a duty to encode its moral constraints into its operational architecture rather than relying exclusively on the virtue of its operators.

This duty does not mean every institution must run on cryptographic protocols. It means every institution must ask: which of our moral commitments are currently enforced only by culture, and which of those would hold if the culture shifted? Where the answer is "they would not hold," encoded objective law identifies a design gap that requires structural closure.

Failure Modes

Encoded objective law does not guarantee moral outcomes. It guarantees that moral constraints are carried by structure rather than by hope. When the design requirements are absent, specific failure modes emerge.

Protocol capture. A protocol designed to enforce moral constraints is modified, extended, or reinterpreted to serve the interests of those who control it. The protocol retains its original language — it still references rights, consent, transparency — but the operational rules have been adjusted so that the constraints no longer bind the powerful. The protocol has been captured. This is the protocol-level analogue of the institutional capture described in (1.1.1), and it is structurally identical: the outputs are redirected while the labels remain unchanged.

Enforcement theater. The protocol exists. The enforcement mechanism exists. The violations continue. Enforcement theater occurs when the institutional cost of genuine enforcement exceeds the institution's willingness to pay — and the institution responds not by redesigning the protocol but by performing enforcement selectively, symbolically, or on the weakest participants. The protocol's existence provides political cover. Its enforcement provides the appearance of integrity. Neither produces the constraint it claims.

Over-encoding. The protocol specifies too much. Constraints that require judgment are encoded as hard rules. Edge cases are handled by rigid logic rather than human deliberation. The result is a system that enforces the letter of the moral commitment while systematically violating its purpose — a bureaucratic morality that substitutes compliance for ethics. Over-encoding is the failure mode that (1.1.6) anticipated when it named RO's refusal of over-encoding as a structural commitment: the capacity to act is not permission to specify.

Finding without recourse. A system automates a punitive or restrictive action, correctly encodes the resulting rule as binary, and then treats a judgment-laden predicate — fraud, violation, ineligibility — as though it required no interpretation at all, leaving the affected person with no path to contest the finding that triggered the action. The rule itself may be entirely sound; what fails is the predicate feeding it, and with it, Requirement A above. This is distinct from over-encoding, which wrongly hard-codes a proportionality or context judgment as the rule itself — the rule is the problem there, not the finding behind it. It is also distinct from moral-hazard drift below, which delegates too much trust to a protocol that is otherwise working as designed, rather than leaving a single unreviewable finding standing behind an automated action. Finding without recourse is scoped to the domain the adjudication requirement governs: it names the failure of Requirement A specifically, not a general caution about automation.

Moral-hazard drift. A well-designed protocol creates the appearance of moral safety — "the protocol handles it" — which erodes the individual moral vigilance that the protocol was designed to supplement, not replace. Over time, participants delegate more judgment to the protocol than it was designed to carry, and the protocol operates beyond its load capacity. The system produces outcomes that no protocol designer intended and no participant examined, because everyone assumed the protocol was handling it.

What RO Takes / What RO Leaves

What RO Takes:

What RO Builds:

Encoded objective law — the design discipline of encoding moral constraints into operational architecture. Five components: the enforce-in-code / enforce-in-culture distinction (determining which constraints belong where), the adjudication requirement (governing what must survive the encoding when the constraint being encoded is the exercise of public or delegated force, regardless of the mode chosen), moral harm as diagnostic threshold (naming when a condition warrants a system's own designers' attention, not licensing outside intervention), privacy as embedded constraint (building opacity into the protocol from the start), and the institutional duty of enforcement (establishing the design obligation). The innovation is original because it unites the admitted patterns under a moral architecture derived from rights as boundary conditions — no source discipline imposes this obligation on its own.

What RO Leaves Behind:

• Techno-utopianism. The belief that encoding rules in code automatically produces moral outcomes. Code is a medium, not a morality. A protocol that encodes the wrong constraints with perfect fidelity has not achieved encoded objective law — it has automated injustice. The innovation requires that the constraints themselves be morally grounded before they are operationally encoded.

• Total codification. The demand that all moral constraints be enforceable in code. Some constraints — proportionality, mercy, contextual judgment — cannot be reduced to binary logic without losing what makes them moral. The enforce-in-code / enforce-in-culture distinction exists precisely because encoded objective law recognizes the limits of hard encoding.

• Surveillance-dependent enforcement. Any enforcement mechanism that requires constant monitoring of persons. A protocol that achieves compliance by making every participant transparent to the enforcer has traded one form of coercion for another. Enforcement must be compatible with privacy by default — verification without exposure.

• Consent theater. Mechanisms that present the appearance of consent — "by clicking you agree" — without the structural conditions that make consent meaningful: comprehension, genuine alternatives, and the capacity to refuse without disproportionate cost. Encoded objective law requires that consent be operationally real, not performatively present.