Autonomous Volition Credentials

Identity vs. authority vs. volition vs. execution

Identity

Who an actor is. A signing key, a name, a registration.

Authority

What an actor may invoke under policy. Often local to a system.

Volition

The delegated operational intent encoded in an AVC. Scoped, expiring, revocable, hierarchical.

Execution

What the actor actually did. Recorded as a trust receipt.

Volition, defined precisely

EXOCHAIN does not claim that AI systems possess consciousness or human-like will. Volition here is operational and delegated. It refers to the authorized intent that a principal (human, organization, agent, or holon) hands to a subject for the purpose of autonomous action.

Volition is bounded. It has a scope (a set of permitted actions), a policy domain, optional constraints (such as a ceiling, an allowlist, a region), a validity window, a parent credential where applicable, and a signature from the issuer.

AVCs are operational credentials, not securities. They confer authority to pursue declared actions; they do not represent ownership, equity, or revenue rights.

Worked examples

Human → Agent

A finance leader issues an AVC to a procurement agent. Scope: procure.search · procure.quote · procure.purchase. Constraints: ceiling_usd ≤ 50000, vendor allowlist. Validity: 6 months.

Agent → Sub-Agent (delegation)

The agent issues a derivative AVC to a sub-agent for a narrower window: procure.search · procure.quote only, ceiling_usd ≤ 5000. Validation rejects any attempt to widen scope beyond the parent.

Org → Department agent

An organization delegates a department-scoped agent. Receipts reference the org as ultimate principal in the delegation chain.

Holon participation

A multi-organization holon issues AVCs to validators it has vetted. Holon-issued AVCs participate in custody attestation across jurisdictions.

Anatomy of an AVC

The on-chain canonical encoding is deterministic; the JSON below is the human-readable view rendered by the SDK.

{
  "id": "avc_001",
  "subject_actor_id": "actor_003",
  "issuer_actor_id": "actor_002",
  "policy_domain_id": "aperture.procurement",
  "scope": {
    "actions": ["procure.search", "procure.quote", "procure.purchase"],
    "constraints": {
      "ceiling_usd": 50000,
      "vendor_allowlist": "aperture-tier1"
    }
  },
  "not_before": "2026-02-12T18:00:00Z",
  "not_after":  "2026-08-12T18:00:00Z",
  "signature": {
    "algorithm": "ML-DSA-65",
    "value": "0xa11d…f0c2"
  }
}

Sample AVC · human-readable view

Validation is fail-closed

Validation does not consult pricing or settlement state. It evaluates signature, validity window, scope inclusion, parent chain, revocation status, and policy expressions deterministically. If any check fails or is indeterminate, validation returns FAIL with a structured reason code.

This guarantees that trust never depends on the economic layer being available, and that pricing changes can never weaken credentialing.

Autonomous Volition Credentials.