Standards

A public standard index for AI Agent identity.

Standards make AIAA read like infrastructure. Each section defines how agent records, evidence, review, registry states, and public trust signals should work.

0.1
draft version
7
standard groups
Public
index format
Review
decision layer
Registry
record output

Document Index

Standards should look like reference material.

The page uses chapter rows, version metadata, clauses, and status fields instead of large marketing blocks.

01

Identity Standard

Defines agent name, owner, company, AIAA ID, country, category, and public record format.

Draft
02

Capability Standard

Defines what an agent does, what evidence supports the claim, and which tasks are in scope.

Draft
03

Safety Standard

Defines risk notes, failure behavior, human override, permission limits, and prohibited claims.

Draft
04

Registry Standard

Defines public registry fields, verification states, status changes, expiry, and revocation logic.

Draft
05

Evidence Standard

Defines logs, screenshots, repository links, deployment notes, benchmark files, and reviewer traceability.

Draft
06

Review Standard

Defines screening, reviewer decision states, information requests, appeals, and final certificate issuance.

Draft
07

Public Trust Standard

Defines how AIAA displays signals without confusing popularity, certification, and public identity.

Draft

Clauses

The first clauses are practical.

These clauses can expand into full policy pages after the UI structure is accepted.

ClauseRequirementPublic effect
ID-001Every public agent record must have one AIAA ID.Visitors can verify identity without guessing.
ID-002Owner fields must identify the accountable operator.Public accountability stays visible.
EV-001Every certification decision must cite evidence types.Reviewer trust becomes visible.
EV-002Private evidence should be summarized without exposing sensitive data.Public proof stays useful and controlled.
RV-001Expired and revoked records must stay visible.Registry history remains auditable.
RK-001Ranking pages must separate popularity and certification.Signals stay honest and readable.
TR-001Brand and level labels must avoid ambiguous abbreviations.Browser translation remains stable.

Status Labels

Policy status needs public labels.

Visitors and applicants should know whether a standard is a draft, current rule, archived rule, or review item.

LabelMeaningUsage
DraftNot final. Open for internal review.Early AIAA page structure.
CurrentAccepted active rule.Certification and registry logic.
Under ReviewActive rule being checked.Policy updates and appeals.
ArchivedOld rule preserved for history.Deprecated public records.

Next Action

Connect standards to certification.

The standards page should become the source of truth for registry fields, review decisions, public labels, and ranking boundaries.