PARSE · VALIDATE · CORRELATE
Message type failures: inspect the schema boundary
Edit a real request document. Follow validation, decoded payloads, a local handler and response-id matching.
Editable request
Response received by the client
Local receiver effects
Your experiment
The opening role is invalid. Compare it with user and agent messages. Replace a data object with an array or text with a number, and inspect the exact rejected part before any handler receipt exists.
Use Play for a full minute at 1×, Pause to inspect a gate, or Next gate for manual review. The timeline and speed control operate on this exact validation trace. Editing an input resets the inspection without autoplay.
Validated part inspector
Version-pinned teaching subset: JSON-RPC 2.0 and the A2A v0.3.0 message/part shape. This is not a complete A2A SDK or a conformance validator. Only message/send is dispatched; batches, streaming, tasks, authentication and extensions are not implemented. The notification example teaches the generic JSON-RPC no-response rule, not a supported A2A call shape. Unknown fields are not a full-schema validation. File bytes use canonical padded Base64; URI references use a strict reserved example host and are never fetched. MIME labels are not content-sniffed. The handler creates only an in-memory teaching receipt. Sixty seconds is inspection time, not measured latency. JSON-RPC specification · Pinned A2A message reference · Official AICassindra articles.
Distinguish roles from content kinds
Load the wrong-role fixture: system is not an accepted message role in this subset. Restore the valid example and replace a data part object with an array. The data part fails even though arrays are valid JSON values. Restore the object, then set parts to an empty array to exercise the nonempty-content rule. Text, object data and file representations have different validators; a role field does not select their encoding. These checks cover the local versioned teaching subset and do not establish universal protocol compatibility.
Edit an actual request document
Fixture loads a complete JSON example into the request editor. Selecting another fixture replaces your edits. The editor then becomes the source of truth: parsing, envelope validation, method dispatch and part validation all examine its current text. Keep the JSON-RPC request id separate from the nested messageId. Response correlation checks the former and preserves its type; neither identifier is a security credential or an implemented idempotency key in this lesson.
Apply a local validation policy
Per-part byte limit counts UTF-8 text, serialized JSON-object data, or decoded Base64 file bytes. It is not a limit on total request size or MIME content validation. Allow URI references permits only the fixture reserved HTTPS host and never fetches the linked content, whose size is consequently unknown. Mismatch response id corrupts correlation after handling; Inject server fault fails the local handler before a receipt is created. These toggles isolate different failure boundaries rather than simulating remote infrastructure.
Follow the earliest failed gate
Play presents the validation trace over a minute; Pause, Next gate, Restart, Speed and the timeline provide controlled inspection. An input edit resets the inspection. If a gate fails, later dispatch or handler stages are not run, but an error response can still be inspected. A successful local handler with a mismatched response id is not accepted by the client. Removing the top-level id illustrates a generic JSON-RPC notification without a response; it must not be treated as confirmed success or a fully supported A2A notification contract.