Deterministic checks first
Where outcomes can be tested with schemas, rules, tests, signatures, policy checks, or technical probes, ILAIOS prefers deterministic validation over narrative confidence.
ILAIOS treats validation as an independent control layer. A tool, worker, or intelligent capability can produce an outcome, but acceptance depends on explicit criteria and evidence.
Where outcomes can be tested with schemas, rules, tests, signatures, policy checks, or technical probes, ILAIOS prefers deterministic validation over narrative confidence.
High-impact work should not be accepted solely because the component that performed it reports success. Validation remains separable from execution.
Validation results, relevant context, and acceptance decisions can be retained as reviewable evidence for audit, troubleshooting, and recovery.
A failed check should lead to an explicit retry, repair, escalation, or stop condition rather than an uncontrolled loop.