What is Validation Intelligence?

Ivorleaf determines what the evidence actually supports. The product establishes the relationship between information and evidence as machine-readable state.

From input to determination

1. Supply information and at least one evidence item.
2. Supplied text enters VI unchanged. Only explicit acquire requests invoke public-source inspection.
3. Ivorleaf evaluates canonical material information units against independent evidence items.
4. Receive or retrieve a determination, relationships, signals, and provenance.

With inline evidence, the supplied text is the evidence material. Acquisition failure fails closed without caller-text substitution. Learn Information & Evidence and Source Inspection.

Completed outcomes

supported, unsupported, conflicting, and uncertain describe what the evidence establishes. They are not universal truth claims. Execution failures do not become uncertain determinations.

POST may return 200 completed or, with async acceptance, 202 in_progress. GET retrieves the stored state. See Async Execution.

Canonical relationship work uses Validation Units. Duplicate evidence, polling, failed execution, and completed replay add no VUs.

Begin

Use the Quickstart and Your First Validation. Ivorleaf owns the validation execution contract; customers do not configure the underlying evaluator.

Technical Sessions remain available for advanced persistent workflows with saved context and generated artifacts.