PRODUCT DIRECTION

Authority infrastructure for consequential AI.

Verimand builds implementation, enforcement and enterprise infrastructure around VAGP. The 0.3 reference profile binds authority to attested Agent DNA; the frozen 0.2 cloud proofs remain versioned evidence.

Enterprise control plane · PlannedMCP server available

PRODUCT PRINCIPLE 01

VAGP 0.3 is public as an open protocol. The Verimand MCP Authority Server is now available for agent-native authority tooling.

PRODUCT ARCHITECTURE / DISTINCT RESPONSIBILITIES

01 / Open protocol

VAGP

PUBLIC / APACHE-2.0

The specification, authority semantics, schemas, vectors and conformance model are publicly available as VAGP 0.3.

Explore the protocol

02 / Interfaces

Developer access

REFERENCE CODE · PRODUCT INTERFACES PLANNED

API for systems. SDK for developers. MCP for agent-native access. These interfaces carry requests; they do not confer authority.

Inspect the integration direction

03 / Enforcement

Authority Gateway

REFERENCE RUNTIME · MCP GATEWAY PLANNED

The protected boundary between agents and tools, services or APIs. Verify current authority before a consequential action.

Understand enforcement

04 / Commercial infrastructure

Verimand Platform

IN DEVELOPMENT / PLANNED OFFERING

The future managed service and enterprise control plane around VAGP: mandates, Agent DNA, revocations and evidence.

Explore the platform direction

THE PRODUCT BOUNDARY

An authority layer, not a replacement stack.

Identity establishes an actor. Policy expresses organisational rules. Approval introduces human decisions. Agent frameworks orchestrate work. Verimand’s distinct responsibility is to preserve the evidence chain that explains why one exact autonomous action falls within current delegated authority.

Identity providerComplements

Policy engineFeeds and follows authority evaluation

Agent runtimeRemains outside the trust boundary

Protected resourceVerifies locally before consequence

REAL MULTICLOUD AUTHORITY

One authority model. Across cloud boundaries.

MC-02 validates VAGP authority enforcement across real Microsoft Azure and Google Cloud boundaries. The result is evidence for the authority model and gateway enforcement path, not a claim of production SaaS availability.

Identity establishes who the agent is. Verimand governs what it is authorized to do. Bring your identity. Keep one authority model.

Inspect validation evidence

AzureVerimand Authority Layer / VAGPGoogle Cloud

Azure → GCPREAL VALIDATED

GCP → AzureREAL VALIDATED

Google Workload Identity FederationREAL VALIDATED

Real GCP → Azure replay/revocation enforcementVALIDATED

SPIFFE/SPIRE SVID issuanceREAL VALIDATED

Architecture is broader than current integration coverage. Microsoft Entra Agent ID is not yet validated, and SPIFFE Gateway verifier integration is not yet fully validated.

OPEN CORE SEMANTICS

One protocol.
Many operating models.

VAGP remains vendor-, infrastructure- and jurisdiction-neutral. The Verimand product direction adds administration, integration and operational evidence around that stable core.

Inspect VAGP Connect via MCP MCP GitHub Learn the authority model Open the VAGP v0.2 reference Discuss an authority pilot

ILLUSTRATIVE AUTHORITY PATH STRUCTURALLY VALID

BOUNDAgent 17Exact witness · no path merging

PRODUCT ARCHITECTURE · CONCEPTUAL COMPOSITION

A distinct authority boundary.

The core exists. The enterprise operating surface remains a product direction, not a generally available control plane.

Existing identity

Establish the caller with your identity provider.

Shared Authority Gateway Runtime

Map trusted identity to the exact request; provider adapters remain cloud-specific.

VAGP v0.2

RESOLVE → BIND → DERIVE → VERIFY. Frozen reviewed semantic core.

Authority Graph

One complete current path and its mandate lineage.

Policy / interaction layer

Keep policy, approvals and business controls distinct. Future enterprise integration.

Protected resource

VERIFY at the consequence boundary before execution.

RESOLVE
Find one valid authority path.
BIND
Bind identity, action, resource and trusted context.
DERIVE
Create one process-local execution grant.
VERIFY
Validate current authority before execution.

Conceptual responsibilities, not a mandatory serial API topology. Current unsigned grants remain in one authoritative process.

AUTHORITY EXPLORER · READ-ONLY CONCEPT

AUTHORITY EXPLORERREAD-ONLY CONCEPT

Why was this action allowed?

A presentation prototype for inspecting evidence. Not a shipping administration product.

Identity → Agent

Authenticated workload → cloudops-agent. The subject comes from trusted identity mapping, never a claimed Agent field.

Mandate → Delegation

M-100 → D-204. Head of Cloud Operations delegates development scope only. Child authority never exceeds parent authority.

Authority Path → Bound action

One complete qualifying path. cloud.vm.stop is bound to vm:development:17 and its authoritative context.

Current status → Verification

ACTIVE at simulated execution. Resource-side VERIFY returns VERIFIED before the application reports EXECUTED.

Authority Witness concept · explanatory evidence · not a credential or cryptographic receipt.

INTENDED PRODUCT SURFACE

01Authority modelling

Graph-native organisational mandates, delegation lineage and constrained authority administration.

02Operational evidence

Current status, resource context, Authority Witness evidence and future cryptographic receipts.

03Enterprise integration

Future identity, policy, agent and cloud adapters without embedding their semantics in VAGP.

04Sovereign operation

Portable deployment profiles designed for substitutability, customer control and auditable dependency risk.

HONEST IMPLEMENTATION FRONTIER

TODAY

Authority Platform foundation

Frozen VAGP v0.2 semantics, a shared Authority Gateway runtime, a local simulated CloudOps application, and bounded live Google Cloud and Microsoft Azure authority PoVs.

Local Proof of Value

Contract2Authority + Agentic Managed Services

MCP Authority Gateway enforcement, Contract-to-authority modelling, managed agentic operations, durable enterprise state, production integrations, portable signed grants and cryptographic receipts remain roadmap capabilities.

Gateway and protected execution remain future