We wrote the specification. Vortalis is the reference implementation.

Vortalis is built and tested against AGAP®, the AI agent runtime governance specification we authored.

What AGAP® is

The Agent Governance and Action Protocol (AGAP®) is the specification that defines the runtime governance requirements for AI agent systems. It specifies how agents must authenticate, how their actions must be authorised, how sensitive data must be protected, and how every decision must be recorded.

AGAP® was created by MTE Software Ltd as the specification Vortalis's own engineering builds and is tested against, control by control. We intend to publish it openly under CC BY 4.0; that publication has not happened yet, so treat any reference to a standalone external specification document as forward-looking rather than live today.

Conformance is structured in three tiers (Core, Extended, and Full), allowing organisations to adopt governance incrementally and verify each level independently.

A named specification with a controlled conformance signal

A Named, Testable Specification

AGAP® is the specification Vortalis's own engineering is built and tested against, control by control, not marketing language layered on afterward. We intend to publish it externally; until then, the per-control conformance mapping is available on request.

Controlled Conformance Signal

AGAP Protocol® and AGAP CONFORMANT® are UK-registered trade marks held by MTE Software Limited (UK00004357019 and UK00004357025, registered 15 June 2026). The specification itself is not yet externally published; the conformance mark is controlled regardless.

Regulatory Mapping by Architecture

AGAP® controls are mapped to selected EU AI Act articles, DORA, and NIST AI RMF requirements, per control and by declared status. A mapping is not a conformance or compliance finding, and Article 10 (training data) is only partly addressed. Evidence for a mapped control is produced from the same governance records where a control exists; some mapped obligations, such as conformity assessment, rest on evidence the deployer supplies.

Conformance per control is recorded

Conformance per control is recorded, with the difference between letter-code-bound and capability-bound rows set out in the per-control mapping, which is available on request, rather than buried in the test suite.

Every requirement is recorded in one of three categories. A requirement is letter-code-bound when a named conformance test file binds it, so a regulator can read the requirement, the assertion, and the implementation the assertion exercises together. It is capability-bound when the implementation exists and is exercised by the broader test suite but no dedicated letter-coded test has been bound yet. The remainder is not represented, where neither a binding nor a clear implementation pointer exists today. The binding programme is in progress, and capability-bound rows convert to letter-code-bound as named test files land.

A capability-bound row is not marketed as if it were letter-code-bound. The categorisation lives in public so the difference is stated in the per-control mapping rather than buried in the test suite. The suite is written and run by MTE Software in its own CI; it is not an independent assessment. Every Vortalis release is exercised against the AGAP® Conformance Test Suite in CI, alongside several thousand platform-wide tests.

Per-tier conformance breakdown

AGAP® Core

18 controls
  • 18 of 18 letter-code-bound
  • 0 of 18 capability-bound

Foundational governance controls: policy enforcement, credential isolation, audit logging, kill switches, and role-based access.

AGAP® Extended

11 controls
  • 11 of 11 letter-code-bound
  • 0 of 11 capability-bound

Advanced capabilities: anomaly detection, human-in-the-loop approval, inter-agent governance, runtime resource limits, and workflow enforcement.

AGAP® Full

7 controls
  • 1 of 7 letter-code-bound
  • 0 of 7 capability-bound

Ecosystem features: governance spine with principal chain tracking, federated governance, cross-tenant policy negotiation, and regulatory export automation. F-09, F-10, and F-12 test files exist in the suite but exceed the public F-01..F-07 numbering range named in AGAP® Working Draft 04.

Today the totals are 18 of 18 Core letter-code-bound, 11 of 11 Extended letter-code-bound, and 1 of 7 Full letter-code-bound. The Core and Extended bands are now fully letter-code-bound; the remaining Full-band controls are blocked on AGAP® working-group reconciliation of the underlying requirement statements, not on engineering. The suite also contains test files for F-09, F-10, and F-12, which exceed the public F-01..F-07 range in AGAP® Working Draft 04; the AGAP® working group is the right venue to decide whether to extend the public Full range, reclassify those bindings into Extended, or park them under a profile extension. The full per-control mapping is available on request from the Vortalis team (the repository that holds it is private).

AGAP® is the specification. AGAP CONFORMANT® is the mark.

AGAP Protocol® (the Agent Governance and Action Protocol specification) and AGAP CONFORMANT® (the certification mark for implementations that pass the letter-code-bound conformance suite above) are separate, UK registered trade marks held by MTE Software Limited. The specification will be published under Creative Commons Attribution 4.0 (CC BY 4.0) once full external publication is complete (see above); the certification mark is controlled by MTE Software Limited, so that "AGAP CONFORMANT" means the same verifiable thing wherever it appears.

Vortalis is the reference implementation and the first holder of the mark. Other implementations wishing to use AGAP CONFORMANT® on their own conformance results should contact the AGAP working group.

Governance you can verify

Vortalis is built against a named specification, with per-control conformance results available on request. No black boxes. No trust-us claims.