Finite facts use explicit known, unknown, and conflict values. Honesty note: simplified toy logic-constraint workflow, corpus-light with no neochart dependency; the pinned first step carries the full honesty note.
highlighted = computed this step
Logic constraint honesty note
Honesty note: simplified toy logic-constraint workflow; corpus-light and no neochart dependency; jurisdictions and interpretations vary; as of June 24, 2026; not legal advice; code encodes a stated interpretation workflow, not the law itself.
logic constraints as of June24,2026
State the finite fact process
The stated process stores each fact as a finite row with a selected value or review state.
finite fact rows
Example fact packet
The toy packet sets notice_present to true, leaves record_complete unknown, and marks review_flag as conflict.
true unknown conflict
The domain recomputes row counts
The toy domain has 3 rows: 1 known row, 1 unknown row, and 1 conflict row.
fact rows=3,unknown=1,conflict=1
Diagram note
The diagram is a fact-domain table. Unknown and conflict are review labels, not model outputs that answer a legal question.
fact review labels
Jurisdiction: US; as of 2026-06-24; not legal advice; Code encodes a stated interpretation workflow, not the law itself.
Summary
Finite facts keep missing and conflicting inputs visible before any constraint row tries to use them.