<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Institutions on Moonment</title><link>https://moonment.net/en/tags/institutions/</link><description>Moon's notes on concepts, real projects, and reasoning open to review.</description><generator>Hugo</generator><language>en-US</language><managingEditor>Moon</managingEditor><webMaster>Moon</webMaster><copyright>© 2026 Moonment</copyright><lastBuildDate>Tue, 29 Sep 2026 13:55:00 +0800</lastBuildDate><atom:link href="https://moonment.net/en/tags/institutions/index.xml" rel="self" type="application/rss+xml"/><item><title>Rules and Principles: Reasons, Constraints, and Responsible Action</title><link>https://moonment.net/en/notes/rules-and-principles/</link><pubDate>Tue, 29 Sep 2026 11:08:00 +0800</pubDate><dc:creator>Moon</dc:creator><guid>https://moonment.net/en/notes/rules-and-principles/</guid><description>Rules state actionable requirements; principles supply reasons for creating, interpreting, and revising them. This essay separates norms, policies, standards, procedures, controls, and AI constraints.</description><content:encoded><![CDATA[<p>Rules and principles are both normative: they concern what may, must, or should be done. They differ mainly in the work they perform.</p>
<blockquote>
<p><strong>A rule specifies an actionable constraint under stated conditions. A principle supplies a reason or standard for making, interpreting, evaluating, and revising such constraints.</strong></p>
</blockquote>
<p>This is a functional distinction rather than a law of vocabulary. Legal systems, companies, technical standards, and ordinary speech often use <em>rule</em>, <em>principle</em>, <em>policy</em>, <em>standard</em>, and <em>norm</em> differently. The useful question is therefore not merely what a document calls something, but how that statement guides judgment and action.</p>
<h2 id="rules-reduce-the-available-actions">Rules reduce the available actions</h2>
<p>A practical rule often has a conditional structure:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">when condition C applies,
</span></span><span class="line"><span class="cl">agent S must, may, or must not perform action A
</span></span></code></pre></div><p>For example:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">If the user has not authorized disclosure,
</span></span><span class="line"><span class="cl">the system must not publish the user&#39;s private information.
</span></span></code></pre></div><p>A well-specified rule identifies:</p>
<ul>
<li>the agent or role to which it applies;</li>
<li>its triggering conditions;</li>
<li>the required, permitted, or prohibited conduct;</li>
<li>its jurisdiction or operational scope;</li>
<li>any recognized exceptions;</li>
<li>the evidence used to determine compliance;</li>
<li>the authority that enforces or changes it.</li>
</ul>
<p>Rules make coordination possible because they narrow the space of acceptable conduct. They reduce the need to reopen a foundational argument every time a recurring situation appears.</p>
<h2 id="regulative-constitutive-and-procedural-rules">Regulative, constitutive, and procedural rules</h2>
<p>Not every rule performs the same function.</p>
<table>
  <thead>
      <tr>
          <th>Kind of rule</th>
          <th>Function</th>
          <th>Example</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>regulative</td>
          <td>constrains conduct that can exist without the rule</td>
          <td>do not disclose private records</td>
      </tr>
      <tr>
          <td>constitutive</td>
          <td>helps create an activity or institutional status</td>
          <td>a ballot submitted under conditions C counts as a valid vote</td>
      </tr>
      <tr>
          <td>procedural</td>
          <td>specifies how an authorized result is produced</td>
          <td>two reviewers must approve publication</td>
      </tr>
      <tr>
          <td>classificatory</td>
          <td>determines how cases are counted or labeled</td>
          <td>a task counts as complete only with a completion event</td>
      </tr>
      <tr>
          <td>technical</td>
          <td>constrains system states or operations</td>
          <td>an unprivileged process cannot call an administrative tool</td>
      </tr>
  </tbody>
