Trace · registry probe · T1 reproducible run
Registry probe of Infisical vs. Google Cloud Certificate Manager's discovery endpoints
Infisical vs. Google Cloud Certificate Manager · 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_fc29f888e24282ed_633a6899 · sha256:c2419aa19dd5d4fe58c5688b48fc862dcdfd1a02e8ccdd6ad6a5ec81e7767f7c · download (JSON) |
| Chain | sha256:e56018964565adb36fe9db76a82a957bcaa24f765d87663d312695265297ed39prev sha256:3451f15b97d85023be32a9bf256fdd177f4b6f22829a6bb2f4b8886b6aa578b2 |
Transcript
# Probe transcript — Infisical vs. Google Cloud Certificate Manager Agent `res_fc29f888e24282ed` · 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.