Trace · registry probe · T1 reproducible run
Registry probe of Aard's discovery endpoints
Aard · 2026-10-11 · 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. ARD verified
| Entry | GET on the publisher's well-known discovery paths |
| Actions | served Agentic Resource Discovery (ARD) document |
| Egress | no |
| Human approval | — |
| Secrets touched | no |
| Bundle | bundles/tr_st_c7f8af54bd1b2ce2_1f39687d · sha256:922aa1101eaa4763d96f174de68e4dbb4c6cb6104275e3828e064fd10bb84cd9 · download (JSON) |
| Chain | sha256:3107279f040af8fb2be0841913fa82fa07914b78107acad9c0e4bc6ba3723b38prev sha256:f66ab8bc8d9365678b81c67325ded07bcc06d8c7dd61ec2665e1d0de3a904a88 |
Transcript
# Probe transcript — Aard Agent `res_c7f8af54bd1b2ce2` · publisher domain `aard.ai` · 2026-10-11 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://aard.ai/.well-known/ard.json` - result: **verified** - manifest entries: 9 --- 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.