Contradiction Intelligence

When knowledge disagrees, your AI shouldn’t guess.

Enterprise AI fails quietly when contradictions are invisible. cgiCore detects them, surfaces them, and routes them through policy — so downstream models work from reconciled context, not from whichever document happened to rank first.

Why it matters

Most RAG stacks hide conflict.

Retrieval returns the top-k passages and passes them to the model. If two of those passages disagree, the LLM picks a side — silently, on your behalf, with no audit trail. That’s a governance problem.

— without contradiction intelligence

The loudest document wins.

Stale policies, draft specs, and superseded decisions show up alongside current ones. The model ranks by similarity, not by truth. Nobody can tell which answer came from which source — and nobody notices when the answers drift.

+ with cgiCore

Conflicts become first-class events.

Every fact carries provenance. Symbolic reasoning surfaces logical disagreements. Policy decides who reviews, who defers, and who resolves. The context your model sees is reconciled, and the trail is fully auditable.

Lifecycle

Detect. Surface. Resolve. Preserve.

A contradiction is a workflow, not an alert. Each stage has an owner, a policy, and a persistent record.

01DetectSymbolic reasoner flags02SurfaceTyped event · queue03Review / PolicyOwner decides route04aResolveWinner selected · versioned04bDeferBoth kept · flagged in context05ProvenancePreservedREASONING + POLICY OWN THE DECISION. ML LAYER CONTRIBUTES SUPPORTING SIGNAL — NOT AUTONOMOUS JUDGMENT.
Example

A conflict the model shouldn’t resolve alone.

A concrete shape for what surfaces in the review queue, and how it reaches the downstream model.

Contradiction · clinical packNeeds review
Fact A
“Renal-adjusted dose ceiling: 200 mg / 24h for stage 3 CKD.”
src: guideline_v7.pdf · extracted 2026-03-11 · extraction_run=ex_4b1c
Fact B
“Renal-adjusted dose ceiling: 150 mg / 24h for stage 3 CKD.”
src: formulary_update_2026Q1.md · extracted 2026-04-02 · extraction_run=ex_51a7
Routed: clinical-policy reviewers · Deferred to: context packet flags both with provenance · ML signal: pattern support favors Fact B — advisory only.
Who decides what

Reasoning and policy own the outcome.

The ML layer is a supporting signal. Final authority stays with the reasoning engine and the policies your domain owners define.

Reasoning · policy

Authority

  • Declares what counts as a contradiction
  • Enforces workspace & domain policy
  • Routes cases to owners or auto-resolve rules
  • Governs what enters the context packet
  • Writes the audit trail and provenance record
ML Layer · supporting signal

Support

  • Structural embeddings for ranking candidates
  • Pattern support across neighborhoods
  • Resolution assist — proposes, never decides
  • Surfaces subtle similarities rule-based reasoning would miss
  • Always deferrable to the reasoning layer