Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Public-sector auditability profile for verifiable AI agents

Aperta
  • Qualcosa non va?
#209 5 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@fernandacamiladecarli ci sta già lavorando.

Dal 7/9/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Spec section affected

§3 Trust Record fields; §4 Verification / conformance guidance; potentially an informative annex for sector-specific profiles.

Problem

The current TRACE specification appears to focus on general evidence records for verifiable AI agent activity, but it does not yet define a public-sector auditability profile for agents used in procurement, public oversight, or administrative decision-support.

For public institutions, auditability requires more than a record that an agent acted. Auditors and oversight bodies may need evidence of:

agent identity;
delegated authority;
authorized tools;
data access;
human approval or override;
policy exceptions;
incident or escalation triggers;
retention requirements for later review.

Without a public-sector profile, different agencies or vendors may implement evidence records inconsistently, making later audit, accountability, and oversight harder.

Proposed change

Add an optional, non-breaking public-sector auditability profile to TRACE, either as an informative annex or sector-specific guidance.

Proposed normative/informative text:

Implementations MAY support a public-sector auditability profile for AI agents used in procurement, oversight, regulatory, or administrative decision-support contexts.

When this profile is used, Trust Records SHOULD include sufficient evidence to support later institutional review of:

the identity and version of the agent;
the public authority, delegation, or approval under which the agent acted;
the tools, systems, or external services accessed by the agent;
the categories of data accessed or processed;
any human approval, override, denial, or escalation;
any policy exception or rule violation;
incident, near-incident, or escalation triggers;
retention metadata necessary for audit or oversight review.

This profile SHOULD NOT require disclosure of protected, confidential, classified, or legally restricted information in the Trust Record itself. Where appropriate, the Trust Record MAY reference protected evidence through controlled-access identifiers, hashes, or other mechanisms that preserve verifiability without exposing sensitive content.

This profile is intended to support public accountability, auditability, and institutional oversight without changing the core TRACE wire format.

Backward compatibility

Non-breaking (new optional field, informative addition)
Breaking (removes or changes required field, changes wire format, changes algorithm set)

Motivation

Public institutions are increasingly exploring AI agents for procurement, auditing, regulatory, and administrative workflows. In these settings, accountability depends not only on technical performance, but also on whether later reviewers can verify who authorized the agent, what it did, what data and tools it used, whether a human approved or overrode the action, and whether exceptions or incidents were escalated.

A public-sector auditability profile would help agencies, vendors, auditors, and oversight bodies use TRACE in a more consistent way. It could also connect TRACE with adjacent AgenTrust work, especially Agent Manifest fields related to identity, delegated authority, tools, policies, provenance, and human approvals.

This proposal could connect to Agent Manifest fields, but I am opening it here because the main contribution would be a TRACE profile for public-sector auditability and evidence events.

My background is in public oversight and procurement accountability, not core infrastructure engineering. I am interested in whether this kind of governance-focused profile would be useful for the AgenTrust ecosystem.

Related issues or PRs

None yet.

Lingua principale
Python
Stelle
37
Fork
33
Merge medio
1g 4h
PR unite (30g)
122

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di agentrust-io/trace-spec

Tutte le issue di agentrust-io/trace-spec

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.