Framework overview
Agent Identity & Authority · OCC Agent Recordv0.1 · Draft for public comment · 2 October 2026

One record per agent: who it is, who it acts for, what it can really do.

The OCC Agent Record brings the whole family into a single document an operator publishes, a procurer requests and a regulator can read. It answers the 5 As, records the AIH-12 horizon, AIT-12 threshold status and AIE-12 evidence, and points to the F-ACT declaration and the revocation endpoint. It is self-declared: publishing one implies no conformance, certification or endorsement.

Specification

Fields

Identity
Record ID
record_id
RequiredStable identifier for this record (URI or UUID). Never reused.
Agent name
agent.name
RequiredHuman-readable name of the deployed agent.
Agent identifier
agent.identifier
RequiredVerifiable identifier — e.g. a DID, SPIFFE ID or signed key reference. See the agent-identity interop page.
Version
agent.version
RequiredDeployment version, including the underlying model version where known.
Authority (5 As — Authority, Access)
Principal
principal
RequiredThe person or organisation the agent acts for.
Operator and contact
operator
RequiredWho runs the deployment and how to reach them.
Mandate
mandate
RequiredThe written purpose and limits, with an expiry date.
Declared authority
authority.declared
RequiredWhat the agent is authorised to access, spend or change.
Effective authority
authority.effective
RequiredWhat it can actually reach, from a dated reconciliation. List every gap.
Authority ceiling
authority.ceiling
RequiredThe highest delegation-ladder rung permitted (from AIT-12).
Classification
AIH-12 horizon
aih12.horizon
RequiredH1–H12, with who classified it and how (self, second party, independent).
AIT-12 threshold
ait12.threshold
RequiredTn matching the horizon, and status: meets · partially meets · does not meet.
Threshold gaps
ait12.gaps
OptionalControls not yet in place and the conditions applied meanwhile.
AIE-12 evidence profile
aie12.profile
RequiredEn, plus whether evidence is at, above or below profile.
Evidence and conformance (5 As — Activity)
Evidence register
evidence[]
RequiredEach item: control, evidence class (Assertion → Independent review), producer, date, link, and what could not be checked.
F-ACT declaration
f_act.declaration
OptionalLink to the GUARD declaration and level, if any. Required from T5.
PACTE assessment
pacte
OptionalLink to the most recent PACTE assessment, if any.
Control (5 As — Action, Accountability)
Revocation endpoint
revocation.endpoint
RequiredWhere and how authority is withdrawn; T-RUE compatible from T6.
Revocation last tested
revocation.tested
RequiredDate of the last successful interruption and revocation test.
Accountable person
accountable_person
RequiredA named role that answers for the agent.
Incident and redress route
redress
RequiredHow an affected person reports harm and gets an explanation.
Incident history
incidents[]
OptionalDisclosed incidents and their outcomes. Failures are part of the record.
Automated decisions & transparency (optional)
Decisions made solely by the agent
adm.solely_automated_decision_types
OptionalKinds of decisions the agent makes without a person deciding, where the decision could significantly affect someone. Mirrors the Australian Privacy Act transparency duty from 10 December 2026 (APP 1.7–1.9).
Decisions the agent substantially shapes
adm.substantially_related_decision_types
OptionalKinds of decisions where the agent does something substantially and directly related to a person making the decision.
Kinds of personal information used
adm.personal_information_kinds
OptionalThe kinds of personal information the agent uses in those decisions.
Privacy policy
adm.privacy_policy
OptionalLink to the privacy policy where the operator makes the legal disclosure. The record points to it; it does not replace it.
AI-interaction disclosure
eu_art50.ai_interaction_disclosure
OptionalHow people are told they are dealing with an AI system (EU AI Act Art. 50(1), applies from 2 August 2026).
Synthetic content marking
eu_art50.synthetic_content_marking
OptionalHow generated audio, image, video or text is marked as machine-generated (Art. 50(2)), e.g. C2PA manifest or watermark.
Lifecycle
Status
status
Requiredactive · suspended · revoked · retired.
Issued
issued
RequiredDate this version of the record was issued.
Reassess by
reassess_by
RequiredFrom the AIT-12 reassessment interval, or sooner on material change.
Alignment

Agent identity: alignment with NIST NCCoE work

The NIST National Cybersecurity Center of Excellence (NCCoE) published a concept paper, Accelerating the Adoption of Software and AI Agent Identity and Authorization, on 5 February 2026; public comments closed on 2 April 2026. It proposes showing how OAuth 2.0, OpenID Connect, SPIFFE/SPIRE and Next Generation Access Control (NGAC) can be applied to agents. OCC tracks that work and aligns the Agent Record to it; where NIST guidance is final, it prevails. OCC is not affiliated with or endorsed by NIST.

