Accountability for AI that acts
AI needs supervision. Prove yours had it.
Glacis applies your rules when AI acts, blocks or escalates actions outside them, and leaves an independently verifiable record of the supervision that occurred.
One consequential action
The scribe produced a draft clinical note. Its PHI control recorded a pass.
At the model boundary, Glacis applied the configured PHI egress policy, evaluated 14 rules, allowed the draft, and created a signed operational record another party can verify.
Demonstration workflow data. The record shows that a named control ran and what it decided. It does not prove the note was clinically correct, the AI system was safe, or every encounter was covered.
- 09:14:02 workflow → ambient-scribe-draft-note action
- 09:14:02 PHI egress check → 14 rules evaluated control ran
- 09:14:02 0 rules triggered · policy mode enforce allowed
- 09:14:02 signed operational record created proof ready
- Action
- ambient-scribe-draft-note
- Rule
- PHI egress check · policy mode enforce
- Control
- 14 rules evaluated · 0 triggered
- Outcome
- pass · allowed · signed record
The supervision layer
Policies say what should happen. Logs say what the application recorded.
Glacis applies the approved rule while the AI action is in flight, blocks or escalates what falls outside it, and leaves an independently verifiable record of the supervision that occurred.
Visible
See where supervision is operating — and where it is not.
Control coverage, execution gaps and drift across the AI workflows you have put into production.
Controllable
Apply the rule before the action completes.
Allow, block, redact, escalate or require human review at the point where the AI is about to act.
Provable
Leave a record somebody else can check.
Each action routed through Glacis can produce a signed, portable operational record that does not require a Glacis account to verify.
Browser verification
Check a sample record yourself.
This is the same demonstration record shown above. Its signature and integrity checks run locally in your browser without a Glacis account or the protected underlying content. For known-key and provenance checks, open the full verifier.
What monitoring leaves unanswered
A conventional log is useful. It is not independent proof.
Most application logs remain under the operator’s control; signed or attested logs can provide stronger integrity. Glacis has a narrower job: connect the approved rule to the control decision and leave a record an outside party can verify.
Where Glacis fits
Keep the tools you have. Add the missing operational proof.
Governance, observability and guardrails remain useful. Glacis connects their intended state to a control decision while the AI is acting, then makes that decision independently checkable.
| Primary job | Before the action | Record for outsiders | |
|---|---|---|---|
| Governance | Defines intended policy | — not usually in the action path | — approvals and reports |
| Observability | Records application activity | — alerts or post-hoc analysis | — operator-controlled logs |
| Guardrails & policy engines | Evaluate configured rules | ✓ can allow, block or route | — implementation-dependent |
| GLACIS | Connects rule to action | ✓ allow, block or escalate | ✓ independently verifiable |
Glacis does not reveal a model’s internal reasoning. It shows which named control evaluated an action, what it decided, and whether the resulting operational record still verifies.
When somebody asks what happened
The answer should already exist.
A customer security review. A board or internal risk question. An insurance renewal. A regulator or auditor. An incident investigation. Do not reconstruct responsible behavior afterward. Operate in a way that leaves evidence while it happens.
- CustomerShow the controls around the AI you sell without asking the customer to rely only on your assertion.
- Board & riskAnswer what the AI was permitted to do, which control ran, and whether the action was allowed, blocked, or escalated.
- InsuranceBring operational evidence to a renewal, claim, or diligence review instead of reconstructing it from application logs.
- Audit & incidentGive reviewers a portable record they can check independently, including any later alteration.
How the proof holds up
The operational record can travel without the protected content.
When an action is routed through Glacis, its control decision can be signed and linked to prior records. Alter one and the verifier identifies the break.
Simulated for illustration
The proof is written to an open standard.
OVERT defines a portable format for signed operational evidence. A verifier can check the record without a Glacis account or disclosure of the protected underlying content.
Start with one consequential AI workflow.
If AI is already acting in production, show us the workflow and the rule that matters. If you want to prove the integration first, start free. The verifier is available to anyone.