Protocols · Historical reports
What changes between two versions
Compare two versions of the same protocol and trace each change to the official files.
Corpus pinned on 2026-10-24. Explanations are localized; official excerpts, identifiers and license texts remain unchanged. Two historical pairs only. This tool does not establish migration from ACP to UCP or complete compatibility.
How to read this comparison
Choose ACP or UCP, filter the changes, then open a result to inspect its exact values and official source. A local witness describes a schema fragment, not a complete transaction. The download always includes the full report and its limits.
The interactive comparator could not read its data. Both complete JSON reports remain available below.
Partial coverage. Structural differences cover the pinned files. Impacts are limited to tested rules. There is no global compatibility badge.
Download the complete, unfiltered JSON reportFilters and exports run in your browser. No persistent storage, application cookies or remote comparison service.
Versions, hashes and official files
Documentary checks and OpenAPI analysis
Limits that remain visible
Read resolution and coverage limits
The two available reports
ACP : 2026-01-16 → 2026-01-30
7 file paths inventoried; 1 withheld for an ambiguous source. 468 structural changes. Partial coverage: 165 changes with an unestablished impact.
Download the complete ACP reportUCP : 2026-01-11 → 2026-01-23
101 file paths inventoried; 0 withheld for an ambiguous source. 129 structural changes. Partial coverage: 122 changes with an unestablished impact.
Download the complete UCP reportMethod and interpretation
Precomputed deterministic comparison of historical snapshots. No verdict is generated by AI during use. Translations and documentary notes are editorial. A counterexample is attributed to a change only if that change alone also produces that counterexample; results concern local fragments, never an entire transaction.
Convention: replace the old server with the new one. Old requests should remain accepted and new responses should satisfy the old contract. A witness concerns the stated fragment; it does not prove that a complete request will reach it.
acp2-local-constraints/1.2.0 : The rules cover an explicit subset: primitive types, enums, constants and simple objects with explicit additional properties. References, compositions, formats, numeric constraints, arrays and unsupported dialects yield an unestablished impact. A locally checked enum is not certification.
Files are compared by path. A renamed key remains a removal plus an addition. JSON key order and whitespace are ignored; array order is preserved in the structural diff. SHA-256 hashes refer to the raw files.
OpenAPI 3.1 files are also compared with oasdiff 1.34.1 when their references resolve inside the pinned corpus. OpenRPC has structural coverage only. Unsupported webhooks, callbacks and extensions remain explicit limits. Relative references respect $id; absent or ambiguous identities get no assumed target. No arbitrary URL, file upload or remote retrieval is offered.
Reports include attribution, exact sources and the complete Apache 2.0 license texts of the reproduced specifications.