Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Governance-decision evidence as a composable layer in the Trust Record schema

Open
  • Is something wrong?
#220 3 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
34/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
go
Domain
documentation

Research direction

Start by reading §3.1 and §4.3, especially the existing transparency and tool_transcript patterns, then review the referenced verifier and companion paper for the proposed evidence requirements. The work is to define how an external governance-decision artifact is referenced and verified without requiring TRACE to define its format. Done means the optional addition is specified, backward-compatible, and supports the described verification needs.

Written by the indexing model from the issue text.

Description

Spec section affected

§3.1 (Logical schema — Trust Record field set), §4.3 (Bindings TRACE adds)

Problem

The policy field in §3.1 binds a policy hash and enforcement mode to the Trust Record. This proves which policy was in force during execution. It does not prove what governance decision that policy produced for a specific agent action, what the evaluation inputs were, or whether the decision record is independently verifiable with keys not controlled by the platform operator.

The tool_transcript field captures what tools were called, with what parameters, and what responses were returned. This proves what the agent did. It does not prove what governance evaluation was applied to each action before it was permitted or denied.

These are distinct evidence requirements. A runtime attestation proves the environment was intact and the policy was bound. A governance-decision record proves the per-action evaluation: what was requested, what policy was evaluated, what the decision was, and that the resulting record was not altered after evaluation. For cross-organizational AI agent interactions, a counterparty needs to verify both: (a) the runtime was trustworthy (covered by TRACE) and (b) the governance decision applied to a specific agent action was correctly recorded and is independently verifiable (not currently covered).

§4.3 lists four bindings TRACE adds on top of existing standards: policy claim, data_class claim, tool_transcript claim, and AI-agent execution profile. None of these bindings capture governance-decision-level evidence as a composable artifact that can be verified independently of the platform that produced it.

Proposed change

TRACE should define a composition interface in §4.3 that allows governance-decision evidence records to be referenced from or bound to a Trust Record. This would enable a Trust Record to link to a governance-decision evidence artifact carrying:

The governance policy identifier evaluated for a specific agent action
The evaluation inputs (request metadata, entity identifiers, classification results)
The governance decision outcome (permit, deny, modify, flag)
A cryptographic signature over the canonicalized decision record, produced with keys not controlled by the platform operator
A chain-integrity field linking the current decision record to the prior record, enabling tamper-evident sequences across the lifecycle of an agent session

This does not require TRACE to define the governance-decision evidence format itself. It requires TRACE to define how an external governance-decision evidence artifact, produced by a governance layer operating alongside the runtime, can be referenced from a Trust Record so that verifiers can validate both layers in a single verification pass.

In §3.1, this would appear as an optional governance_evidence field (or equivalent) carrying a reference URI, a digest of the governance-decision record, and the verification key identifier, following the same pattern TRACE already uses for transparency (URI + cryptographic anchor) and tool_transcript (hash + reference).

An existing open-source implementation of governance-decision evidence verification exists: github.com/scarpprotocol/scarp-verify (Apache 2.0, Go, zero external dependencies, offline verification, RFC 8785 canonicalization). The architectural requirements for governance-decision evidence are described in a peer-reviewed companion paper (DOI 10.5281/zenodo.21927017).

Backward compatibility

Non-breaking (new optional field, informative addition)

A composition interface for governance-decision evidence would be additive. Existing Trust Records remain valid. Verifiers that do not support governance-decision evidence ignore the new optional field. Verifiers that do support it gain the ability to validate both runtime attestation and per-action governance decisions in a single verification pass.

Motivation

Runtime attestation and governance-decision evidence address different regulatory and operational requirements:

The EU AI Act (high-risk obligations, effective December 2027) requires evidence of governance decisions applied to AI systems, not only evidence of runtime integrity. Article 12 mandates logging that enables verification of compliance at the decision level.
The OSAIA SAFE RFC review framework asks whether authorization assumptions were correct and whether the model recognized scope boundaries. These are governance-decision questions that runtime attestation alone cannot answer.
Contractual flow-down requirements already in force (e.g., Fannie Mae LL-2026-04, effective August 2026) require vendors to maintain AI governance records demonstrating policy enforcement at the per-action level.
Cross-organizational agent interactions require both parties to independently verify the other's governance decisions, not only their runtime environment. The principle stated in the TRACE announcement applies equally here: evidence that is portable, independently verifiable, and not controlled by the vendor producing it must extend to governance decisions, not only to runtime attestation.

Related issues or PRs

OSAIA SAFE RFC Issue #24: Lifecycle infrastructure dependencies (github.com/osaia/safe-rfc)
OSAIA SAFE RFC Issue #25: Identity infrastructure dependencies (github.com/osaia/safe-rfc)
OSAIA SAFE RFC Issue #26: Composition governance dependencies (github.com/osaia/safe-rfc)
Governance-decision evidence verifier: github.com/scarpprotocol/scarp-verify
Companion paper: DOI 10.5281/zenodo.21927017

Dominant language
Python
Stars
37
Forks
33
Avg merge
1d 4h
Merged PRs (30d)
122

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from agentrust-io/trace-spec

All issues in agentrust-io/trace-spec

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.