PARSE · VALIDATE · CORRELATE
File parts: bytes versus URI references
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 request incorrectly includes both bytes and uri. Repair it using the Base64 fixture, then the URI fixture. Lower the byte limit below six and inspect the decoded-size failure. URI contents are never fetched.
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.
Choose one file representation
The opening document supplies both bytes and uri, which this validator rejects. Load the Base64 fixture: SGVsbG8h decodes to six bytes representing Hello!. Set the per-part byte limit to five and then six to inspect the exact size boundary. Load the URI fixture and disable URI references to exercise the separate local allowlist policy. A passing reference does not prove the file exists or is safe, because this offline lab never retrieves it.
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.