</table>
<p>The distinction between regulative and constitutive rules is central to social ontology. A regulative rule governs an antecedently intelligible activity, while a constitutive rule participates in defining what an institutional act is. A familiar form is:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">X counts as Y in context C
</span></span></code></pre></div><p>Games, contracts, elections, offices, and money all depend partly on rules that make certain moves, documents, or objects count as socially significant acts or statuses.<a href="https://plato.stanford.edu/entries/social-institutions/">Stanford Encyclopedia of Philosophy: Social Institutions</a></p>
<h2 id="principles-operate-as-reasons">Principles operate as reasons</h2>
<p>A principle is a comparatively general normative consideration. It tells decision-makers what should matter across a range of cases.</p>
<p>Examples include:</p>
<ul>
<li>equal cases should be treated alike;</li>
<li>exercises of power should be accountable;</li>
<li>restrictions should be necessary and proportionate;</li>
<li>claims should be answerable to evidence;</li>
<li>affected people should retain meaningful agency;</li>
<li>access should be limited to what a task requires.</li>
</ul>
<p>A principle can do several kinds of work:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">justify a family of rules
</span></span><span class="line"><span class="cl">guide interpretation when a rule is unclear
</span></span><span class="line"><span class="cl">identify a defect in an existing rule
</span></span><span class="line"><span class="cl">direct judgment in a case not yet covered
</span></span><span class="line"><span class="cl">provide a reason in conflicts among norms
</span></span></code></pre></div><p>A principle is therefore not simply a rule written at a higher level of abstraction. Its distinctive role is justificatory and evaluative.</p>
<h2 id="values-principles-policies-standards-and-procedures">Values, principles, policies, standards, and procedures</h2>
<p>These terms are often arranged as if every organization had one fixed hierarchy. Real systems are less tidy. A functional map is still useful:</p>
<table>
  <thead>
      <tr>
          <th>Element</th>
          <th>Main question</th>
          <th>Example</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>value</td>
          <td>What is worth protecting or pursuing?</td>
          <td>privacy matters</td>
      </tr>
      <tr>
          <td>principle</td>
          <td>What reason should guide judgment?</td>
          <td>personal data should remain under meaningful user control</td>
      </tr>
      <tr>
          <td>policy</td>
          <td>How will an institution govern this domain?</td>
          <td>data retention and access policy</td>
      </tr>
      <tr>
          <td>rule</td>
          <td>What is required, permitted, or forbidden?</td>
          <td>do not disclose data without authorization</td>
      </tr>
      <tr>
          <td>standard</td>
          <td>What threshold or specification counts as acceptable?</td>
          <td>encryption and response-time requirements</td>
      </tr>
      <tr>
          <td>procedure</td>
          <td>In what sequence is work performed?</td>
          <td>collect, review, authorize, publish</td>
      </tr>
      <tr>
          <td>control</td>
          <td>What prevents, detects, or records departures?</td>
          <td>access checks, logs, and automated scans</td>
      </tr>
  </tbody>
</table>
<p>The same normative idea can move through several layers:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">value: privacy is worth protecting
</span></span><span class="line"><span class="cl">principle: processing should preserve user control
</span></span><span class="line"><span class="cl">rule: disclosure requires authorization
</span></span><span class="line"><span class="cl">procedure: verify authorization before publication
</span></span><span class="line"><span class="cl">control: reject publication when the authorization record is absent
</span></span></code></pre></div><p>The label on a document does not settle its function. A “policy” may contain rules, principles, procedures, and standards in the same text.</p>
<h2 id="a-useful-distinction-not-an-absolute-dichotomy">A useful distinction, not an absolute dichotomy</h2>
<p>Rules and principles can be compared along several dimensions:</p>
<table>
  <thead>
      <tr>
          <th>Dimension</th>
          <th>Rule</th>
          <th>Principle</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>primary role</td>
          <td>constrain and coordinate conduct</td>
          <td>supply reasons and evaluative direction</td>
      </tr>
      <tr>
          <td>typical form</td>
          <td>condition plus requirement, permission, or prohibition</td>
          <td>a consideration that counts for or against a judgment</td>
      </tr>
      <tr>
          <td>application</td>
          <td>usually more determinate once conditions are established</td>
          <td>often requires interpretation and contextual judgment</td>
      </tr>
      <tr>
          <td>conflict</td>
          <td>resolved through scope, authority, priority, or exception</td>
          <td>resolved by assessing competing reasons in the case</td>
      </tr>
      <tr>
          <td>audit</td>
          <td>was the stated requirement followed?</td>
          <td>was the underlying reason adequately respected?</td>
      </tr>
      <tr>
          <td>revision</td>
          <td>changes with operations and evidence</td>
          <td>changes more slowly but remains open to criticism</td>
      </tr>
  </tbody>
