Skip to content

Commitment

Version
v1 · 2026-08-24 · History
Prime #
711
Origin domain
Philosophy
Subdomain
speech act theory → Philosophy

Core Idea

A commitment is the creation of a new constraint on future behavior by an act in the present — a speech act, signature, deposit, or irreversible step — that demarcates a before (the agent was free) from an after (the agent is bound) that others build on.

How would you explain it like I'm…

The Pinky Swear

A commitment is when you promise to do something, and now people count on you doing it. Before you promise, you're free to do anything; after you promise, you're tied to your word. A pinky-promise is small, but a written-and-signed promise is big and hard to take back.

Tying Yourself Down

A commitment is when you bind yourself now to do something later, or to stand behind something being true. You do an act in the present — a promise, a signature, putting money down — and that act creates a new rule on your future behavior. It splits time into a 'before,' when you were free, and an 'after,' when you're bound. The point is that other people can rely on it: they make plans, lend things, or depend on your word because you've tied yourself down.

Before-and-After Binding

A Commitment is a state in which an agent has bound itself to a future action, or to the truth of a claim, in a way others can rely on. The defining move is self-referential: an act in the present creates a new constraint on future behavior — a promise, a signature, a deposit, an irreversible step. That act marks a 'before' (free) and an 'after' (bound), and the bind is what others build on when they extend credit or make plans. Commitments also vary along two independent axes: strength (how hard the bind, what penalty on breach) and visibility (who can see it). A casual verbal promise and a notarized contract both bind, but very differently. The structural questions are: what is bound, to whom, how visibly, under what release conditions, with what penalty?

 

A Commitment is a structural state in which an agent has bound itself to a future course of action, or to the truth of a proposition, in a way that downstream behavior, accountability, and counterfactual reasoning can rely on. The defining commitment — the term is self-referential here — is the creation of a new constraint on future behavior by an act in the present: a speech act, a signature, a registration, a deposit, or an irreversible operational step. The act demarcates a before, in which the agent was free, from an after, in which it is bound, and the bind is what others build on when they extend credit, make plans, or pin dependencies to the agent's word. A second structural fact is that commitment has strength and visibility axes that vary independently of content: a casual verbal undertaking and a notarized contract both create commitments, but with vastly different binding force, recourse on breach, and observability to third parties. The structural questions are therefore: what action or proposition is bound, to whom, with what visibility, under what conditions of release, and with what penalty on breach. The pattern inherits a speech-act and contract framing with a normative load — promise-keeping is widely treated as obligatory — placing it toward the framed end of the spectrum, even though instances like a database commit are structurally clean; the human-practice centroid of binding-and-breach dominates how the concept is used.

Broad Use

  • Speech-act theory: the commissive class — promise, vow, oath, undertaking — is exactly the class that creates commitments.
  • Contract law: a contract is a structured commitment package of offer, acceptance, consideration, and bind.
  • Computing: transactions commit or roll back; version control records immutable commits; distributed protocols agree on whether a commitment is in force.
  • Game theory: making one's own future choice set smaller is a strategic asset — the burned bridge, the irrevocable threat.
  • Finance: forward contracts, options, and escrow are commitments with structured release conditions.
  • Engineering: design freezes, sign-offs, and change-control gates are commitment points in irreversible processes.

Clarity

Clarifies what is bound, by whom, to whom, with what release conditions, and what consequence on breach — and distinguishes an intention (an inner state) from a commitment (a publicly or operationally binding one) that others may rely on.

Manages Complexity

Compresses promise, contract, transaction, vow, and sign-off into one diagnostic and a small intervention menu — tighten, loosen, clarify, or dissolve the bind — reasoned over the agent's standing commitment slate.

Abstract Reasoning

Enables reasoning about the commitment slate (a possibly-inconsistent set of standing binds), about visibility (a commitment is weaker the harder breach is to observe), and about atomicity (whether a multi-part bind holds all-or-nothing).

Knowledge Transfer

  • Distributed systems: atomic-commit semantics — all effects happen or none — transfer to payment clearing and programmable contracts.
  • Programming languages: design-by-contract carried contract-law structure — preconditions, postconditions, recourse on breach — into language semantics.
  • Release engineering: the manufacturing discipline of design-freeze and sign-off transferred into error-budget and release-gating practice.

Example

A database transaction COMMIT is the structurally cleanest instance: before COMMIT the writes are tentative and silently discardable; after, they are durable and undoable only by a deliberate compensating action — the before/after demarcation with no normative load.

Relationships to Other Abstractions

Local relationship map for CommitmentParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.CommitmentPRIMEPrime abstraction: Constraint — is a kind ofConstraintPRIMEDomain-specific abstraction: Available-to-Promise — is part ofAvailable-to-Pr…DOMAINDomain-specific abstraction: Backorder — is part ofBackorderDOMAINDomain-specific abstraction: Embargo — is part ofEmbargoDOMAINDomain-specific abstraction: Responsiveness channel — is part ofResponsivenesschannelDOMAINDomain-specific abstraction: Source Protection — is part ofSourceProtectionDOMAINDomain-specific abstraction: Off the Record — is a decomposition ofOff the RecordDOMAINDomain-specific abstraction: Climate emergency declaration — is a kind ofClimate emergen…DOMAINDomain-specific abstraction: Database transaction — is a kind ofDatabasetransactionDOMAINDomain-specific abstraction: Lockstep protocol — is a kind ofLockstepprotocolDOMAINDomain-specific abstraction: Ratification — is a kind ofRatificationDOMAINDomain-specific abstraction: Service Level — is a kind ofService LevelDOMAINPrime abstraction: Commitment Device — is a kind ofCommitmentDevicePRIME+2 more

Current abstraction Commitment Prime

Parents (1) — more general patterns this builds on

  • Commitment is a kind of Constraint Prime

    A commitment is a reflexive (self-imposed) constraint-creation on one's own future; commitment is a kind-of constraint (the existing commitment_device already sits under constraint).

Children (14) — more specific cases that build on this

  • Climate emergency declaration Domain-specific is a kind of Commitment

    The proposed strict upward parent is prime:commitment.

  • Database transaction Domain-specific is a kind of Commitment

    The proposed strict upward parent is prime:commitment.

  • Lockstep protocol Domain-specific is a kind of Commitment

    The proposed strict upward parent is prime:commitment.

  • Ratification Domain-specific is a kind of Commitment

    The proposed strict upward parent is prime:commitment.

  • Service Level Domain-specific is a kind of Commitment

    A service level is a commitment specialized to a measured fulfillment quantile, time window, and predeclared consequence for breach.

Hierarchy path (1) — routes to 1 parentless root

Not to Be Confused With

  • Commitment is not a Commitment Device because a device is a mechanism deployed to make a commitment binding whereas commitment is the broader state of being bound.
  • Commitment is not a Constraint imposed from outside because commitment is reflexive self-binding whereas a constraint limits behavior regardless of source — the distinction governs the agent's own stake in honoring it.
  • Commitment is not Credible Commitment because credible commitment adds the requirement that the bind be believable to others whereas bare commitment includes weak, private binds that are operationally hollow.