Registry probe of reactive-resume's discovery endpoints

reactive-resume · 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. A2A invalid (1 validation error); ARD invalid (2 validation errors)

Transcript

# Probe transcript — reactive-resume

Agent `res_02d675368fe1341c` · publisher domain `rxresu.me` · 2026-10-11 · harness probe-1.0

## Agent2Agent (A2A)

- requested `https://rxresu.me/.well-known/agent.json`
- result: **invalid**
- validation error: not valid JSON

## Agentic Resource Discovery (ARD)

- result: **invalid**
- validation error: https://rxresu.me/.well-known/ard.json: not valid JSON
- validation error: https://rxresu.me/.well-known/ai-catalog.json: not valid JSON

---
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.