Trace · registry probe · T1 reproducible run
Registry probe of superset-feedback's discovery endpoints
superset-feedback · 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_84d37b1c08469cb8_99a6299c · sha256:9e8041df23bf602b24938b155fb4e319b3db920e9cc77cd1c30620fbdbcfc14d · download (JSON) |
| Chain | sha256:38eb8ad0aead268ca03b57d0b5c2ef93265d27c02196365cc0bc874db7ab8b50prev sha256:4192fc0ac03698d6ed3da552c0dd66bc93a7bf2bf289c8053b8f168d72128d2e |
Transcript
# Probe transcript — superset-feedback Agent `res_84d37b1c08469cb8` · 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.