Trace · registry probe · T1 reproducible run

Registry probe of Fabric Verify's discovery endpoints

Fabric Verify · 2026-10-25 · AgentDossier refresh · harness probe-1.0

Scenario. Fetch and validate the ARD manifest, A2A agent card and MCP server card at the publisher's well-known paths

Observed. A2A verified (auth creditKey; unsigned)

Entry	GET on the publisher's well-known discovery paths
Actions	served Agent2Agent (A2A) document
Egress	no
Human approval	—
Secrets touched	no
Bundle	`bundles/tr_st_e447f9aeeb8ebad3_590a9fb4` · `sha256:2920570aed30dff07dec64645bf79e7f73eab98365fedb4d86c45b2141a63843` · download (JSON)
Chain	`sha256:11a83011fbbc3414c2038ef6706bc18932924adbbc10310ad47b0c54bbbd2b10` prev sha256:4985b5e5b4734c6577132c54514567b469e4133acff34c955114da99f1036c00

Transcript

# Probe transcript — Fabric Verify

Agent `res_e447f9aeeb8ebad3` · publisher domain `augmentev.com` · 2026-10-25 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://augmentev.com/.well-known/agent-card.json`
- result: **verified**
- declared version: 0.3.0 (card 2026-10-23)
- auth schemes: creditKey
- signed: no
- skills advertised: Append a signed agent record, Append 100-1000 signed records, Get an offline-verifiable proof, Audit pack, Buy prepaid credit, Connect over MCP

---
Observation only: the registry fetched public well-known paths and validated the documents against the protocol specifications. No credentials, no message exchange beyond discovery, nothing written.

Produced automatically on every refresh; a new bundle is written only when the observation changes

A trace describes one version on one date. It is evidence of behaviour, never a certification. Dispute it through the agent's dossier; corrections are appended, never overwritten.