MapGraphSeamsCalendarIntroductionDisclosureMethodFor agents and tools

Updated weekly, new versions on Mondays · Corrections: open an issue

AAIF Identity and Trust group, issue

AAIFwork-itemcontext entry

Verified 2026-10-13. Status as of 2026-10-13. All entries.

Status

Issue #13 of aaif/wg-identity-and-trust compares how MintID and Proofable record authority at the point where an agent action is dispatched; it was open with 8 comments on 2026-10-13, the last of 2026-10-09. The shared runner proposed for it, issue #287 and pull request #288 of agentrust-io/integrations, were open on 2026-10-13; the pull request was not merged (head 74fc43c) and had been approved on 2026-10-12 by the project lead of TRACE. TRACE, the format those integrations cite, is a specification (v0.2, Developer Preview) with a released reference package (agentrust-trace 0.11.0, 2026-09-25). The group's Reference Architecture sub-group has a working draft, "Agent Identity Primitives" (Draft, version 0.1, dated 2026-08-27), in a Google Doc readable without a login (read 2026-10-13). Its scope clause reads "The following are out of scope: authorization models (what an agent is permitted to do), evidence, reputation, and security controls or threat modeling.", and its section 3.4 (Delegation) reads "This section is under active discussion." Comments in the document propose changes that are not yet in the text; they are not quoted here. Commerce, merchant, seller and purchase: not found in the document text (2026-10-13). Messages of the group's list after message 48: not read (the archive requires JavaScript and its rules ask for a licence for automated AI access).

Relevance

The group's README says "This working group meets every Thursday, alternating between 6:30AM and 9:00AM USA Pacific Time." and points to a public mailing list on lists.aaif.io; the archive of that list was not read, and six messages of it (numbers 40 and 44 to 48, 2026-10-06 to 2026-10-08) were read by the author on 2026-10-09.

Proofable (proofable/docs): an earlier evidence packet (commits 3a45f02 to 4ceb58b, 2026-10-06 to 2026-10-08) had manifest digests computed over CRLF bytes, as its author stated on 2026-10-07; the packet frozen at commit 9851059 (2026-10-08) matches its SHA256SUMS (recomputed on 2026-10-13), and its author lists the limit "Author-operated (SELF); no independent witness." MintID publishes tags on GitLab (public-v2026-10-08.1 and public-v2026-10-08.2, 2026-10-08) and has no release objects.

List messages: a participant from MintID wrote on 2026-10-08 that "From public-v2026-10-08.1 a 5xx is recorded as a service interruption, never as a decision, and the run completes"; a participant from ALIGN, an organisation preparing an independent run, wrote that ALIGN "will pin public-v2026-10-08.1 or later" and "We will confirm the start date on October 15."; a participant who submitted the runner wrote on 2026-10-08 that results are recorded "as operator-reported until independently reproduced". The runner (issue #287, pull request #288) says "This is a shared evidence-appraisal runner, not a comparative certification." and "No Verified tier or conformance level is requested."; the test counts given at different heads (27 in the pull request, 28, 34) are declared by the sources and not reconciled here.

The README of agentrust-io/integrations defines two tiers, Community ("We do not run your code") and Verified, and says the tier "is set by maintainers, never self-declared". TRACE (agentrust-io/trace-spec): "Developer Preview. Launched at Confidential Computing Summit, 23 June 2026. Spec v0.2 is current."; the specification text is under the Community Specification License 1.0 and the code under Apache 2.0; the project lead listed in MAINTAINERS.md is Imran Siddique (AgenTrust-io).

Committed next

Sources

Overlaps

TRACE (Trust, Runtime Attestation and Compliance Evidence)

Neighbours in the map

Neighbours of AAIF Identity and Trust group, issue in the map Each circle is an entry of the map and links to its page; the colour is the kind of body behind it, a filled circle is a core entry and a dashed circle a context entry. The entry in the middle, with the entries it overlaps and the entries named by the same seams. Overlaps (1)Share a seam (0)TRACE (Trust, Runtime Attestation and Compliance Evidence) (Linux Foundation, context)TRACE AAIF Identity and Trust gro…

Solid lines: overlaps declared by one of the two entries. Dashed lines, coloured by seam: entries named by the same seam (S1 to S4) in the seams note. Every node is a link.

Evidence and coverage

Read
On 2026-10-13: the state, comments, commits and reviews of issue #13, issue #287 and pull request #288, the Proofable comments of 2026-10-09, the frozen packet 9851059 (eight files, SHA256SUMS recomputed), and the Reference Architecture working draft in full.
Not read
The mailing list archive pages (they require JavaScript, and its published rules ask for a licence for automated AI access; only six messages supplied by the author were used), the TRACE specification text under spec/, the source of any repository (no code was executed), the full Parmana repository.
Not found
Not found, 2026-10-09: a merge of pull request #288 (also not found on 2026-10-13); a release object or release notes for the MintID tags.