Rule Model Foundations

Unknown and Conflict Trace

Unknown and conflicting facts stay visible as trace rows. Honesty note: simplified toy rule-modeling workflow, corpus-light with no neochart dependency; the pinned first step carries the full honesty note.

highlighted = computed this step

Rule model honesty note

Honesty note: simplified toy rule-modeling 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.

rule model as of June24,2026\text{rule model as of }June 24, 2026

Keep unknowns and conflicts visible

The stated process leaves missing facts as unknown rows and conflicting facts as conflict rows.

uncertainty stays visible\text{uncertainty stays visible}

Example uncertain packet

The toy packet has missing age data, conflicting residency data, and a stated filing-date row.

missing age plus conflict residency\text{missing age plus conflict residency}

The trace recomputes row status

The compiled trace has 1 unknown row and 1 conflict row.

unknown rows=1,conflict rows=1\text{unknown rows}=1,\quad \text{conflict rows}=1

Diagram note

The diagram is a prong trace. It keeps missing and conflicting facts as separate rows.

separate review rows\text{separate review rows}

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

Unknown and conflict trace age_minimum: unknown via age_years=None compare=17 residency_scope: conflict via residency_scope=conflict compare=True filed_by_date: satisfied via filed_by_date=True compare=True

Summary

Unknown and conflict rows should remain visible until human review resolves the model inputs.

uncertainty to review\text{uncertainty to review}