Breach of Contract¶

A legally cognizable failure to honor a binding contractual duty, including qualifying anticipatory repudiation.

Version: v1 · 2026-09-28 · History
Domain-specific #: 8267
Domain group: Professional & Organizational Practice
Origin domain: Law & Governance
Subdomain: Contract Law → Law & Governance
Aliases: Contractual breach

Core Idea¶

Breach of contract is observed non-satisfaction of an enforceable contractual duty under governing law. It can be unexcused nonperformance when due or, where the doctrine applies, an unequivocal present repudiation of a future obligation. Hochster v De La Tour allowed an English courier claimant to sue after such an advance renunciation without waiting for service to begin. A tentative worry or disappointed nonbinding plan is not enough. Breach occurrence is distinct from its seriousness and remedy: conditions, warranties, and innominate terms can have different consequences, and not every breach permits termination or proves compensable loss. UCC sale-of-goods rules also have their own thresholds. This is a legal subtype of criterion-relative Failure, not a kind of Contract agreement.

How would you explain it like I'm…

Breaking the Deal

When two people make a real promise that counts, like I give you my toy car and you give me your sticker, that is a contract. A breach of contract is when someone does not do their part, or clearly says ahead of time that they will not. Just wishing you had made a different deal is not a breach. And what happens next, like how to fix it, is a separate question.

Not Keeping Your Side of the Deal

A contract is an agreement that the law will actually back up, with specific jobs each side has promised to do. Breach of contract means one side fails to do its promised job when it is due, gets in the way of the other side doing their job, or, in some legal systems, clearly announces in advance that it will not do its job. Feeling unhappy with a deal is not a breach, and neither is breaking a plan that was never a binding promise. In one famous English case, someone was told before a job even started that they would not be needed, and the court let them sue right away. Whether there is a breach is one question; what the fix should be, like money or ending the deal, is another.

Failing a Binding Obligation

Breach of contract is a legal event: it only makes sense relative to an enforceable agreement and the specific duties it creates. A party breaches by failing to perform when performance is due, by interfering with the other party's performance, or, where the governing law recognizes it, by clearly repudiating a future duty in advance (called anticipatory repudiation). In the English case Hochster v De La Tour, an unequivocal repudiation before a courier job had even begun let the other side sue immediately, showing that breach isn't only something that happens after a deadline passes. To analyze a breach you need the parties, the duty, the timing, the conduct, and which legal system applies. Whether a breach happened and how serious it is are separate from what remedy follows; not every breach lets the other side end the contract.

Breach of contract is defined relative to an enforceable agreement and its particular obligations, so an analysis must specify the parties, the duty in question, its timing, the conduct, and the governing legal framework. Breach can take several forms: failure to perform when due, interference with the counterparty's performance, and, where recognized, anticipatory repudiation, an unequivocal advance refusal of a future duty. Hochster v De La Tour is the classic English illustration: a clear repudiation before a courier engagement was to start supported an immediate action. Dissatisfaction with a bargain, or the non-fulfilment of a non-binding plan, is not breach. Crucially, occurrence and gravity of breach are distinct from remedy. English law classifies terms as conditions, warranties, or innominate terms, and the right to terminate depends on the type of term or on how substantial the consequences are. Other regimes, such as UCC sale-of-goods rules, set their own anticipatory-repudiation thresholds and options. Damages, cure, election, and termination each require further analysis rather than following automatically from a finding of breach.

Scope of Application¶

Use the concept only with an enforceable duty and an identified legal frame.

Contract interpretation. Locate the precise duty and time that the alleged conduct failed to honor.
Dispute classification. Distinguish actual nonperformance from a legally sufficient anticipatory renunciation.
Remedy analysis. Keep breach occurrence separate from damages, cure, and termination entitlement.
Comparative contract law. Explain why English common-law and UCC sale rules may use different thresholds and choices.

Clarity¶

State the binding agreement, exact duty, due time, conduct, and governing law. An unexcused missed delivery is a clear actual example; a definite refusal before a future duty may be anticipatory breach. A tentative worry without qualifying repudiation is the nearest miss. An informal promise is outside contract law. Even where breach is established, termination and damages need separate seriousness, loss, and remedy tests; the label does not resolve them automatically.

Manages Complexity¶

The label separates a binding duty, applicable time, and observed deviation from later remedy questions. Actual and anticipatory breach can be compared without treating every performance concern as repudiation. This staging prevents both premature termination claims and the error of forcing a claimant to wait after a clear renunciation.

Abstract Reasoning¶

Establish that an enforceable contract and relevant parties exist under the chosen law.
Identify the exact obligation, its due time, and any lawful modification or excuse.
Compare actual conduct or advance communication with that obligation.
Classify any deviation as actual or qualifying anticipatory breach under the governing test.
Only then analyze seriousness, election, available remedies, and proof of loss separately.

Knowledge Transfer¶

The broad pattern of commitment, applicable criterion, and non-satisfaction can inform reasoning about service agreements or institutional obligations, but 'breach of contract' requires legal enforceability and the governing doctrine of performance or repudiation. An engineering failure or disappointed expectation is not literally this legal cause of action. The English Hochster rule and UCC §2-610 should not be blended into one jurisdiction-free remedy statement.

Relationships to Other Abstractions¶

Current abstraction Breach of Contract Domain-specific

Parents (1) — more general patterns this builds on

Breach of Contract is a kind of Failure Prime

A breach is observed non-satisfaction of an applicable contractual duty or present no-renunciation criterion under governing law.

Hierarchy path (1) — routes to 1 parentless root

Breach of Contract → Failure

Neighborhood in Abstraction Space¶

Breach of Contract sits in a moderately populated region (40^th percentile for distinctiveness): it has near-neighbors but no dense thicket of look-alikes.

Family — Decisions Under Constraint & Commitment (9 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-10-08