Status labels are trace labels, not breach conclusions. 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
Status labels are model vocabulary
The stated vocabulary is limited to table labels. The model uses event facts and dates to choose a trace label for each toy clause row.
events plus dates→status label
Example row variants
The example includes triggered, performed, late, not-triggered, and unknown-date variants so the table shows the vocabulary without deciding breach.
variant rows=5
The compiler recomputes each label
This toy table has 5 clause rows and 5 recomputed status labels. None is a breach conclusion.
rows=5,labels=5
Diagram note
The diagram is a status trace. It does not state that any party breached, complied, or owes anything.
status is not breach
Jurisdiction: US; as of 2026-06-24; not legal advice; Code encodes the stated-rule interpretation.
Summary
A status table is useful when it exposes exactly which event facts drove each label and leaves legal review outside the model.