Unit Review: Encoded Objective Law Rollout 2.3C.3-R

Key Structural Points

• Encoded objective law (1.2.2) at the organizational level means deciding what to hard-encode into structure that operates independent of individual discretion and what to leave to trained judgment — then building the enforcement, change control, and rollback that keep encoded rules honest.

• The enforce-in-code flow evaluates four criteria — stakes, frequency, human variability, and reversibility — to determine whether a decision should be hard-coded, policy-gated, reviewed, or left to judgment.

• Four encoding mechanisms are available, ranked from strongest to lightest: hard code (system enforcement), mandatory policy (approval gates), mandatory review (oversight check), and structured ceremony (rigorous process without predetermined conclusion).

• Three structural layers support every encoded protocol: least privilege and segregation of duties (who can decide vs. verify), audit and attestation (append-only records of every decision), and change control with rollback (how rules are revised and reverted).

• Data governance is encoded objective law applied to information — data minimization, least-privilege access, and selective disclosure become enforced at the system level through privacy by design (1.2.4).

• Finance controls express the Trader Principle (Arc 1) through protocol enforcement: segregation of duties, append-only ledgers, and capped discretion prevent any single person from committing more than the institution agreed to allow.

• AI-mediated decisions require three structural governance layers: algorithmic transparency before deployment, accountability auditing after, and override and rollback capability always available — with explainability requirements increasing as stakes increase.

• Phase I's strain condition on epistemology and ethics under adversarial pressure (1.3.9) applies directly: an organization whose enforcement depends entirely on good faith has no structural defense when good faith fails.

Philosophical Lexicon

• encoded objective law — The embedding of moral constraints into system design, where values like consent, sovereignty, and property are enforced structurally — through code or protocol — not merely by law, habit, or virtue; at the organizational level, rules, procedures, and institutional architecture so that ethical outcomes are structural properties of the system rather than contingent on the virtue of its operators. One of RO's nine design patterns. (RO)
• privacy by design — The architectural commitment that persons remain selectively opaque to power; systems default to privacy and require justification for exposure, not the reverse — at the organizational level, enforced through data minimization, least-privilege access, and selective disclosure. One of RO's nine design patterns. (RO)
• attestation — A verification mechanism that confirms a claim without exposing the underlying data; at the organizational level, formal statements signed or verified by responsible persons creating accountability for claims. (RO)
• append-only state — A system design in which records, once written, cannot be silently altered; ensures the history of the system is auditable by design. (RO)
• capture — The process by which an institution's structure is gradually redirected to serve the interests of its powerful actors rather than its stated purpose; encoded objective law is a defense against capture. (RO)
• Trader Principle — The principle that human relationships should be exchanges of value — each party contributes something the other values and receives something in return, with no sacrifice on either side. (TO)

Unit Glossary

• enforce-in-code flow — A four-criteria decision framework (stakes, frequency, human variability, reversibility) that determines whether an organizational decision should be hard-coded, policy-gated, reviewed, or left to judgment.
• hard code — System enforcement of a decision rule built into software or database constraints; a person cannot override without triggering an audit trail and escalation.
• mandatory policy — Decision follows a defined path with approval thresholds; exceptions are possible with documented authority.
• mandatory review — Decision is made by authority but reviewed before or after implementation; review can veto or modify.
• change control — The defined process for modifying an encoded rule: who proposes, who reviews, how long the review period, when the change takes effect.
• rollback — The defined process for reverting a rule change that causes harm: what triggers reversion, who initiates, how quickly the institution can revert.
• data minimization — Collecting only data necessary for a stated purpose; retention limited; purge automated.
• selective disclosure — When sharing data externally, disclosing only the minimum necessary for the stated purpose.
• capped discretion — Manager authority on spending capped by role and time period; exceptions require escalation.

Concept Check

• Why does the article argue that you cannot hard-encode everything and cannot leave everything to judgment? What structural consequence does each extreme produce?

• The enforce-in-code flow uses four criteria. Walk through a concrete organizational decision and assess it against all four. What encoding mechanism does the result recommend?

• What is the structural difference between hard code and mandatory policy? Under what conditions would you choose one over the other?

• Why does the article treat least privilege and segregation of duties as distrust mechanisms rather than trust mechanisms? What structural assumption drives that framing?

• How does change control prevent encoded rules from calcifying? What is the relationship between change control and the restraint principle's sunset mechanisms (2.3C.2)?

• Data governance applies three principles: minimization, least privilege, and selective disclosure. What structural risk does each principle address, and what happens to the organization if any one of the three is missing?

• The AI sidebar argues that explainability requirements should increase as stakes increase. What structural tradeoff does this principle navigate, and why does the article argue against automating every decision that could be automated?

• How do finance controls — segregation of duties, append-only ledgers, and capped discretion — express the Trader Principle through protocol enforcement? What does each mechanism prevent?

Points to Ponder

• Identify one decision in your organization that is currently left to individual judgment. Assess it against the four enforce-in-code criteria. Does the assessment recommend encoding? If so, what mechanism would you choose — and what resistance would you expect from the people who currently hold that discretion?

• Consider your organization's data practices. Do you know what data the organization holds about you? If you asked for a complete inventory, could the organization produce one? What does the answer tell you about the state of data governance?

• Think about a policy that changed recently in your organization. Did the change go through a defined process — proposal, review, approval, rollback plan — or did it change informally? What does the process (or absence of process) tell you about whether your organization's rules are structurally encoded or culturally performed?

To Learn More

• Lessig, Lawrence. Code: And Other Laws of Cyberspace. Version 2.0. New York: Basic Books, 2006. Argues that code is law — that the architecture of digital systems constrains behavior as effectively as legal regulation, directly relevant to this unit's argument that encoding moral constraints into structure is a design discipline, not merely a policy preference.

• Nissenbaum, Helen. Privacy in Context: Technology, Policy, and the Integrity of Social Life. Stanford, CA: Stanford University Press, 2010. Develops the concept of contextual integrity — that privacy norms are tied to the context of information flow, not to abstract rules about data types — directly relevant to the selective disclosure principle and the unit's argument that data governance must be enforced structurally, not left to judgment.

• O'Neil, Cathy. Weapons of Math Destruction: How Big Data Increases Inequality and Threatens Democracy. New York: Crown, 2016. Documents how algorithmic decision systems operating without transparency, accountability, or override capability produce systematic harm at scale — directly relevant to the AI sidebar's argument that algorithmic governance must increase structural oversight as stakes increase.