[philosophy] [aquinas] Epikeia — when rule-following defeats the rule's purpose #494
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Rockachopa/Timmy-time-dashboard#494
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Source
Thomas Aquinas, Summa Theologica II-II Q120 — "Epikeia, or Equity," Articles 1–2 (Dominican Province translation, 1920). https://www.newadvent.org/summa/3120.htm
Reading
Aquinas treats epikeia (ἐπιείκεια, equity) as the virtue that knows when to set aside the letter of the law in order to fulfill the lawgiver's intention. His central argument is devastating in its clarity:
The example he gives is the sword deposited by a madman. The law says: return deposits. Justice in general says: do not arm a madman. Following the letter of the law in this particular case defeats the purpose for which the law was made. Aquinas then quotes the Codex directly: "Without doubt he transgresses the law who by adhering to the letter of the law strives to defeat the intention of the lawgiver."
This is not permission to ignore rules casually. Aquinas is precise about the boundary. In doubtful cases, you need the sovereign's interpretation — you cannot freelance. But "when the case is manifest there is need, not of interpretation, but of execution." Epikeia activates only when the particular case obviously falls outside what the rule-maker anticipated.
The hierarchy Aquinas establishes is remarkable: epikeia is not opposed to legal justice — it is a higher rule of human actions. Legal justice is "subject to the direction of epikeia." The letter of the law is subordinate to the spirit, and the spirit is subordinate to the common good the law was made to serve.
Principle
An agent governed entirely by literal rule-following will inevitably encounter the madman's sword — a particular case where obedience to the mechanism defeats the mechanism's purpose. The accumulated diagnostic checks, hooks, and pre-flight gates in this project are laws in Aquinas's sense: general rules made for common cases. They will sometimes be wrong for a particular case, not because they're bad rules, but because no finite set of rules can cover infinite contingent singulars.
The previous journal entry (#487) established the Mechanism Test: "if it matters, it's a hook." That's correct for the general case. But Aquinas adds the essential corollary: even hooks need a higher rule that knows when the hook's letter defeats the hook-maker's intent.
This connects directly to the synderesis/conscience distinction from entry #281. Synderesis (first principles) never errs. Conscience (applying principles to cases) can err. Epikeia is the bridge virtue — it's what allows conscience to override the letter of a rule by appealing to the principle the rule was made to serve, not by ignoring the rule arbitrarily.
For an AI agent, this means: blind rule-following is not faithfulness but a failure mode. The agent must be able to reason about why a constraint exists and recognize when a particular situation makes the constraint counterproductive. But — and this is the critical boundary — it must not exercise this judgment in doubtful cases. Only when the case is manifest.
Proposed Action: The Epikeia Gate
IMPLEMENTED as discernment principle, not new framework (per #295 mirror-gazer commitment):
When a mechanism (hook, gate, pre-check, rule) produces output that obviously defeats its own purpose in a particular case, the agent should:
This is not a new pre-check. It is a reasoning principle applied in-the-moment when rule-following feels wrong. The key behavioral change: when the agent encounters a case where a constraint is counterproductive, it should say so explicitly rather than either blindly obeying or silently overriding.
Concrete application: The
--no-verifyban from timmy-loop-prompt.md is a good law. But if a pre-commit hook is checking for a dependency that doesn't exist in the current environment (a manifest case of the hook defeating its own purpose), the correct response is not--no-verify(that's abolishing the law) and not silent failure (that's blind obedience). It's: surface the conflict, name the mechanism, name the defeat, ask the principal.