Trace · registry probe · T1 reproducible run
Registry probe of Infisical vs. Microsoft AD CS's discovery endpoints
Infisical vs. Microsoft AD CS · 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. 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_2372a6d751dd3b93_5c477a11 · sha256:b63bfb739b998a9cb4ebf770a1146cbe4e7c0e5298ea0d614545030d5e462ce6 · download (JSON) |
| Chain | sha256:3451f15b97d85023be32a9bf256fdd177f4b6f22829a6bb2f4b8886b6aa578b2prev sha256:d53c9d07a7e5f000b9273c035aaf82c8824d38f1af5808e565c293596e4dbf6b |
Transcript
# Probe transcript — Infisical vs. Microsoft AD CS Agent `res_2372a6d751dd3b93` · publisher domain `infisical.com` · 2026-10-25 · 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.