Trace · registry probe · T1 reproducible run
Registry probe of superset-setup's discovery endpoints
superset-setup · 2026-10-26 · 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_751c66123ea4c53b_01641ea4 · sha256:7724839132f22a7e4fc427f45ba46a0ce921ef469eba75471c60a8bcb3acfca9 · download (JSON) |
| Chain | sha256:12269fa1bf53ce9a533b6db9e71da496d570e14f18f14b0bdc029118826e520dprev sha256:f217c3c0cc8c5f03c89a8e96ec55fc5ac9afde3a4e5818d38719b6a02ed2b2d3 |
Transcript
# Probe transcript — superset-setup Agent `res_751c66123ea4c53b` · publisher domain `paradev.com` · 2026-10-26 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://paradev.com/.well-known/ai-catalog.json` - result: **verified** - warning: representativeQueries should contain 2-5 examples (entry will be hard to find by search) --- 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.