Trace · registry probe · T1 reproducible run
Registry probe of Secrets Management's discovery endpoints
Secrets Management · 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_a962287a0917a0f6_abcb4824 · sha256:a8663a44d9d77b6c0de97e66bb126059dab0fd2c7af952acd4973a1a20b2da76 · download (JSON) |
| Chain | sha256:304bbf26d91c8e66ec11fda7fc2bbb405d30e611c8a3de513834341ce3607617prev sha256:79f1d3400b28a40b3a8a0d03b9402cc1051f52df580e0e8360bc73e8d74140ee |
Transcript
# Probe transcript — Secrets Management Agent `res_a962287a0917a0f6` · publisher domain `infisical.com` · 2026-10-11 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://infisical.com/.well-known/ard.json` - result: **verified** --- 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.