Trace · registry probe · T1 reproducible run
Registry probe of Infisical content, in one document's discovery endpoints
Infisical content, in one document · 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_ca4c264fef83a868_c230e099 · sha256:71ddcdccdee1af7d7485ff36d348d8d18500655bb816657f9997b628dd5a5f8b · download (JSON) |
| Chain | sha256:4aa250c99288c30f46e74e9593fa5409bdb56b444523305e5e93b8fcb3b135ebprev sha256:44a7b5249aeb3b95b78c7f797878714879e67c0ea0026d2bf03b3323ae2f088e |
Transcript
# Probe transcript — Infisical content, in one document Agent `res_ca4c264fef83a868` · 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.