AreaIdentity practiceWhere it goes in the record
IdentificationEach agent has its own non-human identity, distinct from the person or service that launched it.agent.identifier — a stable identifier (e.g. a SPIFFE ID, OAuth client ID or DID). Never a shared human account.
AuthenticationAgents authenticate with short-lived, verifiable credentials rather than long-lived secrets.Evidence entry against the identity control, with the credential type and lifetime. Digest the configuration if it can be shared.
AuthorizationPermissions are scoped to the task and enforced at the resource, with least privilege.authority.effective lists what the agent can actually do; authority.declared what it is meant to do; reconciled_on shows when they were last compared.
DelegationWhere an agent acts for a person or another agent, the chain of authority is explicit and attenuated at each hop.principal names who the agent acts for; declare each downstream agent and the scope passed to it (see multi-hop delegation).
Auditing & non-repudiationActions are logged and attributable to the agent and its principal.F-ACT Audit dimension; evidence entries with digests and attestation levels A1–A3.
RevocationCredentials and delegations can be withdrawn quickly when something goes wrong.revocation.endpoint and revocation.tested (T-RUE). An untested route is recorded as a gap.

Agents that delegate to other agents should declare the chain. See multi-hop delegation.

Example

A record that honestly shows its gaps

A fictional H5 procurement agent. Note the effective-authority gap, the “partially meets T5” status and the evidence recorded below profile — a good record says these things out loud.

{
  "$schema": "https://openconformance.org/occ/agent-record.schema.json",
  "occ_agent_record": "0.1",
  "record_id": "urn:uuid:3f0c2a8e-1b7d-4c55-9e1a-000000000000",
  "agent": {
    "name": "Example Procurement Assistant",
    "identifier": "did:web:example.org:agents:procure",
    "version": "2.3.0 (model: vendor-model-2026-08)"
  },
  "principal": "Example Pty Ltd — Finance team",
  "operator": {
    "name": "Example Pty Ltd IT",
    "contact": "[email protected]"
  },
  "mandate": {
    "purpose": "Raise purchase orders for approved suppliers",
    "limits": "AUD 5,000 per order; AUD 20,000 per week; approved supplier list only",
    "expires": "2027-03-31"
  },
  "authority": {
    "declared": [
      "Read supplier catalogue",
      "Create purchase orders up to limits"
    ],
    "effective": [
      "Read supplier catalogue",
      "Create purchase orders up to limits",
      "Read all finance mailboxes (gap: inherited from service account)"
    ],
    "reconciled_on": "2026-09-28",
    "ceiling": "Act within limits"
  },
  "aih12": {
    "horizon": "H5",
    "classified_by": "self"
  },
  "ait12": {
    "threshold": "T5",
    "status": "partially meets",
    "gaps": [
      "Least-privilege credentials: mailbox access to be removed by 2026-10-15"
    ]
  },
  "aie12": {
    "profile": "E5",
    "status": "below profile",
    "note": "Revocation test is a demonstration, not yet reproducible"
  },
  "evidence": [
    {
      "control": "Interruption and revocation tested",
      "class": "Demonstration",
      "producer": "self",
      "date": "2026-09-20",
      "unchecked": "Behaviour under network partition"
    },
    {
      "control": "Authority budget",
      "class": "Reproducible test",
      "producer": "self",
      "date": "2026-09-22",
      "link": "https://example.org/tests/budget"
    }
  ],
  "f_act": {
    "declaration": "https://example.org/.well-known/f-act.json",
    "guard_level": "GUARD 1"
  },
  "revocation": {
    "endpoint": "https://example.org/agents/procure/revoke",
    "tested": "2026-09-20"
  },
  "accountable_person": "Head of Finance Operations",
  "redress": "https://example.org/agents/report",
  "incidents": [],
  "adm": {
    "substantially_related_decision_types": [
      "Recommending which supplier quote is accepted"
    ],
    "personal_information_kinds": [
      "Supplier contact names and business email addresses"
    ],
    "privacy_policy": "https://example.org/privacy#automated-decisions"
  },
  "eu_art50": {
    "ai_interaction_disclosure": "disclosed at start of interaction"
  },
  "status": "active",
  "issued": "2026-10-02",
  "reassess_by": "2027-04-02"
}
Where to publish it
We suggest /.well-known/occ-agent-record.json on the operator’s domain, or one record per agent linked from there. The location is a proposal for comment, not a requirement.