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.

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

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.

performance datedue date\text{performance date}\leftrightarrow\text{due date}

Example due date and performance date

The performance event dated June 5, 2026 is compared to due date June 4, 2026.

performance date=June5,2026\text{performance date}=June 5, 2026

The difference becomes a trace value

The recomputed difference is 1 day. That label is a model status input, not a breach conclusion.

days late=1\text{days late}=1

Diagram note

The diagram shows due date, performance date, and recomputed days late in one row for audit.

comparison is row data\text{comparison is row data}

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

Performance eventrowfieldvaluescopenotePerformance 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 deliverystatuslateclause deliverytriggeredTrueclause deliverytrigger2026-06-01clause deliverydue2026-06-04clause deliveryperformance2026-06-05clause deliverydaysLate1clause deliveryciteToy Contract sec. 2.1

Summary

Performance comparison is useful as trace data only; legal breach analysis stays outside the diagram.

trace data only\text{trace data only}