Trace · registry probe · T1 reproducible run
Registry probe of editor's discovery endpoints
editor · 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_ded48ed46b9a45e7_a51bbe0f · sha256:b4499308a48fade14320b2f9cd1bf959f12f4d05c732fcd66baf0d2e40d04183 · download (JSON) |
| Chain | sha256:da3329f39818208bde8b64eda51269aa51a2c84e550c3fb2d0b00521b5b5e2afprev sha256:ece9e7a116e45eee20d3fcf1b39467df77ce48adee555de1faf6d4ad99d29737 |
Transcript
# Probe transcript — editor Agent `res_ded48ed46b9a45e7` · publisher domain `editor.pascal.app` · 2026-10-25 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://editor.pascal.app/.well-known/ard.json` - result: **verified** - manifest entries: 5 --- 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.