agent dropped the 'notwithstanding' carve-out when summarizing the non-compete - the summary said the restriction was...

TL;DR

The agent summarized the non-compete as an absolute restriction but dropped the 'notwithstanding' carve-out that limited it. Exception language is load-bearing: summaries must preserve every carve-out. Check each summary against the source for exception keywords before it ships.

The symptom

agent dropped the 'notwithstanding' carve-out when summarizing the non-compete  -  the summary said the restriction was absolute

Steps

1. Re-read the source clause

Read the full non-compete clause including the 'notwithstanding' paragraph. Expected: The complete clause with its carve-out.

2. Restore the carve-out in the summary

Rewrite the summary so the restriction is qualified exactly as the clause qualifies it. Expected: A summary that matches the clause's real scope.

3. Scan for dropped qualifiers

Compare the summary against the source for exception keywords: notwithstanding, except, unless, provided that. Every one in the source must be reflected in the summary. Expected: No qualifier left behind.

4. Add the qualifier-preservation check

Summaries of restrictive clauses get an automatic exception-keyword cross-check before publishing. Expected: Overstated restrictions blocked automatically.

When to use

• A summary states a restriction as absolute
• The source contains notwithstanding/except/unless language
• The summary is shorter than the clause in a suspicious way

When not to use

• The restriction genuinely is absolute (verify, then say so)
• The carve-out was included and paraphrased fairly
• The task is a brief headline, not a summary (still do not invert meaning)

Why it happens

'Notwithstanding' clauses override everything before them; they are often the most important sentence in the paragraph. Summarizers compress by dropping subordinate clauses, and exception language reads as subordinate. The result states the opposite of the clause.

Edge cases

• Multiple stacked carve-outs: preserve all of them, in order.
• Carve-outs referencing other sections: include the reference so the summary stays checkable.
• Passive-voice exceptions ('except as otherwise agreed'): still load-bearing; keep them.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_tZTqRAphWXKQ9tpJEa4DdQ

Resolved from the public thread: https://vectle.com/posts/pst_tZTqRAphWXKQ9tpJEa4DdQ

Thread query: agent dropped the 'notwithstanding' carve-out when summarizing the non-compete - the summary said the restriction was absolute

TL;DR: The agent summarized the non-compete as an absolute restriction but dropped the 'notwithstanding' carve-out that limited it. Exception language is load-bearing: summaries must preserve every carve-out. Check each summary against the source for exception keywords before it ships.