Institutions, Law, and Power

By the end of this lesson, you will be able to...

• Design an institution around a promise, a scarce resource, a decision boundary, and a visible failure mode.

• Compare institutional alternatives by incentives, legitimacy, enforcement, speed, and who gains power.

• Explain how a law becomes meaningful only when people can obey, evade, challenge, or enforce it.

Idea in one sentence: An institution is a repeated way of making important decisions, distributing costs, and earning or forcing cooperation.

Core Insight

Imagine Nima after the material flow from the previous lesson: its water is not an object sitting in a warehouse. It moves through a valley, filters, routines, and a fragile marsh.

Now the city faces a social question: who decides which district receives water first when the next collection is smaller than expected?

The answer cannot be only a name on a building. “The Cistern Authority” sounds official, but the name does not tell us who controls the gates, why households cooperate, what happens when someone cheats, or how a family can challenge a bad decision.

Institutions make pressure repeatable. They turn a recurring problem into roles, rules, records, incentives, decisions, and consequences.

The Promise We Need to Keep

Start with the promise, not the title.

Nima needs a water arrangement that can do four things:

• allocate a limited flow during the six-hour collection window
• protect the marsh that makes filtering possible
• make emergency decisions when a pipe or cistern fails
• give households enough evidence to believe the arrangement is not simply favoritism

This promise creates a design boundary. The institution does not need to solve every conflict in Nima. It needs to make water decisions predictable enough to coordinate and flexible enough to respond to a damaged cycle.

Plain meaning:

An institution is a durable arrangement for making a recurring decision.

In Nima:

The arrangement decides who opens which gate, when reserves may be used, and how a household can object.

Technical names:

• A rule states what should happen.
• An incentive changes what people gain or lose by following a choice.
• Legitimacy is the reason people accept a decision as rightful enough to obey, even when they dislike the result.
• Enforcement changes the cost of breaking a rule.
• Power is the ability to shape decisions, access, records, or consequences.

These are not five decorative labels. They are five questions about whether the institution can keep its promise.

The Naive Design: Give the Problem a Name

The first design is a single official called the First Cistern Keeper. The Keeper announces the order, holds the keys, and decides exceptions.

This is attractive. One person can act quickly. Everyone knows where to go. During a calm cycle, the arrangement may appear to work.

Then the Keeper's district receives a cracked pipe. The Keeper moves that district to the front of the next collection. The decision may be reasonable, but nobody can inspect the damage report. A rival district sees only favoritism. A law exists, but the institution has no independent record, appeal, or reason to trust the exception.

The failure is not “one person is evil.” The failure is concentrated power with weak evidence and no correction path.

Check: Which part is missing from this rule: “The Keeper may change the order during emergencies”?

Think first, then reveal.

Answer: The rule has an emergency power but no definition of emergency, evidence requirement, time limit, or appeal. It gives discretion without a visible boundary. That can be useful in a real crisis, but it also makes capture easy.

Design the Institution as a System

Use this sequence:

recurring pressure
  -> public promise
  -> decision boundary
  -> roles and resources
  -> rules and incentives
  -> legitimacy and enforcement
  -> failure and correction

Recurring pressure

What problem comes back often enough to need an arrangement?

Nima's collection window, unequal pipe pressure, and marsh recovery repeat every cycle. A one-time argument may need a judgment; a repeating allocation problem needs an institution.

Public promise

What should people be able to expect?

“Every district receives a measured share, emergency reserves protect survival, and the reasons for exceptions are recorded.” This promise is specific enough to test.

Decision boundary

Which decisions belong to the institution, and which remain with households or other groups?

The council may set gate order and reserve rules. It should not decide how every household cooks, prays, or repairs a private cup. A broad institution becomes intrusive; a narrow one cannot keep its promise.

Roles and resources

Who acts, and what can they control?

Nima needs gate operators, marsh stewards, record keepers, district delegates, and a small reserve store. The operator controls a gate. The record keeper controls evidence. The steward controls access to a recovering marsh. Power appears wherever a role can delay, deny, hide, or redirect a resource.

Rules and incentives

What happens by default, and why would people follow it?

The schedule may rotate priority between districts. A household that reports a leak receives repair credit, while a household that hides a private intake loses priority in the next cycle. The rule is not only text; it changes payoffs.

Legitimacy and enforcement

Why accept the rule, and what happens when someone refuses?

Legitimacy can come from representation, visible measurements, an old oath, successful results, or a process people recognize as fair. Enforcement may be a fine, loss of priority, public review, physical control of a gate, or removal from a role. A punishment without acceptance creates fear; acceptance without any consequence creates a suggestion.

Failure and correction

What happens when the institution is wrong, captured, slow, or surprised?

Nima needs an appeal window, an emergency expiry, a second reader for measurements, and a rule for replacing a corrupt gate operator. Correction is part of the design, not an admission that the institution failed to be perfect.

