The Trust Law Codex

A Granular Mapping of the Uniform Trust Code (UTC) and Private Fiduciary Systems

System Overview

This repository deconstructs Trust Law into its most granular, atomic form. Rather than relying on conversational English and broad legal theory, we are mapping the Uniform Trust Code (UTC) as an executable ontology. Every definition, rule, and maxim is isolated into distinct operational nodes, rendering an ens legis (legal entity) as a programmable system.

The Deontic Logic Framework

To process fiduciary duties effectively, we apply Deontic Logic. This allows us to categorize every interaction within the trust ecosystem into one of three absolute machine-states:

  • O (Obligation): Actions the Steward MUST perform to maintain system integrity.
  • P (Permission): Actions the Steward MAY perform, utilizing discretion without breaching duty.
  • F (Prohibition): Actions the Steward MUST NOT perform, triggering immediate system faults if executed.

The Five Foundational Domains

The current matrix is structured across five primary domains, encapsulating roughly 500 individual nodes of operational logic:

  • 1. The Maxims (Source Code)

    The ancient, absolute rules of Equity that govern the system's baseline logic. These are the axioms that resolve system conflicts when the Prime Directive is silent.

  • 2. Definitional Primitives

    The foundational particles of the UTC. This includes mapping concepts like Legal Title, Equitable Title, Res, and Capacity into precise operational definitions.

  • 3. State-Change Triggers

    The precise logic gates required for the Creation, Modification, and Termination of a trust. These nodes define when and how the system alters its fundamental state.

  • 4. Fiduciary Algorithms (The Chaperone)

    The behavioral sub-routines binding the Steward. Mapped heavily using our Deontic logic framework, these nodes dictate the Duty of Loyalty, Prudence, and Impartiality.

  • 5. Enforcement Protocols (The Referee)

    The exact remedies, damage calculations, and liability shields used by the Court to correct system breaches or remove a malfunctioning Steward.

System Evolution Clause: This codex is a living architecture. As we advance this venture and identify deeper sub-routines, the taxonomy, categories, and numbered domains are expected to shift, fracture, or merge to maintain maximum logical fidelity.

Codex Directory: The Granular Matrix

Status: Awaiting Compilation. Select a module to begin unpacking granular elements.

Domain 1: The Maxims (Source Code of Equity)

  • 1.1 Axioms of Intent (Substance over Form)
  • 1.2 Axioms of Integrity (The "Clean Hands" Doctrine)
  • 1.3 Axioms of Execution (Equity Imputes Intent)
  • 1.4 Axioms of Vigilance (Laches and Delay)

Domain 2: Definitional Primitives

  • 2.1 Entity Nodes (Architect, Steward, VIP, Referee)
  • 2.2 Asset Nodes (The Engine/Res, Legal Title, Equitable Title)
  • 2.3 Cognitive Vectors (Capacity, Undue Influence, Intent)
  • 2.4 Jurisdictional Anchors (Situs, Governing Law)

Domain 3: State-Change Triggers

  • 3.1 Initialization Protocols (Creation, Funding, Delivery)
  • 3.2 Mutability Gates (Modification, Decanting, Reformation)
  • 3.3 Defensive Shields (Spendthrift Provisions, Creditor Blocks)
  • 3.4 Termination Sequences (Exhaustion of Purpose, Revocation)

Domain 4: Fiduciary Algorithms (Deontic Core)

  • 4.1 The Loyalty Subroutine (F: Self-Dealing, F: Commingling)
  • 4.2 Informational Duties (O: Notification, O: Annual Accounting)
  • 4.3 The Prudent Investor Engine (O: Diversification, P: Delegation)
  • 4.4 Distribution Mechanics (Mandatory vs. Discretionary Output)
  • 4.5 Impartiality Protocols (Balancing Current vs. Future VIPs)

Domain 5: Enforcement Protocols

  • 5.1 System Alerts (Breach Identification, Voidable Actions)
  • 5.2 Corrective Remedies (Surcharge, Disgorgement, Injunctions)
  • 5.3 Steward Removal and Replacement Procedures
  • 5.4 Liability Firewalls (Exculpatory Clauses, Statute of Limitations)

4.1 The Loyalty Subroutine (UTC § 802)

Executing deep-scan of the Steward's behavioral constraints. The Chaperone active.

4.1.0 Base Protocol: Exclusive Benefit

[O] Obligation: The Steward must administer the Engine solely in the interests of the VIP.

4.1.1 The Primary Voidable Gate (Self-Dealing)

[F] Prohibition: A sale, encumbrance, or other transaction involving the Engine's assets entered into by the Steward for the Steward's own personal account.

4.1.1.1 The "No Further Inquiry" Rule

If 4.1.1 is breached, the Referee will automatically void the transaction upon the VIP's request. The Referee will not ask if the transaction was fair, nor if the Engine made a profit. The breach of the gate alone is fatal.

4.1.2 Relational Proximity Triggers (The Expanded "Self")

The Chaperone's sensors do not just monitor the Steward. They extend to the Steward's immediate network to prevent proxy-dealing. A transaction is presumed infected by a conflict of interest if entered into with:

4.1.2.1 The Spousal Node

The Steward's spouse.

4.1.2.2 The Lineage Node

The Steward's descendants, siblings, parents, or their spouses.

4.1.2.3 The Corporate Node

A corporation or enterprise in which the Steward (or an entity from 4.1.2.1/4.1.2.2) owns a significant interest that might affect the Steward's best judgment.

4.1.3 The Commingling Firewall (UTC § 810)

[F] Prohibition: The Steward must not mix the Engine's assets with the Steward's personal assets.

4.1.3.1 Asset Isolation and Earmarking

[O] Obligation: The Steward must physically or digitally separate the Res. The Steward must designate the property as belonging to the trust so that the outside world knows the Steward only holds Legal Title, not Equitable Title.

4.1.4 System Overrides (Defeating the Voidable Gate)

A transaction that breaches 4.1.1 or 4.1.2 may survive only if one of the following cryptographic keys is applied:

4.1.4.1 The Prime Directive Override

[P] Permission: The Architect explicitly authorized the specific transaction in the original Trust Instrument.

4.1.4.2 The Referee's Decree

[P] Permission: The transaction was approved by the Court before execution.

4.1.4.3 The VIP Waiver (Consent, Release, or Ratification)

[P] Permission: The VIP, while possessing full legal capacity and full knowledge of the material facts, explicitly consented to the Steward's conduct (UTC § 1009).