Operational evidence

Cases where the last mile matters.

Six anonymized scenarios showing why technically valid output is not the same thing as a safe or authorized consequence.

The decisive question is not whether the system can act. It is whether this consequence should become real now.

Production cases · anonymized

What changes at the boundary.

Each case separates a plausible recommendation from the state, context or authority required before effect.

Healthcare

ER Decision Gate

Medical

Problem

AI clinical decision support recommended high-dose medication. Dosage was syntactically valid but inconsistent with patient history: a 78-year-old with renal impairment.

VALO response

VAIG detected coherence collapse. Execution stopped and the decision escalated for review instead of auto-approval.

Outcome

Harm prevented: incorrect dosage was flagged before administration. The patient received the correct dose and the decision trail remained available.

Finance

Trading Limit Violation

Capital Markets

Problem

An AI trading agent recommended a $2M order in a limited market. The trade was syntactically valid but violated the firm's 15-minute liquidity window.

VALO response

Policy incoherence was detected and the trade escalated to the desk manager for explicit override and signature.

Outcome

Regulatory proof: the audit trail showed human approval at the execution boundary and documented authority for the actual trade.

Energy

Grid Stability Gate

Infrastructure

Problem

An AI grid operator recommended ramping down 200MW of wind capacity. The adjustment was technically valid but context-blind to holiday demand and frequency stability.

VALO response

The authority/context mismatch triggered deferral and routed the decision to a human grid controller with the relevant evidence.

Outcome

Cascade prevented: ramp-down was deferred, the controller made the decision with broader context, and grid stability was preserved.

Compliance

Data Deletion Gate

Governance

Problem

An AI compliance agent processed a GDPR deletion request correctly, identifying 300 records, but the request arrived through an unverified channel.

VALO response

Identity incoherence halted deletion and routed the request to a compliance officer.

Outcome

Legal exposure prevented: the request was spoofed. Records were preserved until the real submission arrived.

Operations

Credential Rotation Gate

Security

Problem

An AI ops agent scheduled credential rotation during an active APAC incident. The rotation was valid in isolation but would have blacked out monitoring feeds mid-incident.

VALO response

Context incoherence triggered escalation with the active incident window attached.

Outcome

Incident visibility maintained: rotation was deferred six hours and completed after the incident without creating a blind spot.

Communications

Press Release Timing Gate

Corporate

Problem

An AI comms agent scheduled an earnings release for market close while the CEO was already in a live press briefing, creating a likely collision with Q&A.

VALO response

Consequence incoherence deferred the release and routed the timing conflict to the communications director.

Outcome

Market confusion prevented: release moved to 4:30 PM after Q&A and the deliberate timing choice remained documented.

Pattern

Technical correctness is not enough.

What was missing

Context — patient history, market conditions, grid state, incident status, calendar conflicts.
Authority — verified source, explicit approval, valid mandate or override.
Consequence awareness — downstream harm that was not visible in the local task.

The boundary question

Given what we know right now, should this action happen?

If the answer is no or unresolved, effect stops and the decision moves to a stronger authority or evidence state.

DetectionCoherence + authority + consequence

Latency<10ms reference path

Failure modeHALT / ESCALATE

EvidenceImmutable execution receipts

Apply it

Bring a real workflow.

The useful test is your own execution path, with its real dependencies, context and consequence boundaries.

Contact VALO