Obligation Models
Clause Record
A contract clause can be represented as an exact obligation record. 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.
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.
A clause is modeled as fields
The stated process begins with a clause record. The toy source is Toy Contract sec. 2.1, represented as structured fields rather than an enforceability conclusion.
Example clause data
The example has Vendor, Buyer, deliver, report, order_received, and a due-days field of 3.
The model counts records and authored fields
The compiler renders 1 clause record with 12 authored fields. Derived status fields are recomputed outside the authored clause.
Diagram note
The table shows the clause as review data. A row is not a statement that any real contract term is enforceable.
Jurisdiction: US; as of 2026-06-24; not legal advice; Code encodes the stated-rule interpretation.
Summary
The first move is structural: capture source, parties, action, object, trigger, and due rule before computing any trace.