</table>
<p>This contrast became especially influential in jurisprudence through Ronald Dworkin&rsquo;s criticism of rule-centered accounts of law. On his view, adjudication also invokes principles of justice, fairness, and due process that function as reasons within legal interpretation. The broader Hart–Dworkin debate concerns whether and how such moral considerations form part of law.<a href="https://plato.stanford.edu/entries/legal-positivism/">Stanford Encyclopedia of Philosophy: Legal Positivism</a></p>
<p>The distinction should not be exaggerated. Rules can be vague, defeasible, or sensitive to proportionality. Principles can be institutionalized as strong constraints. “Rule” and “principle” do not name two natural kinds whose members always behave identically.</p>
<h2 id="exceptions-require-governance">Exceptions require governance</h2>
<p>Rules cannot anticipate every circumstance. A new case may fall outside the original design, two rules may conflict, or literal compliance may defeat the reason for which the rule exists.</p>
<p>This does not grant every decision-maker a general license to invoke a principle and ignore a rule. A defensible exception should identify:</p>
<ol>
<li>why the case falls outside ordinary application;</li>
<li>which reason or principle is at stake;</li>
<li>why the existing rule produces an unacceptable result;</li>
<li>how the departure is limited to what is necessary;</li>
<li>who has authority to approve it;</li>
<li>how it will be recorded and reviewed;</li>
<li>whether the rule itself should be revised.</li>
</ol>
<p>Principles can justify exceptions, but accountable institutions turn those exceptions into an explicit process.</p>
<h2 id="principles-can-conflict">Principles can conflict</h2>
<p>Transparency, privacy, safety, autonomy, fairness, and efficiency may all be defensible principles. They do not always point in the same direction.</p>
<p>Full transparency can expose private information. Respect for individual choice can conflict with duties to protect people who cannot understand a serious risk. Uniform treatment can perpetuate disadvantages produced by unequal conditions.</p>
<p>Moral philosophy often uses <em>prima facie</em> or <em>pro tanto</em> duties to describe considerations that have genuine normative force but may be outweighed in a particular case. W. D. Ross&rsquo;s account is influential precisely because it does not treat every principle as absolute or assume that a fixed ranking mechanically resolves every conflict.<a href="https://plato.stanford.edu/entries/reasoning-moral/">Stanford Encyclopedia of Philosophy: Moral Reasoning</a></p>
<p>Reasoning through a conflict therefore requires more than naming two principles. It requires an account of:</p>
<ul>
<li>the people and interests affected;</li>
<li>the kind and magnitude of possible harm;</li>
<li>necessity and proportionality;</li>
<li>available alternatives;</li>
<li>decision authority;</li>
<li>residual duties such as explanation, compensation, or review.</li>
</ul>
<h2 id="compliance-legitimacy-and-effectiveness-are-separate">Compliance, legitimacy, and effectiveness are separate</h2>
<p>A rule can be followed perfectly and still produce a bad result.</p>
<p>The rule may rest on false assumptions, omit an affected group, reward a proxy rather than the real objective, or persist after its environment changes. Several locally reasonable rules can also interact to create a system-level failure.</p>
<p>Imagine a support center requiring every call to end within three minutes. The rule is measurable and consistently enforceable. Agents may meet it by ending difficult calls before the customer&rsquo;s problem is solved.</p>
<p>Four judgments must remain separate:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">compliance with the rule
</span></span><span class="line"><span class="cl">≠ legitimacy of the rule
</span></span><span class="line"><span class="cl">≠ effectiveness of the intervention
</span></span><span class="line"><span class="cl">≠ desirability of the outcome
</span></span></code></pre></div><p>Compliance evidence shows whether a requirement was followed. It does not by itself establish that the rule was justified, that it served its purpose, or that its effects were acceptable.</p>
<h2 id="principles-without-rules-rules-without-principles">Principles without rules, rules without principles</h2>
<p>Principles without operational rules invite inconsistent interpretation. Responsibility becomes difficult to audit, recurring questions are repeatedly reopened, and public commitments remain disconnected from actual behavior.</p>
<p>Rules without principles create a different failure. People optimize for literal compliance, new cases have no intelligible direction, and an expanding rulebook substitutes for judgment. “The procedure was followed” becomes an answer to questions about fairness, truth, or consequences.</p>
<p>A workable normative system joins several components:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">principles provide reasons and direction
</span></span><span class="line"><span class="cl">rules establish actionable boundaries
</span></span><span class="line"><span class="cl">procedures organize execution
</span></span><span class="line"><span class="cl">controls prevent and record departures
</span></span><span class="line"><span class="cl">feedback reveals effects
</span></span><span class="line"><span class="cl">revision changes rules when evidence warrants it
</span></span></code></pre></div><h2 id="from-principle-to-enforceable-system">From principle to enforceable system</h2>
<p>The security principle of least privilege provides a concrete example. NIST defines it as restricting users, or processes acting for them, to the minimum authorizations and resources needed to perform assigned functions.<a href="https://csrc.nist.gov/glossary/term/least_privilege">NIST CSRC: Least Privilege</a></p>
<p>That principle does not implement itself. It can generate rules and controls such as:</p>
<ul>
<li>administrative access is denied by default;</li>
<li>elevated access expires after a stated interval;</li>
<li>ordinary work uses non-privileged accounts;</li>
<li>privileged actions are logged;</li>
<li>roles receive only the transactions required for their duties.</li>
</ul>
<p>The principle explains the direction and the threat model. Rules specify the constraints. Access-control mechanisms enforce them. Audit logs provide evidence. Incident reviews test whether the design was effective.</p>
<h2 id="rules-and-principles-in-ai-systems">Rules and principles in AI systems</h2>
<p>A language model produces plausible continuations from probability distributions. Plausibility does not guarantee truth, logical validity, authorization, or acceptable consequences.</p>
<p>An AI system therefore needs a path from normative reason to technical enforcement:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">principle: system action must remain within user authority
</span></span><span class="line"><span class="cl">rule: no external write without explicit authorization
</span></span><span class="line"><span class="cl">control: reject tool calls lacking an authorization state
</span></span><span class="line"><span class="cl">verification: inspect the target identity and observed result
</span></span><span class="line"><span class="cl">record: preserve an auditable action log
</span></span></code></pre></div><p>Other executable rules may include:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">identity unresolved → stop
</span></span><span class="line"><span class="cl">evidence unavailable → mark unknown
</span></span><span class="line"><span class="cl">validation failed → do not claim success
</span></span><span class="line"><span class="cl">irreversible effect → require stronger review
</span></span></code></pre></div><p>Principles remain necessary because no finite rule set anticipates every context. They can guide how a novel case is escalated, how uncertainty is represented, and which harms should be minimized. But a model that writes a persuasive explanation of a principle has not thereby complied with it. Reliable constraint requires permissions, schemas, tool boundaries, validation, logs, and human accountability.</p>
<h2 id="designing-a-rule-and-principle-system">Designing a rule-and-principle system</h2>
<h3 id="identify-what-is-at-stake">Identify what is at stake</h3>
<p>Name the affected people, protected values, intended outcomes, possible harms, and responsible authority.</p>
<h3 id="state-a-small-set-of-principles">State a small set of principles</h3>
<p>A principle should explain a family of judgments. Renaming every instruction as a principle only hides the operational work.</p>
<h3 id="derive-rules-with-complete-conditions">Derive rules with complete conditions</h3>
<p>For each rule, specify:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">subject or role
</span></span><span class="line"><span class="cl">+ trigger
</span></span><span class="line"><span class="cl">+ requirement, permission, or prohibition
</span></span><span class="line"><span class="cl">+ scope
</span></span><span class="line"><span class="cl">+ exception
</span></span><span class="line"><span class="cl">+ evidence
</span></span><span class="line"><span class="cl">+ authority
</span></span></code></pre></div><h3 id="implement-procedures-and-controls">Implement procedures and controls</h3>
<p>Important rules should appear in checklists, access controls, validation code, review workflows, and audit records rather than relying on memory alone.</p>
<h3 id="evaluate-different-layers-separately">Evaluate different layers separately</h3>
<p>Ask:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">Was the rule followed?
</span></span><span class="line"><span class="cl">Did the rule adequately serve its principle?
</span></span><span class="line"><span class="cl">Did the intervention achieve its objective?
</span></span><span class="line"><span class="cl">What side effects appeared?
</span></span></code></pre></div><h3 id="create-a-revision-path">Create a revision path</h3>
<p>Repeated exceptions usually signal an incomplete rule, a changed environment, or an unresolved conflict of principles. Revision should be governed rather than improvised.</p>
<h2 id="conclusion">Conclusion</h2>
<p>Rules and principles belong to the same normative architecture but perform different jobs.</p>
<blockquote>
<p><strong>Rules state actionable requirements, permissions, and prohibitions under defined conditions. Principles provide the reasons and standards used to create, interpret, evaluate, and revise those rules.</strong></p>
</blockquote>
<p>Their relationship can be summarized as:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">principles guide judgment
</span></span><span class="line"><span class="cl">→ rules constrain action
</span></span><span class="line"><span class="cl">→ procedures and controls implement rules
</span></span><span class="line"><span class="cl">→ outcomes test effectiveness
</span></span><span class="line"><span class="cl">→ feedback supports interpretation and revision
</span></span></code></pre></div><p>Rules cannot replace principles because no rulebook covers every future case or justifies its own authority. Principles cannot replace rules because general reasons do not produce consistent, auditable conduct by themselves.</p>
<p>A responsible system must explain both why a consideration matters and who must do what under which conditions. It must then examine actual consequences rather than treating either noble language or formal compliance as the end of judgment.</p>
<h2 id="references">References</h2>
<ul>
<li><a href="https://plato.stanford.edu/entries/social-institutions/">Stanford Encyclopedia of Philosophy: Social Institutions</a></li>
<li><a href="https://plato.stanford.edu/entries/legal-positivism/">Stanford Encyclopedia of Philosophy: Legal Positivism</a></li>
<li><a href="https://plato.stanford.edu/entries/reasoning-moral/">Stanford Encyclopedia of Philosophy: Moral Reasoning</a></li>
<li><a href="https://plato.stanford.edu/entries/ethics-deontological/">Stanford Encyclopedia of Philosophy: Deontological Ethics</a></li>
<li><a href="https://csrc.nist.gov/glossary/term/least_privilege">NIST CSRC: Least Privilege</a></li>
</ul>
]]></content:encoded></item><item><title>Games and Game Theory: Strategy, Equilibrium, and Institutions</title><link>https://moonment.net/en/notes/game-and-game-theory/</link><pubDate>Sat, 12 Sep 2026 22:03:10 +0800</pubDate><dc:creator>Moon</dc:creator><guid>https://moonment.net/en/notes/game-and-game-theory/</guid><description>A game is a model of interdependent choice. This guide explains strategies, best responses, Nash equilibrium, cooperation, and the limits of formal rationality.</description><content:encoded><![CDATA[<p>Game theory uses the word <em>game</em> in a broader sense than ordinary recreation. A game is any modeled situation in which the result of one agent’s choice depends on what other agents choose.</p>
<p>That is why pricing, bargaining, voting, traffic, military deterrence, shared resources, and workplace coordination can all be studied as games. They need not be playful, and they need not have a single winner. Their common structure is <strong>strategic interdependence</strong>.</p>
<blockquote>
<p><strong>In a strategic interaction, I cannot evaluate my action without considering how others may act and respond.</strong></p>
</blockquote>
<h2 id="from-play-to-a-formal-model">From play to a formal model</h2>
<p>The English word <em>game</em> has long referred to play, amusement, contest, and structured activity. Game theory abstracts from these familiar cases. It keeps the elements that make strategic reasoning possible—participants, permitted moves, information, consequences, and rules—while discarding the requirement that the situation be entertainment. <a href="https://www.merriam-webster.com/dictionary/game">Merriam-Webster: game</a></p>
<p>The abstraction is useful because the same strategic pattern can appear in very different settings. Two firms choosing prices, two governments considering an agreement, and two drivers approaching a narrow bridge may face structurally similar problems even though the subject matter differs.</p>
<p>The “game” is therefore not the social event itself in all its richness. It is a representation designed to isolate interdependent choice.</p>
<h2 id="a-decision-problem-becomes-a-game-when-another-agent-responds">A decision problem becomes a game when another agent responds</h2>
<p>Choosing whether to carry an umbrella is mainly a decision under uncertainty. The weather affects the outcome, but it does not observe your choice and revise its plan.</p>
<p>Negotiating a salary is different. The employer can infer how urgently you need the offer, conceal its limit, respond to your counteroffer, and change tactics when you change yours.</p>
<p>This gives a practical boundary:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">Decision theory: choose under uncertainty about the world.
</span></span><span class="line"><span class="cl">Game theory: choose under uncertainty about responsive agents.
</span></span></code></pre></div><p>Real problems can involve both. A company deciding whether to enter a market faces uncertain demand and strategic responses from competitors. Game theory does not remove ordinary uncertainty; it adds other decision-makers to it.</p>
<h2 id="the-anatomy-of-a-game">The anatomy of a game</h2>
<p>A formal game specifies enough structure to compare strategies.</p>
<table>
  <thead>
      <tr>
          <th>Element</th>
          <th>Question</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Players</td>
          <td>Who can make relevant choices?</td>
      </tr>
      <tr>
          <td>Actions</td>
          <td>What can each player do at a particular point?</td>
      </tr>
      <tr>
          <td>Strategies</td>
          <td>What complete plan governs a player’s choices?</td>
      </tr>
      <tr>
          <td>Information</td>
          <td>What does each player know when choosing?</td>
      </tr>
      <tr>
          <td>Outcomes</td>
          <td>What follows from the combined choices?</td>
      </tr>
      <tr>
          <td>Preferences or payoffs</td>
          <td>How does each player rank the outcomes?</td>
      </tr>
      <tr>
          <td>Timing and rules</td>
          <td>Who moves when, and which commitments can be enforced?</td>
      </tr>
  </tbody>
