Conditions, Performance, and Breach
Conditions, Performance, and Breach
Conditions, tender, cure, material breach, and anticipatory repudiation.
Structured Visual
Jurisdiction: US; as of 2026-08-28; not legal advice; Render structure, refuse interpretation, cite, abstain, and hand off.
RENDER STRUCTURE · REFUSE INTERPRETATION · CITE · ABSTAIN · HAND-OFF: render structure, refuse interpretation, cite provenance, abstain when unsupported, and hand off to human review.
Scope and honesty note
Jurisdiction: United States common-law overview with Texas sales-law analogues; as of 2026-08-28; jurisdictions and contract types vary; not legal advice. Synthetic facts are classroom inputs, not findings. This lesson renders structure, refuses unsupported interpretation, cites, abstains, and hands off.
See the essential structure first
The preview separates duty, performance, breach analysis, and remedy routing without declaring a breach. This deliberately incomplete preview has 5 nodes; exceptions and legal consequences remain in the sourced prose below.
Jurisdiction: US; as of 2026-08-28; not legal advice; Render structure, refuse interpretation, cite, abstain, and hand off.
RENDER STRUCTURE · REFUSE INTERPRETATION · CITE · ABSTAIN · HAND-OFF: render structure, refuse interpretation, cite provenance, abstain when unsupported, and hand off to human review.
Begin with the governing doctrine
A condition is an event that must occur before a performance duty becomes due; a promise is a commitment whose breach may support a remedy. Courts often require substantial performance for constructive conditions at common law and distinguish material from minor breach by context. Sales law starts with a perfect-tender rule for a single delivery but qualifies it through agreement, cure, installment-contract doctrine, acceptance, revocation, and remedy limits. Anticipatory repudiation addresses a clear refusal of future performance when the resulting loss substantially impairs contract value.
Pin the buyer's improper-delivery choices
This provision states the sales-law baseline when goods or tender fail in any respect to conform, while identifying important qualifications. Verbatim snapshot text: “BUYER'S RIGHTS ON IMPROPER DELIVERY. Subject to the provisions of this chapter on breach in installment contracts (Section 2.612) and unless otherwise agreed under the sections on contractual limitations of remedy (Sections 2.718 and 2.719), if the goods or the tender of delivery fail in any respect to conform to the contract, the buyer may (1) reject the whole; or (2) accept the whole; or (3) accept any commercial unit or units and reject the rest.” Source: Tex. Business and Commerce Code § 2.601; https://www.neochart.com/catalog/texas/business_commerce/chapter_2/section_2_601/tex_bc_2_601_74b2d5b6c3ed/tex_business_commerce_code_sec_2_601_buyer_s_rights_on_impro_0001/index.html; data via neochart.com, snapshot 2026-08.
Pin anticipatory repudiation
This provision states the substantial-impairment predicate and the aggrieved party's principal choices after repudiation of future performance. Verbatim snapshot text: “ANTICIPATORY REPUDIATION. When either party repudiates the contract with respect to a performance not yet due the loss of which will substantially impair the value of the contract to the other, the aggrieved party may (1) for a commercially reasonable time await performance by the repudiating party; or (2) resort to any remedy for breach (Section 2.703 or Section 2.711), even though he has notified the repudiating party that he would await the latter's performance and has urged retraction; and (3) in either case suspend his own performance or proceed in accordance with the provisions of this chapter on the seller's right to identify goods to the contract notwithstanding breach or to salvage unfinished goods (Section 2.704).” Source: Tex. Business and Commerce Code § 2.610; https://www.neochart.com/catalog/texas/business_commerce/chapter_2/section_2_610/tex_bc_2_610_5fc9014f5173/tex_business_commerce_code_sec_2_610_anticipatory_repudiatio_0001/index.html; data via neochart.com, snapshot 2026-08.
Pin the synthetic fact pattern
A synthetic contract makes payment follow conforming delivery. The seller tenders goods with a documented specification variance, then states before the next delivery date that it will not deliver the balance.
Work the application
The trace first separates the condition that activates payment from the seller's delivery promise. The tender record then enters the sales nonconformity path, with cure, installment, acceptance, agreement, and remedy limitations left visible. The later message is tested for repudiation and substantial impairment before the model records the statutory wait-or-resort choices. No breach or materiality result is inferred from the message label.
Read the populated authority-and-fact record
The populated record ties the conforming-delivery condition, variance evidence, future-performance message, statutory tender choices, and repudiation questions to separate rows. The rendered record contains 12 populated rows across source, fact, and application branches.
Jurisdiction: US; as of 2026-08-28; not legal advice; Render structure, refuse interpretation, cite, abstain, and hand off.
RENDER STRUCTURE · REFUSE INTERPRETATION · CITE · ABSTAIN · HAND-OFF: render structure, refuse interpretation, cite provenance, abstain when unsupported, and hand off to human review.
Read the complete fact and application rows
Express condition: Payment follows delivery of conforming identified goods. Tender: Seller tenders goods with a documented specification variance. Later message: Seller states before the next due date that it will not deliver the balance. Condition: Distinguish event-triggered duties from promised performance. Tender: Sales perfect-tender rule is subject to cure, installments, agreement, and remedy limits. Repudiation: Future-performance loss must substantially impair contract value.
Narrow summary
Model conditions, promises, tender, cure, materiality, and repudiation separately so a status trace never becomes an unsupported breach conclusion.