Skip to main content
Reply IntelligenceGroup

DriftGuard · v0.0.1

Your agent says it checked. Nothing proves it did.

DriftGuard binds an agent's attestation to a hash of the artifact it actually read. If they do not match, nothing ships.

The problem

The agent asserts. You trust.

Autonomous agents produce clearance verdicts. Security audits, QA passes, review approvals. Nothing binds a verdict to what was actually inspected.

That works until it does not, and when it fails it fails silently, because a broken control still reports success.

How we found it

A gate that reported green for two months.

Our nightly pipeline runs 20+ autonomous agents that research, architect, audit, build and QA production code.

One security audit gate had been inspecting the wrong branch since 20 May. It reported green for two months. It could not fail.

No monitoring would have caught it. The control was working correctly. It was just working on the wrong thing.

DriftGuard attestation gate

The agent inspects the specification

How it works

Attestation is bound to an artifact rather than asserted by the agent.

  1. 01

    Record

    The audit records a SHA-256 of the exact specification it read.

  2. 02

    Re-hash

    The gate re-hashes that specification before ship.

  3. 03

    Refuse

    On mismatch, it refuses. Nothing ships against a stale attestation.

  4. 04

    Invariant locks

    We also enforce invariant locks that no agent can negotiate past: tenant isolation, inbound enquiry capture, email threading.

What happened when we turned it on

We pointed the new gate at 23 open agent pull requests.

All 23 failed.

Where it sits

Reply Intelligence Group controls what an AI is allowed to do. DriftGuard proves it still behaves that way after someone changes the software.

Control is the register and the ledger: what each agent may do, and what it did. A permission that survives only until the next pull request is not a control. The gate is what makes it one.

What we govern

Status

  • Running in production inside the ReplyOS pipeline.
  • Being productised as a GitHub Action.
  • Not yet generally available.

Get notified

One email when it's ready.

Leave an email address. We will send one message when DriftGuard is available.