Obligation Models

Trigger Event

Event facts can trigger or not trigger a modeled obligation. Honesty note: toy contract model; jurisdictions vary; the pinned first step states the as-of date; enforceability and breach require legal review; not legal advice.

highlighted = computed this step

Contract model honesty note

Honesty note: toy contract model; jurisdictions vary; as of June 24, 2026; enforceability and breach require legal review; not legal advice; status trace is not a breach conclusion.

toy contract as of June24,2026\text{toy contract as of }June 24, 2026

Trigger matching is stated in the record

The clause record names order_received as the trigger event. The table checks event facts against that trigger label.

trigger label→event match\text{trigger label}\to\text{event match}

Example event fact

The event dated June 1, 2026 is an order_received event for the same object as Toy Contract sec. 2.1.

event date=June1,2026\text{event date}=June 1, 2026

The event governs the trace row

The event matches 1 clause row. That matched row can then compute due date June 4, 2026.

triggered rows=1\text{triggered rows}=1

Diagram note

The diagram shows a trigger trace only. It does not decide breach, enforceability, or what any party should do.

trigger is a model row\text{trigger is a model row}

Jurisdiction: US; as of 2026-06-24; not legal advice; Code encodes the stated-rule interpretation.

Trigger eventrowfieldvaluescopenoteTrigger event; jurisdictions vary; enforceability and breach require legal review; not legal advice; status trace is not a breach conclusion.statusvocabularylate,not_triggered,pending,satisfied,unknownclause deliveryrank1clause deliverystatuspendingclause deliverytriggeredTrueclause deliverytrigger2026-06-01clause deliverydue2026-06-04clause deliveryperformancenoneclause deliverydaysLate0clause deliveryciteToy Contract sec. 2.1

Summary

Trigger logic is a match between authored clause fields and event facts, followed by review.

facts govern the row\text{facts govern the row}