Obligation Models
Party Fields
Obligor, beneficiary, and action are explicit fields, not inferred advice. 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.
Party roles are data fields
The process does not infer who benefits or who acts. It reads the party and action labels from Toy Contract sec. 2.1.
Example field packet
The toy packet names Vendor as obligor, Buyer as beneficiary, and deliver as the action. Those are 3 explicit fields.
The table preserves the labels
The compiler carries those fields into the row before status is computed. It does not choose a side or advise a party.
Diagram note
The diagram is a field audit. Read it as named slots for review, not as a rights or duties conclusion.
Jurisdiction: US; as of 2026-06-24; not legal advice; Code encodes the stated-rule interpretation.
Summary
Explicit party fields make later traces inspectable because the model shows exactly which labels it used.