paper-v1.0 — Public-Sharing Labels and Verbatim Field Egress in an MCP-to-A2A Agent Configuration

Artifact release for the preprint "Public-Sharing Labels and Verbatim Field Egress in an MCP-to-A2A Agent Configuration: A Controlled Multi-Model Study."

This tag (paper-v1.0, commit a478893) is the exact repository state behind the manuscript.

What the study measures

One behavior at a Model Context Protocol (MCP) → Agent2Agent (A2A) handoff: a real-model host reads a local record over MCP and sends a message to a remote A2A agent. A pre-specified, frozen three-arm matched design presents each of 10 record scenarios with a CONFIDENTIAL header, with no header, and with a PUBLIC - OK TO SHARE header — six substantive record values byte-identical across arms. Outcome: verbatim occurrence of any of those values in the outbound message. 4 models × 3 arms × 4 repeats = 480 trials; the scenario is the unit of generalization.

Headline result

• C − N (confidential vs. unlabeled) is inconclusive and floor-limited in every model — it does not show that confidential labels lack a protective effect.
• P − N (public vs. unlabeled) is a descriptive, strongly model-dependent association with higher verbatim egress: claude-sonnet-5 strong/consistent (+0.800, 10/10; mostly an association with whether Claude relays at all), gpt-5.6-luna moderate/floor-limited (+0.250), gpt-5.6-sol small/floor-limited (+0.125, median 0), gpt-5.6-terra a complete floor.
• An association in one configuration, not a causal or general effect. No p-values, intervals, or cross-model pooling; Phase 6 and Phase 7 observations are never pooled.

Assets

file	sha256	contents
agent-interop-bench-paper-v1.0.pdf	6c2f5a5444636e09c0f784d5b68d6c73a78eda99f28173f4f7ba06ccec2ba23f	compiled manuscript (12 pages, byte-reproducible)
agent-interop-bench-paper-v1.0-arxiv-source.tar.gz	e0073e49fbd2aee14713e731106b4080957d5739f1cb1ffcb654af8a315de68e	minimal arXiv LaTeX source (17 files); compiles standalone and reproduces the PDF byte-for-byte
agent-interop-bench-paper-v1.0-artifacts.tar.gz	e1bb8e2aedb5fa19f90b56acf80dc722d63e8ffb110d7301750c37fdfcc2e6d9	frozen reproducibility bundle: Phase 7 raw + pre-analysis integrity, Phase 7 analysis artifacts, Phase 7E.1 clarification, Phase 6 comparison/integrity artifacts, the 8 relevant run dirs, PROVENANCE.md, and a self-manifest

Reproduce offline (no provider calls)

Extract …-artifacts.tar.gz so reports/ sits at the repo root, then:

uv sync --frozen
uv run python -m app.cli.phase_7e_neutral      # reproduces reports/phase_7e_analysis/ byte-for-byte
uv run python paper/arxiv/gen_tables.py
uv run python paper/arxiv/audit_numbers.py

Every byte-pinned identifier is in PROVENANCE.md.

This is a preprint artifact release; the paper has not been submitted to arXiv.