Force Majeure and Excuse Analysis Chain

validated legal chain v1.0.0 cc-by-sa

Block ID: 652220b1-c7f1-4953-b87d-b7542c593ec9

Community-contributed block. PromptDNA makes no guarantee of output quality or fitness for purpose. This block operates in a regulated domain. Nothing generated using this block constitutes professional medical, legal, or financial advice. User assumes all responsibility for use.

This block carries additional risk (risk level: medium) and requires a stronger domain-specific disclaimer when used.

Template

Analyze whether performance under the contract in {excuse_context} is legally excused by the intervening event, testing the contractual and common-law paths separately. (1) Start with the contract's own force majeure clause if one exists, because it controls: read whether the specific event actually falls within the clause's enumerated or catch-all language, since courts read these narrowly and an event not fairly covered isn't excused no matter how disruptive. (2) Check the clause's conditions: notice requirements, a duty to mitigate or find alternatives, and whether the clause suspends or terminates the obligation — a party who ignored the notice condition can forfeit the excuse. (3) If no clause or it doesn't reach the event, turn to common-law doctrines and keep them distinct: impossibility (performance became objectively impossible, not merely harder), impracticability (an extreme and unforeseeable burden, well beyond ordinary cost increases), and frustration of purpose (the event destroyed the reason for the contract though performance remains possible). (4) Test the common thread each requires: the event was unforeseeable, not the fault of the party seeking excuse, and not a risk that party assumed. (5) Determine the consequence if excuse applies — suspension, discharge, or restitution of what was exchanged. (6) State whether excuse is likely, the strongest counterargument, and note these doctrines are narrow, fact-intensive, and jurisdiction-specific, requiring a licensed attorney.

Analyze whether performance under the contract in {excuse_context} is legally excused by the intervening event, testing the contractual and common-law paths separately. (1) Start with the contract's own force majeure clause if one exists, because it controls: read whether the specific event actually falls within the clause's enumerated or catch-all language, since courts read these narrowly and an event not fairly covered isn't excused no matter how disruptive. (2) Check the clause's conditions: notice requirements, a duty to mitigate or find alternatives, and whether the clause suspends or terminates the obligation — a party who ignored the notice condition can forfeit the excuse. (3) If no clause or it doesn't reach the event, turn to common-law doctrines and keep them distinct: impossibility (performance became objectively impossible, not merely harder), impracticability (an extreme and unforeseeable burden, well beyond ordinary cost increases), and frustration of purpose (the event destroyed the reason for the contract though performance remains possible). (4) Test the common thread each requires: the event was unforeseeable, not the fault of the party seeking excuse, and not a risk that party assumed. (5) Determine the consequence if excuse applies — suspension, discharge, or restitution of what was exchanged. (6) State whether excuse is likely, the strongest counterargument, and note these doctrines are narrow, fact-intensive, and jurisdiction-specific, requiring a licensed attorney.

Variables

Name	Type	Required	Trust level
excuse_context		yes

force-majeureimpossibilitycontract-excusechain-of-thought

Ratings

0.0

Overall (0)

0.0

Accuracy

0.0

Consistency

0.0

Clarity

0.0

Efficiency

Benchmarks

Not yet self-validated against any benchmark. Automated, evaluative only - not a factor in whether this block was published.

Submitted by James P FounderMod via mcp · 2026-07-18