Incomplete Contract¶
Core Idea¶
An incomplete contract is a rule-set that deliberately leaves some contingencies unspecified — knowing exhaustive enumeration is impossible — and designates some other mechanism to fill the gap when the unspecified case arises. Its signature is gap + gap-handler + governance of the handler: the unwritten zone, the rule or person that activates in it, and the constraint that keeps that discretion honest.
How would you explain it like I'm…
The On-Purpose Blank
Imagine making a deal with a friend but you can't list every single thing that might happen. So you agree, 'If something weird comes up that we didn't plan, we'll let Mom decide.' You leave a blank on purpose and say who fills it in later. That's smarter than pretending you thought of everything.
Honest About The Future
An incomplete contract is a set of rules that on purpose leaves some 'what ifs' unwritten, because nobody can list every possible future. Instead of pretending the agreement covers everything, it names a backup plan for the gaps — like a trusted person who decides, or a default rule that kicks in. This isn't a bad or sloppy contract; it's an honest one that admits we can't see the whole future. The key parts are the gap (the unwritten zone), a gap-handler (whoever or whatever decides when you hit the gap), and a way to keep that handler from abusing their power.
Gap And Gap-Handler
An incomplete contract is a rule-set that deliberately leaves some contingencies unspecified, knowing that listing every possibility is impossible, too costly, or unenforceable, and that some other mechanism will fill the gap when an unplanned situation arises. That filling mechanism can be residual control rights, renegotiation, default doctrines, a trusted arbiter, norms, or good faith. It differs from 'a contract with mistakes' in three ways: bounded foresight (the future is too big to enumerate), a verifiability gap (some things like effort or intent are too hard for an outsider to confirm, so writing them in is pointless), and designed residual authority (it specifies WHO decides when the unplanned case arises, even if not WHAT they'll decide). So the structural signature is gap + gap-handler + governance of the handler. Reading any agreement as 'this part is specified, this part is left to a handler, and this is how the handler is held to account' is the move the concept gives you.
An incomplete contract is the structural pattern of a rule-set that deliberately leaves some contingencies unspecified, in the knowledge that exhaustive enumeration is impossible, prohibitively costly, or unenforceable, and that some other mechanism — residual control rights, renegotiation, default doctrines, trusted arbiters, norms, or good faith — will fill the gap when the unspecified contingency arises. The defining commitment is the acknowledged gap PLUS a gap-filling regime: incomplete contracts are not bad contracts but honest ones about the limits of foresight, language, verifiability, or enforcement. Three features distinguish it from 'a contract with mistakes.' Bounded foresight: the parties recognize the space of future states is too large or uncertain to specify exhaustively. Verifiability gap: even when a contingency can be described, some variables — effort, intent, quality, future value — are hard for a third party to observe, so writing them in is pointless without an oracle. Designed residual authority: the contract specifies who decides when the unspecified case arises, even if it cannot specify what they will decide. The structural signature is therefore gap + gap-handler + governance of the handler — the gap is the unwritten zone, the handler is the rule, person, doctrine, or norm that activates when the zone is entered, and the governance is whatever constrains the handler from abusing the discretion. The move the prime supplies is reading any rule-set as 'this part is specified, this part is left to a handler, this is how the handler is held to account.' That move is abstractly general, but the prime's vocabulary and theory are deeply law-and-economics-bound, and its non-human instances arrive largely as analogies, which is why it sits at the framed end of the spectrum.
Broad Use¶
- Contract theory: the transaction-cost origin of incomplete contracts and ownership as residual control rights.
- Law: constitutional vagueness ("due process," "reasonable") delegating gap-filling to courts; common-law evolution.
- Diplomacy: constructive ambiguity — deliberate vagueness that secures agreement despite irreconcilable preferences.
- Organizations: open-ended employment where the employer holds residual decision rights over unnamed tasks.
- Software: specifications that intentionally underspecify (side-effect ordering, malformed input), relying on a runtime or compiler.
- AI alignment: reward functions and prompts as incomplete specifications whose handlers are learned priors and fallback rules.
Clarity¶
Shifts the question from "did we write down enough?" — a losing race — to "who handles the gap, and how is that handler constrained?", exposing the hidden completeness premise in naive specification.
Manages Complexity¶
Replaces the impossible task of specifying every contingency with the bounded task of designing the gap-handler — one design problem instead of infinitely many.
Abstract Reasoning¶
Lets one ask of any rule-set: where is it deliberately silent, who decides in that silence, and what holds that decider to account — with hold-up, capture, and overreach as the forecast failure modes.
Knowledge Transfer¶
- Public-works contracting: a 30-year concession sets gap location, a regulatory adjustment commission as handler, and state-board review as governance — the same three knobs as an API versioning policy.
- API design: a versioning policy plus a breaking-change committee plus an RFC process instantiates gap, handler, and governance.
- AI deployment: a reward function plus fine-tuning plus an oversight board runs the identical structure.
Example¶
In the Grossman–Hart–Moore theory of the firm, ownership is residual control rights — the authority to decide whatever the contract left open — and the fix is to assign that control to the party whose non-contractible investment matters most, so hold-up does least damage.
Relationships to Other Primes¶
Parents (1) — more general patterns this builds on
- Incomplete Contract is a kind of Contract — An incomplete contract is, structurally, a contract (a rule-set fixing outcomes for some contingencies) plus the distinctive move of an acknowledged gap + designated gap-handler + governance. contract is the canonical genus; incomplete_contract is the specific kind that deliberately leaves gaps. Phase-C already records the link to contract. The file severs it from interface (complete contract over its cases), delegation (only the decision-right piece), and optionality (a held right) — none is the genus; contract is. Good conviction: the is-a holds even though the prime is heavily framed (law/econ), because every instance is literally a contract or rule-set.
Path to root: Incomplete Contract → Contract → Interface → Boundary
Not to Be Confused With¶
- Incomplete Contract is not an Interface because an interface specifies a complete contract over the cases it covers (any case outside it is simply not a legal call), whereas an incomplete contract admits cases it does not cover and routes them to a handler with discretion.
- Incomplete Contract is not Authority Delegation Under Uncertainty because delegation hands a decision right to an agent within a scope, whereas an incomplete contract is the broader structure — gap, plus handler, plus governance of the handler — of which a delegated right is one gap-handling mechanism.
- Incomplete Contract is not Optionality because optionality is a held right to act later, whereas an incomplete contract's gap is not anyone's option — it is an unspecified zone someone is empowered to resolve when it arises.