Trace · registry probe · T1 reproducible run
Registry probe of Alpic Plugin's discovery endpoints
Alpic Plugin · 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_888ec7892efd0890_6d610780 · sha256:775188db2c2d21cf26e038f0e5daa6f7e43c3c63a4812382a0101385c47084b7 · download (JSON) |
| Chain | sha256:66209d6d590e2d039b96063695bf3bdad459d574a61743b61c6567ba719169adprev sha256:9c5ed5e5d6ca90ec9fb8f3412f268596442b1279dd4aa1d0c24e8dfe0b36894a |
Transcript
# Probe transcript — Alpic Plugin Agent `res_888ec7892efd0890` · publisher domain `alpic.ai` · 2026-10-11 · harness probe-1.0 ## Agentic Resource Discovery (ARD) - requested `https://alpic.ai/.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.