</table>
<p>An <strong>action</strong> is a move. A <strong>strategy</strong> is a plan specifying what to do in every relevant situation. “Lower the price today” is an action. “Match any rival’s price cut, otherwise hold” is a strategy.</p>
<p>A payoff need not be money. It represents how a player ranks outcomes within the model. Safety, fairness, reputation, loyalty, risk, and the welfare of other people can all affect that ranking. Modeling an agent as payoff-maximizing does not by itself imply selfishness; it says that the model represents the agent as choosing according to an ordering of outcomes.</p>
<h2 id="best-responses-and-nash-equilibrium">Best responses and Nash equilibrium</h2>
<p>A strategy is a <strong>best response</strong> when it gives a player the most preferred available result given what the other players are doing.</p>
<p>A Nash equilibrium is a profile of strategies in which every player’s strategy is a best response to the others. No player can improve their modeled payoff by changing strategy alone while everyone else stays fixed.</p>
<p>This is a stability condition:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">Given what everyone else is doing,
</span></span><span class="line"><span class="cl">does any one player benefit by deviating alone?
</span></span></code></pre></div><p>If the answer is no for every player, the profile is a Nash equilibrium.</p>
<p>Nash showed that every finite game has at least one equilibrium when mixed strategies—probability distributions over pure strategies—are allowed. <a href="https://doi.org/10.1073/pnas.36.1.48">John F. Nash Jr., “Equilibrium Points in N-Person Games”</a></p>
<p>Existence does not tell us which equilibrium people will reach, whether they know the game, or whether the equilibrium is desirable.</p>
<h2 id="the-prisoners-dilemma-separates-stability-from-collective-value">The prisoner’s dilemma separates stability from collective value</h2>
<p>Suppose two players can cooperate or defect. Higher numbers are preferred:</p>
<table>
  <thead>
      <tr>
          <th></th>
          <th style="text-align: right">B cooperates</th>
          <th style="text-align: right">B defects</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td><strong>A cooperates</strong></td>
          <td style="text-align: right">3, 3</td>
          <td style="text-align: right">0, 5</td>
      </tr>
      <tr>
          <td><strong>A defects</strong></td>
          <td style="text-align: right">5, 0</td>
          <td style="text-align: right">1, 1</td>
      </tr>
  </tbody>
