Claims Imladri can prove
Buyer-readable claims tied to current proof surfaces.
These are the claims a customer can support from today's Profile, CLI, SDK/adopter certification, scanner, detector, and proof packet evidence. Unsupported enterprise, payment, and absolute-security language is intentionally excluded.
Supported Claims
| Claim | What it means | Proof source |
|---|---|---|
| Action-boundary enforcement | Wrapped SDK/adopter paths and strict preflight can stop prohibited actions before the tool/function body runs. | Runtime activity, blocked event, zero dangerous body-call evidence, proof digest. |
| Per-decision evidence | Each monitored decision can land in Profile with action, status, source, latency, request identity, authority context, and integrity metadata. | Profile Deployments timeline, proof export, trace reference JSON. |
| Profile-visible monitoring | A customer can see the active agent, policy state, trial usage, monitored activity, proof state, AI-card summary, and proof-health alerts. | Profile Home, Deployments, Proof, Account. |
| Free Proof Trial | The default customer path supports one monitored agent with quota-limited proof usage. | Profile trial meter and Worker quota responses. |
| Buyer/auditor proof packet | Profile exports buyer-readable JSON/Markdown proof packets and auditor-redacted share links. | Proof tab packet export, public proof share, verifier. |
| Scanner and detector lanes | The scanner reports missing boundary patterns plus detector findings for prompt, secret, PII, URL, unsafe-content, and tool-argument risks. | Scanner JSON/SARIF/Markdown, Profile scanner lane, detector summary. |
| Certified SDK/adopter paths | Certified lanes prove the adapter surfaces that were actually run and uploaded to Profile. | SDK certification packets and adopter pages. |
Not Claimed
| Universal framework coverage | Certified proof covers listed adapter surfaces, not every plugin or custom wrapper. |
| Hosted credential proof without credentials | Missing hosted probe credentials stay visible as missing or not applicable. They are not counted as a pass. |
| Enterprise readiness | SSO, SCIM, procurement, customer SIEM export, and formal compliance programs are outside this customer proof-trial claim set. |
| Payment or subscription support | This page does not claim billing, payment, subscription, or checkout implementation. |
| Absolute security | Imladri reduces and proves specific boundary behavior. It does not claim that any system is 100% secure. |
Customer Review Path
| 01 Start in Profile | Confirm the active agent id, policy version, AI card, proof health, and trial usage. |
| 02 Run evidence | Run one allowed action and one blocked risky action through the wrapped runtime/API path. |
| 03 Attach lanes | Upload scanner, SDK certification, detector, red-team, tuning, or reviewer evidence when those lanes are part of the proof. |
| 04 Verify packet | Export JSON/Markdown, check digest/hash-chain state, and create an auditor-redacted share only after proof is current. |
| 05 Read limitations | Review not-claimed rows and packet limitations before sending evidence externally. |