Compare Three Alternatives

The same promise can produce different institutions.

There is no universally best design. The third option fits Nima's promise if the city can pay the coordination cost. During an immediate pipe collapse, the Keeper may still act first, but the emergency rule should expire and leave evidence for review.

The design trade-off is speed versus legitimacy and correction. Central power can move quickly. Distributed participation can expose error and distribute voice. Neither is free.

A Worked Trace: The Short Collection

Suppose the next valley crossing brings only half the expected water.

The naive design says, “The Keeper chose who deserved water.” The designed institution says, “A measured condition triggered a bounded procedure, people could inspect the evidence, and the exception had an end.”

So far, the important shift is from organizations as nouns to institutions as repeated decision systems. The system has inputs, roles, rules, incentives, evidence, and correction.

Law, Legitimacy, and Power Are Different

These concepts often collapse into “the government.” Keep them separate.

A law is a stated rule. It can be clear and still ignored.

Legitimacy explains why obedience feels justified, necessary, or less costly than refusal. A law can be legal but lose legitimacy after a hidden exception.

Power is not only a throne. The person who controls the gauge, schedule, archive, gate, or appeal may shape outcomes without holding the title.

For Nima, ask:

• Who writes the water charter?
• Who measures the flow?
• Who stores the records?
• Who can grant an exception?
• Who can challenge the measurement?
• Who pays when the rule is enforced unevenly?

These questions reveal the institution's actual structure. Titles can hide power; procedures expose it.

Common Confusions

Confusion: A building is an institution

Why it is tempting:

Buildings are easy to draw and name.

Better model:

The institution is the repeated arrangement of roles, decisions, resources, and consequences. The building may host it, but it does not make the arrangement work.

Confusion: A law creates behavior by itself

Why it is tempting:

Written rules look complete.

Better model:

Ask who knows the rule, who benefits from it, who can evade it, who enforces it, and what happens when enforcement is challenged.

Confusion: Legitimacy means everyone agrees

Why it is tempting:

An accepted institution can look unanimous from a distance.

Better model:

Legitimacy means enough people recognize a decision process as rightful or unavoidable to keep cooperating. Disagreement can remain visible inside a legitimate process.

Confusion: More representation always makes an institution fairer

Why it is tempting:

More voices can correct blind spots.

Better model:

Representation adds information and legitimacy, but it also costs time and can be captured by organized groups. Design the correction path, not only the number of seats.

Check the Boundary

Check: Nima's council publishes a perfect water schedule, but only the upper district can read the clock and access the archive. Is the institution transparent?

Think first, then reveal.

Answer: No. A public rule is not usable evidence when access is unequal. The institution may need shared markers, delegated readers, oral announcements, or an appeal process that lower districts can actually reach.

Practice: Design a Repeating Arrangement

Return to the Glass Orchard from the previous lessons:

Fruit becomes poisonous one hour after it is picked. Merchants want to sell it in distant towns, but preservation work is limited.

Design a small institution in six moves:

1. State the public promise.
2. Name the scarce resource or decision it controls.
3. Define one default rule and one incentive.
4. Give it a source of legitimacy.
5. Add enforcement and an appeal path.
6. Name one failure signal showing capture, delay, or unequal access.

One model answer:

The Orchard Bell Guild promises that harvested fruit will be preserved in a safe order rather than sold to the most powerful merchant. It controls the harvest bells and preservation ovens. Crews rotate by orchard block; a crew that records spoiled batches loses priority for the next market day. The guild is legitimate because each village sends a delegate and the bell records remain public. A merchant who jumps the queue loses access for one cycle, while a grower can appeal a contaminated oven test to a second crew. If the same merchant's fruit is always tested first, the institution is being captured.

The guild does not eliminate conflict. It makes conflict inspectable. That is what an institution can do.

What Comes Next

Nima now has a way to turn material pressure into rules, roles, evidence, and contested authority. The next lesson asks what happens when technology or magic adds a new capability, cost, access pattern, or failure mode to this institutional landscape.

Resources

• [BOOK] Wonderbook - Focus: visual prompts that make social arrangements and consequences concrete.
• [BOOK] The Kobold Guide to Worldbuilding - Focus: practical questions about institutions, power, and conflict in invented worlds.
• [ARTICLE] Worldbuilding Stack Exchange - Focus: competing institutional designs and their failure modes; evaluate answers critically.

Key Takeaways

• An institution is a repeated decision arrangement, not just a building, title, or organization name.
• Design from a promise through boundaries, roles, resources, rules, incentives, legitimacy, enforcement, and correction.
• Power appears wherever someone can control access, evidence, timing, exceptions, or consequences.
• Faster central decisions can cost legitimacy and correction; broader participation can cost time and coordination.
• A useful institution does not remove conflict. It makes decisions and failures visible enough to contest.