</table>
<p>For each player, defection produces a higher payoff regardless of what the other does. Both therefore defect and receive <code>1</code>, even though mutual cooperation would give each <code>3</code>.</p>
<p>The result is not a claim that people are naturally selfish. It follows from a particular arrangement of choices and payoffs. Change the possibility of repeated interaction, reputation, monitoring, communication, or enforcement and the strategic structure changes.</p>
<p>The model reveals a general possibility:</p>
<blockquote>
<p><strong>Choices that are individually defensible within a set of rules can combine into an outcome every participant ranks below another feasible outcome.</strong></p>
</blockquote>
<p>That shifts attention from blaming individuals to examining institutions.</p>
<h2 id="information-commitment-and-credibility-change-the-game">Information, commitment, and credibility change the game</h2>
<p>Strategy depends on what players know and what they can credibly promise.</p>
<p>A threat matters only if carrying it out would remain rational when the time comes. A promise matters only if the other side expects compliance. Cheap statements without costs or enforcement may fail to change beliefs.</p>
<p>Several institutional mechanisms can alter behavior:</p>
<ul>
<li>repeated interaction makes future retaliation or reward relevant;</li>
<li>reputation carries information across encounters;</li>
<li>contracts change the consequences of breaking a promise;</li>
<li>transparency changes what can be observed;</li>
<li>voting rules change which coalitions matter;</li>
<li>property rights change the payoff structure around a shared resource.</li>
</ul>
<p>The point is not that every institution improves outcomes. It is that rules are part of the game. What appears to be a fixed conflict between personalities may be produced or intensified by incentives, information, and enforceability.</p>
<h2 id="rationality-inside-the-model-is-conditional">Rationality inside the model is conditional</h2>
<p>Game theory commonly uses instrumental rationality: choose an effective means to an end, given beliefs about others and the available strategies.</p>
<p>This form of rationality does not determine which ends are worth pursuing. It also does not guarantee accurate beliefs, complete information, unlimited computation, or freedom from bias.</p>
<p>A strategy can be instrumentally rational relative to a cruel objective. A cooperative strategy can also be rational if the agent values fairness, relationship, or long-term trust. The mathematics operates on the preferences represented in the model; it does not supply those preferences from outside.</p>
<p>Behavioral and experimental work further shows that real people use heuristics, punish unfairness, reciprocate, misperceive probabilities, and differ in how they understand the situation. These findings do not make formal game theory useless. They clarify when its assumptions approximate behavior and when the model needs enrichment.</p>
<h2 id="equilibrium-is-not-efficiency-consent-or-justice">Equilibrium is not efficiency, consent, or justice</h2>
<p>An equilibrium can be wasteful, coercive, unequal, or sustained by fear. Stability against unilateral deviation establishes none of the following:</p>
<ul>
<li>that total welfare is maximized;</li>
<li>that the distribution is fair;</li>
<li>that the rules are legitimate;</li>
<li>that participation is voluntary;</li>
<li>that no better institution exists.</li>
</ul>
<p>Ethics and political philosophy therefore use game theory in at least two ways. It can explain how norms and institutions emerge or remain stable. It can also contribute to arguments about which institutions people could justify. But an explanatory equilibrium does not become a moral justification merely because it is mathematically stable. <a href="https://plato.stanford.edu/entries/game-ethics/">Stanford Encyclopedia of Philosophy: Game Theory and Ethics</a></p>
<h2 id="models-clarify-by-leaving-things-out">Models clarify by leaving things out</h2>
<p>A useful game makes assumptions explicit. That is also its limitation.</p>
<p>The result may change when the model changes:</p>
<ul>
<li>players may misunderstand one another;</li>
<li>preferences may be unstable or socially formed;</li>
<li>identities and relationships may matter;</li>
<li>power may determine which actions are available;</li>
<li>rules may be disputed rather than fixed;</li>
<li>the relevant game may be embedded in a larger game;</li>
<li>people may change the institution instead of optimizing within it.</li>
</ul>
<p>Game theory is strongest when it identifies the consequences of a specified strategic structure. It is weaker when a simplified payoff table is treated as a complete description of human motivation or political legitimacy.</p>
<h2 id="a-practical-way-to-analyze-strategic-interaction">A practical way to analyze strategic interaction</h2>
<p>When a problem feels like a “game,” ask:</p>
<ol>
<li>Who can respond to whom?</li>
<li>Which actions and strategies are actually available?</li>
<li>What does each participant know or believe?</li>
<li>Which outcomes does each participant prefer, and how do we know?</li>
<li>Which promises or threats are credible?</li>
<li>Is the interaction repeated?</li>
<li>What equilibrium or pattern is stable under the current rules?</li>
<li>Is that stable result efficient, fair, or legitimate?</li>
<li>Which rule change would produce a different game?</li>
</ol>
<p>The final question is often the most useful. Game theory does more than advise a player inside a fixed contest. It can show why changing the rules may matter more than choosing a cleverer move.</p>
<h2 id="sources">Sources</h2>
<ul>
<li><a href="https://plato.stanford.edu/entries/game-theory/">Stanford Encyclopedia of Philosophy: Game Theory</a></li>
<li><a href="https://plato.stanford.edu/entries/game-ethics/">Stanford Encyclopedia of Philosophy: Game Theory and Ethics</a></li>
<li><a href="https://doi.org/10.1073/pnas.36.1.48">John F. Nash Jr., “Equilibrium Points in N-Person Games”</a></li>
<li><a href="https://www.merriam-webster.com/dictionary/game">Merriam-Webster: game</a></li>
</ul>
]]></content:encoded></item></channel></rss>