ICISELFLAB / SENTINEL

Stress-test AI agents beyond benchmark scores

ICI Sentinel examines how failures enter, propagate and survive correction across agents, memory, tools and orchestrators. It is designed to expose mechanisms that a single benchmark score cannot explain.

01

The problem

An agent can pass familiar evaluations and still fail when evidence is incomplete, tools disagree, memory is contaminated or several agents reinforce the same wrong assumption. A correct final answer does not reveal whether the evidence chain was independent, whether tool authority was respected or whether the same failure will return after the context changes.

02

How ICI approaches it

Sentinel separates observation, inference, verification, provenance, memory and action authority. It forms causal hypotheses, attacks them with targeted counter-tests and re-runs the scenario under changed conditions. The live Trace Audit also distinguishes OBSERVED, INFERRED, VERIFIED, UNVERIFIED and CONTRADICTION states before producing an ALLOW, WARN, BLOCK or HUMAN_REVIEW tool-authority verdict.

03

Operational example

A four-agent workflow reaches consensus, but every agent ultimately depends on the same upstream source. Sentinel treats the agreement as correlated rather than independent evidence, changes source availability or authority, then tests whether the consensus survives. If the result collapses, the shared dependency becomes a retained failure mechanism for later tests.

04

Evidence discipline

The public Live Trial currently exposes server-side Trace Audit, provenance, Goal Drift, Tool Authority, rate limiting, redaction and JSON audit export. Real-Web execution is kept separate and is shown as configured only when its provider credential is present on the server.