Logic Constraints

Finite Fact Domain

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.

Structured Visual

Jurisdiction: US; as of 2026-06-24; not legal advice; Code encodes a stated interpretation workflow, not the law itself.

RENDER STRUCTURE · REFUSE INTERPRETATION · CITE · ABSTAIN · HAND-OFF: render structure, refuse interpretation, cite provenance, abstain when unsupported, and hand off to human review.

Finite fact domainrowfieldvaluequerytokensfinite,fact,known,unknown,conflictquerycount5supportcount3supportabstainFalsescopejurisdictionUS classroom logic-constraint workflowscopesource_typefinite_factrecord notice_presentrank3record notice_presentmatch2 of 5record notice_presentfilterpassrecord notice_presentciteFact Row 1record notice_presentsnippetFinite fact row 1 notice present value true review.record record_completerank1record record_completematch3 of 5record record_completefilterpassrecord record_completeciteFact Row 2record record_completesnippetFinite fact row 2 record complete value unknown review.record review_flagrank2record review_flagmatch3 of 5record review_flagfilterpassrecord review_flagciteFact Row 3record review_flagsnippetFinite fact row 3 review flag value conflict review.
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\text{logic constraints as of }June 24, 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\text{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\text{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\text{fact rows}=3,\quad \text{unknown}=1,\quad \text{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\text{fact review labels}

Jurisdiction: US; as of 2026-06-24; not legal advice; Code encodes a stated interpretation workflow, not the law itself.

RENDER STRUCTURE · REFUSE INTERPRETATION · CITE · ABSTAIN · HAND-OFF: render structure, refuse interpretation, cite provenance, abstain when unsupported, and hand off to human review.

Finite fact domainrowfieldvaluequerytokensfinite,fact,known,unknown,conflictquerycount5supportcount3supportabstainFalsescopejurisdictionUS classroom logic-constraint workflowscopesource_typefinite_factrecord notice_presentrank3record notice_presentmatch2 of 5record notice_presentfilterpassrecord notice_presentciteFact Row 1record notice_presentsnippetFinite fact row 1 notice present value true review.record record_completerank1record record_completematch3 of 5record record_completefilterpassrecord record_completeciteFact Row 2record record_completesnippetFinite fact row 2 record complete value unknown review.record review_flagrank2record review_flagmatch3 of 5record review_flagfilterpassrecord review_flagciteFact Row 3record review_flagsnippetFinite fact row 3 review flag value conflict review.

Summary

Finite facts keep missing and conflicting inputs visible before any constraint row tries to use them.

inputs before clauses\text{inputs before clauses}