The Semantic Validity Engine
What we claim: The Semantic Validity Architecture can determine whether a claim is structurally complete—whether it satisfies the six constraints necessary for semantic validity. This operates upstream of empirical verification. A structurally incomplete claim cannot be valid regardless of its factual content.
What we do not claim: The architecture does not replace empirical verification. It does not know whether the Eiffel Tower was built in 1887 or 1923. What it knows is whether the claim asserting a date satisfies the structural conditions that would make it verifiable. It catches the architecture of error, not the content of error.
Why this is stronger: Traditional fact-checkers work downstream—they correct errors after emission. The Hexis works upstream—it prevents structurally incomplete claims from being emitted at all. Prevention, not correction.
Traditional Fact-Checking vs. Semantic Validity Engine
Engine Architecture — Claim Processing Pipeline
Patent Family → Engine Function Map
What We Claim — and What We Do Not
We claim
- Structural completeness checking against six formal constraints
- Categorical output (complete/incomplete) independent of operator
- Real-time validation before emission, not reactive correction
- Inference type discrimination — deduction tagged differently than speculation
- Closure authority routing — the system knows when humans must decide
- Universal application to every claim, not editorial selection
- Formal operators derived from Aristotelian causal analysis, implemented computationally
We do not claim
- Replacement for empirical verification of factual content
- Omniscience about historical dates, statistics, or events
- Infallibility — a structurally complete claim can still be factually wrong
- Elimination of all error — we eliminate structurally preventable error
- Automated resolution of genuine value disputes or ethical questions
- Independence from all human judgment — closure authority preserves it where needed