Pactum’s obligation detection engine runs on a 1.5-second debounce. Every time you stop typing for 1.5 seconds, the engine scans the current paragraph and evaluates it against six weighted patterns.

Scans for “shall,” “must,” “is required to,” “is obligated to.” These are the strongest indicators of a binding obligation. A clause containing “shall” with a specific action and a specific party is almost certainly an obligation.

Scans for “warrants,” “represents,” “covenants,” “undertakes.” These indicate representations, warranties, and covenant commitments that create ongoing duties.

Scans for time-bound phrases: “within [X] days,” “by [date],” “no later than,” “prior to.” These indicate obligations with specific deadlines that need tracking.

Scans for “penalty,” “termination,” “default,” “liquidated damages,” “forfeiture.” These indicate what happens if an obligation is breached.

Scans for “indemnify,” “hold harmless,” “defend,” “compensate.” Indemnification provisions are among the highest-risk obligations in any commercial contract.

Scans for “shall not,” “must not,” “is prohibited from,” “may not.” These indicate restrictions and prohibitions.

When a clause matches one or more patterns, the weights are summed. A score of 3 or above triggers an obligation tag. The engine then auto-fills five fields: bearer (who is obligated), trigger (what activates it), consequence (what happens on breach), deadline (when it is due), and risk level (high, medium, or low).

Seven additional risk flags are checked: unlimited liability, sole discretion, without cause or notice, irrevocable commitments, unconditional obligations, and waiver of rights. Any clause that triggers a risk flag is highlighted in the obligation panel for review.