This document specifies how an agent trust record is displayed, written and exported. A trust record describes one AI agent: its identity, interface, mandate and the parties who build, run and authorise it, together with a trust assertion over its identity, mandate and policy. Agent type is described with the Agentic AI Ontology [[AIAO]], and the record terms are aligned with the KR for Trust ontology [[KRT]].
DRAFT. This is a draft for discussion in the AI Knowledge Representation Community Group. It has not been adopted by the group. The fields, views and vocabulary alignment described here are open for comment, and the reference visualiser [[TRUST-RECORD-VIS]] is offered for testing. After review, the group will decide whether to publish a revised version as a Community Group Report.
To enter comments, suggestions, sections or evaluation results for this visualiser specification, open an issue or PR. Posts to the group's mailing list, public-aikr@w3.org, should carry [trustvisualiser] in the subject.
Implementation reports, test results and reruns are discussed separately from the model: open an issue with [trustvisualiser-impl] at the start of the title. Each report is listed in Implementation reports.
This specification covers how an agent trust record is shown, written and exported. Verification of the claims in a record is out of scope; that work belongs to [[KRT]] and the trust-layer technical note [[KR-OF-TRUST]].
Reference implementations:
A trust record describes one agent with thirteen declared fields in four groups, followed by a trust assertion over three of them. Fields marked proposed have draft descriptions open for review.
| Group | Field | Description |
|---|---|---|
| Identity | Agent name or identifier | The name, DID or other identifier the agent is known by. |
| Identity | Agent type | One class per AIAO dimension, plus cognitive capabilities. |
| Interface | Protocol (proposed) | How it talks to other agents and services, e.g. MCP, A2A, an HTTP API. |
| Interface | Where it lives and operates | URL, DID address or other. |
| Interface | Key publisher (proposed) | Who publishes the key set a verifier trusts: the agent's own origin, or an issuer or network the verifier has chosen. |
| Mandate | Mandate / functions | What the agent does. |
| Mandate | Authority (proposed) | Who granted it the power to act, and within which limits. |
| Mandate | Policy (proposed) | The rules it operates under, e.g. a published usage or data policy. |
| Parties | Developer | Writes the agent. |
| Parties | Deployer | Runs the agent. |
| Parties | User | Authorises use as per the mandate, under the policy. |
| Parties | Owner (proposed) | Who owns the agent. |
| Parties | Funder (proposed) | Who paid for the agent. |
The trust assertion states that the agent's identity, mandate and policy hold:
A record states what was declared. Checking a declaration against what the agent did is outside this specification.
A conforming visualiser MUST provide the three views below.
A conforming visualiser MUST export records as:
aiao:hasCapability.Records SHOULD be kept in the viewer's browser only, with nothing sent to a server.
Each view SHOULD link to the Agent Ontologies Explorer [[AGENT-ONTO-EXPLORER]], so readers can look up an AIAO class from a record.
A conforming visualiser MUST be usable with a keyboard and a screen reader, and SHOULD meet [[WCAG21]] level AA.
The reference implementation provides:
Barriers found by users are reported as issues tagged [trustvisualiser]. Automated checks find only some barriers; testing with people who use screen readers or magnification is planned.
AIAO describes what kind of agent is involved; KRT records whether a relying party could act on a claim the agent presented. The draft mapping below is preliminary and open for review.
| Trust record or AIAO term | KRT term (v0.1) | Relation |
|---|---|---|
| Agent (AIAO) | krt:Agent | AIAO classes describe the kind of agent. |
| Functional role (AIAO) | krt:Mandate | A role names the kind of work; a mandate states the scope granted. |
| Activity (AIAO) | krt:Action | AIAO activity classes, once defined, can type KRT actions. |
| Deployer | krt:Operator | Equivalent. |
| User | krt:Principal | Equivalent. |
| Policy | krt:DeclaredPolicy | Equivalent. |
| Developer | none | Gap; proposed as an addition to KRT. |
The visualiser's type picker uses AIAO v1.1 (eight dimensions). AIAO version 2.3 describes six dimensions and models functional roles as roles an agent plays. The two need to be brought into line.
Implementations of this specification, and test results that relate to it, are listed here. Each entry links to its evidence and carries one of three status levels:
| Implementation | Contributor | Scope | Status | Evidence |
|---|---|---|---|---|
| No reports yet. | ||||
Comments are especially welcome on these points:
Example records for real agents are especially useful for testing. The chair will collect the comments, revise this draft and the visualiser, and bring a revised version to the group for a decision on publication.
The following contributions have been made to this draft and to the visualiser. Further contributions are invited; see the status section for how to send them.
| Contributor | Contribution | Status |
|---|---|---|
| Larry Lewis (W3C Agent Trust Protocol CG) | Review of the trust record model: separate declared, verified, permitted and observed states; declared functions from granted authority; identifiers from service endpoints; test the role mappings against deployments | Partly implemented: "declared, not verified" labels and an "unknown" verification state in the visualiser. Other points open for discussion as issues |
| Yanfeng Liu (Nanjing University, V19) | Reviewer for audit and accountability; reproducible examples for evidence freshness, human approval and revocation | Listed as reviewer; examples offered |
| Francesco Marinoni Moretto | Commerce identity rows with pinned sources; who publishes the key set a verifier trusts (agent's own origin, or an issuer or network the verifier chose) | Contributed: rows confirmed with corrections; key-publisher column proposed and added as a proposed field; draft alignment issue between UCP and Web Bot Auth confirmed and reported to UCP (issue 1080) |
| Kenne Ives (AgentAvow) | did:web example and signed tool-definition test vectors; pinning the key from a source independent of the issuer | Offered; not yet run |