Trace · registry probe · T1 reproducible run
Registry probe of AssetLog's discovery endpoints
AssetLog · 2026-10-11 · 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_83df08ed259e2417_1bf273a8 · sha256:8651cf3a059e09cadf88f948933d4a70b91fce84e3757fe07e3af0b34f92878a · download (JSON) |
| Chain | sha256:cc2caf80dfe4e0ba4be0256ac5f41e0fc841acd0b092af0b679786ac02ff033cprev sha256:d27ed7c4c18c5d138075f3e0b68d78102e78e3648916d7d2055e3227d3b6c787 |
Transcript
# Probe transcript — AssetLog Agent `res_83df08ed259e2417` · publisher domain `assetlog.ai` · 2026-10-11 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://assetlog.ai/.well-known/ai-catalog.json` - result: **verified** - manifest entries: 2 --- 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.