Enforce-in-Code vs. Enforce-in-Culture 1.2.2-2

Two Modes of Enforcement

The article (1.2.2) introduces the enforce-in-code / enforce-in-culture distinction as the central framework of encoded objective law. This sidebar expands the distinction: what each mode looks like in practice, how to determine which mode a given constraint belongs to, and what goes wrong when the assignment is reversed.

The distinction is not about technology. Code, in this context, means any mechanism that makes a constraint structurally automatic — a cryptographic proof, an access-control list, an append-only ledger, a constitutional provision with self-executing remedies. Culture means any mechanism that depends on human judgment to apply — a norm, a review process, an escalation path, a policy that requires interpretation. Both are legitimate modes of enforcement. The design question is which mode fits which constraint.

Enforce-in-Code

Hard constraints are appropriate when all of the following conditions hold:

The constraint is binary. It applies or it does not. There is no spectrum of partial compliance, no contextual gradient, no case-by-case assessment. A signature either verifies or it does not. An access permission is either granted or it is not. A record is either append-only or it is mutable. Binary constraints are the natural candidates for code-level enforcement because the enforcement mechanism does not need to exercise judgment — it needs to execute a rule.

Violation is intolerable. The consequence of a single violation is severe enough that detection-and-punishment after the fact is structurally insufficient. If one unauthorized access to a confidential record can produce irreversible harm, the constraint must prevent the access, not punish it retrospectively. Hard constraints are justified when the cost of a single breach exceeds the cost of enforcing the constraint structurally.

The constraint is universal. It applies to all participants without exception. No role, status, or institutional position exempts anyone from the constraint. Hard constraints that apply selectively — that bind some participants while exempting others — are not constraints. They are instruments of power wearing the language of principle.

The trigger clears the predicate gate. A constraint is only a candidate for code-level enforcement if the fact that triggers it is determinable without deciding a contested question of intent, mental state, or the application of a general term to a particular case. This is a gate the constraint must clear, not one more item on a checklist to weigh against the others — fail it, and the constraint cannot be enforced purely in code no matter how binary, intolerable, or universal it otherwise is. The test is not "directly observable": a signature check is a computation, not an observation, and it clears the gate anyway, because verifying a signature does not require deciding what anyone intended. A credential is present or absent. A signature verifies or it does not. "This was fraud" fails the gate — fraud is constituted by intent, so however binary the resulting enforcement action, the predicate itself is a judgment a code path cannot reach on its own.

Examples: least privilege (access control), cryptographic attestation (identity and provenance verification), append-only state (record integrity), hard caps and rate limits (resource constraints), signature verification (authentication).

The routing rule. A trigger that fails the predicate gate does not automatically move the whole constraint into enforce-in-culture. Where the resulting action is otherwise automatable, this is not a third category alongside enforce-in-code and enforce-in-culture — it is a routing rule: automate the action, but route the finding that authorizes it through independent review first (the article's adjudication requirement, Requirement A, for the narrower domain where that finding also authorizes public or delegated force). A protocol can hold a rule that says "freeze the account once the finding clears" entirely in code while still requiring the finding itself to clear a human or independently reviewed determination. The rule is enforce-in-code. The predicate that feeds it is not.

Enforce-in-Culture

Soft constraints are appropriate when any of the following conditions hold:

The constraint requires proportionality. The appropriate response depends on the severity, context, and circumstances of the situation. A protocol that enforces a single penalty for all violations — regardless of scale, intent, or consequence — is not proportionate. It is mechanical. Proportionality requires judgment, and judgment cannot be reduced to binary logic without producing injustice.

The constraint involves competing values. Two legitimate moral principles may conflict in a specific case. Privacy and accountability. Individual liberty and collective safety. Transparency and security. When constraints conflict, the resolution requires human deliberation — weighing the specific circumstances, assessing the relative stakes, and making a judgment that a code-level rule cannot replicate without privileging one value permanently over the other.

The constraint applies to edge cases. The general rule is clear, but a specific situation falls on the boundary. Edge cases are the domain of culture, because they require the enforcement mechanism to recognize that the rule's purpose is better served by flexible application than by rigid execution.

The constraint involves evolving standards. What constitutes acceptable behavior, fair process, or adequate transparency may change as conditions, knowledge, or technology evolve. A hard-coded constraint that embeds a specific standard risks becoming a structural barrier to legitimate evolution. Soft constraints are adaptable because they operate through review, deliberation, and revision rather than through immutable logic.

Examples: dispute resolution, editorial standards, hiring and evaluation practices, resource-allocation prioritization, inter-institutional coordination, norm evolution.

Category Errors

The most consequential failures in encoded objective law arise not from absent enforcement but from misassigned enforcement — constraints placed in the wrong category.

Hard encoding a judgment call. A constraint that requires contextual assessment is implemented as a binary rule. The system enforces the constraint rigidly. Edge cases are handled badly. Proportionality disappears. The participants experience the system as unjust — not because the constraint is wrong, but because the enforcement mechanism cannot accommodate the complexity the constraint was designed to navigate. Over-encoding is this failure at scale. Hard-coding a judgment-laden predicate specifically — rather than a proportionality judgment generally — is the predicate-gate failure the article names as finding without recourse.

Soft encoding a binary boundary. A constraint that should be structurally automatic is left to cultural enforcement — norms, policies, voluntary compliance. The constraint holds when institutional culture is strong. It erodes when culture drifts, when incentives shift, or when the persons responsible for enforcement change. The boundary becomes optional in practice while remaining mandatory in language. This is the structural condition that produces enforcement theater.

The enforce-in-code / enforce-in-culture distinction does not eliminate difficult decisions. It provides a framework for making them honestly — and for recognizing when the system has assigned a constraint to the wrong category.