ETOS GateKeeperETOS GateKeeper

Validation

Credibility demonstrated at the boundary.

Very few AI platforms can show evidence-boundary, authority-separation and governance testing. Six test categories were run against the gate and its controls. Findings are recorded, not asserted.

Real-world agent assurance

ETOS GateKeeper × Lovable

Independent Release Assurance for an AI Software-Development Agent

ETOS GateKeeper was placed around a real AI software-development workflow as an independent assurance boundary. Lovable retained responsibility for building, testing and remediation. EGK independently determined whether the submitted evidence was sufficient for the consequential release to proceed.

7

Assurance cycles

2

Additional defects identified and closed

0

Escaped from the Governed Release Candidate

Final determination

Controlled Production Release

The experiment demonstrated that independent governance can be introduced without removing the speed or autonomy of the engineering agent. EGK did not tell the agent how to build. It governed whether the resulting evidence justified proceeding.

The agent retained its capability. GateKeeper governed the consequence.

Scope: Demonstrated within this governed software-development and release workflow. This case does not claim validation across all autonomous-agent architectures or use cases.

Read the full case study

Test programme

Six categories, run against the gate.

  • V-01Baseline TestingConfirm the gate behaves as specified under normal decision load.Pass
  • V-02Adversarial TestingPressure the platform with hostile prompts and manipulated inputs.Pass
  • V-03Authority ChallengesAttempt to act without mandate, or to approve one's own output.Blocked
  • V-04Evidence ConflictsPresent contradictory evidence and test whether conflict is surfaced.Surfaced
  • V-05Governance Bypass AttemptsRoute around control tests, thresholds and required approvals.Blocked
  • V-06AI Decision Boundary TestsInduce the model to decide rather than recommend.Held

Findings

What the testing established.

Four findings recur across the validation record. Each is the differentiator an enterprise buyer is actually assessing.

F-01Confirmed

Evidence before assertion

In every recorded case, the platform required a bound evidence trail before an assertion could advance. Unsupported assertions were withheld rather than softened.

F-02Confirmed

Authority separate from evidence

Authority was consistently evaluated independently of the evidence presented. Persuasive evidence did not confer mandate, and mandate did not substitute for evidence.

F-03Confirmed

Human decisions retained

Under boundary testing, the platform continued to assess and recommend rather than exercise decision authority. Where the applicable governance required named human approval or countersignature, no test bypassed it.

F-04Confirmed

Governance remains intact

Bypass attempts were blocked and recorded as events. Control coverage was unchanged after adversarial testing, with no silent degradation observed.

Request the validation reports.

Full baseline, adversarial and governance-bypass testing records are available to qualified enterprise and partner reviewers on request.