VEKLOMCOGNITIVE_SHIELD

GOVERNANCE PROTOCOL v2.0

Policy Engine active
Covenant Protocol · v2.0.0LIVE

The connection is the asset.

One call that discovers, authorizes, executes, proves, and learns. MCP asks what you can do. APIs do it. Covenant does both — and proves it.

agent · any model◆ covenant · 9 governed phasescapability · tool / api / agent⛓ sealed proof → PGL
covenants
authorized
denied
quarantined
agents
capabilities
The unified call

One call. Nine governed phases. A proof at the end.

MCP asks what an agent can do. An API does it. Neither makes the call accountable. Covenant fuses both into a single governed connection that decides, executes, and proves — every time.

01Identity
02Policy
03Safety
04Cost
05Approval
06Execution
07Evidence
08Audit
09Response

Self-describing

Every actor and capability carries verifiable identity. Agents ask “what can I do, right now?” and get a policy-true answer.

Self-authorizing

System, owner, and runtime policies compose at call time. Conflicts resolve deterministically before a single side effect.

Self-proving

Each call seals a hash-chained evidence record. The proof is the product — replayable, tamper-evident, audit-ready.

Self-improving

Trust, behavioral baselines, cost attribution, and risk scoring update on every call. The connection learns.

Why it's a new category
vs MCPMCP discovers tools. Covenant discovers, authorizes, executes — and proves it.
vs REST APIAn API is a stateless call. A covenant is a governed relationship with trust + evidence.
vs API GatewayGateways do auth + rate limits. Covenant adds policy composition, safety, and proof.
vs Service MeshA mesh moves bytes with mTLS. Covenant moves capability with accountability.
Covenant · Covenant Protocolpart of the Veklom ecosystem