# trust & safety layer

Validation Engine — why VAOS is safe to act

Every candidate action passes through the validation envelope before execution. Confidence is composed from sensor reliability, scene quality, memory consistency, and policy fit. Below threshold, no action leaves the runtime.

# the envelope

One scalar. Four signals.

Validation envelope · patent pending
Cv = α·Cs + β·Cm + γ·Ct + δ·Ch

Confidence is a weighted sum: sensor reliability Cs, memory consistency Cm, temporal stability Ct, human policy fit Ch. Action emits only when Cv ≥ τ. Below threshold, the runtime yields a no-op + diagnostic.

# what the engine checks

Eight checks, every action

🎛️

Sensor reliability

Live per-stream confidence — calibration, occlusion, exposure.

📐

Evidence checks

Are the cited objects/events actually in the Scene Contract? No hallucinated entities.

⏱️

Temporal stability

Persistence checks — did the evidence hold over the window?

💾

Memory consistency

Compared to recent history — anomaly or routine?

📜

Policy engine

Configured rules — restricted actions, allowed zones, escalation gates.

🚨

Hallucination reduction

Constrained vocabulary, schema-enforced output, no free-form action text.

🛡️

Runtime guarantees

Reversibility, audit log, replay envelope archived per decision.

🔍

Auditability

Every decision keeps its full envelope — scene + reasoning + confidence + policy. Reviewable in dashboards.

Patent pending. The closed-loop runtime that gates action on real-time scene confidence — the validation envelope — is one of the three patent-pending core innovations of VAOS™.

Safe to act in the physical world.

Reasoning produces candidates. Validation decides whether they leave the runtime.

Reasoning Runtime OSTVAL loop