Obligation Models
Performance Event
Performance events are compared to recomputed due dates. 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.
Performance is another event fact
The stated model adds a performance event after trigger and due-date computation. The comparison is mechanical inside the toy table.
Example due date and performance date
The performance event dated June 5, 2026 is compared to due date June 4, 2026.
The difference becomes a trace value
The recomputed difference is 1 day. That label is a model status input, not a breach conclusion.
Diagram note
The diagram shows due date, performance date, and recomputed days late in one row for audit.
Jurisdiction: US; as of 2026-06-24; not legal advice; Code encodes the stated-rule interpretation.
Summary
Performance comparison is useful as trace data only; legal breach analysis stays outside the diagram.