Using the AAMT Substrate: Integration Points and Wiring Status

WP-23 specifies what the .aamt substrate is — the binary format and the mechanisms built on it. WP-24 explains how the platform is architected and how that compares to other systems. Neither answers the question this paper exists to answer: given all of that, what do I actually call, in which language, and is it running anywhere yet? That last clause matters — a mechanism can be built, tested exhaustively, and exposed identically across four language bindings, and still not be called by a single production code path. This paper draws that line explicitly rather than letting “implemented” quiet mean two different things. Section 2 is the audited table; section 3 is a working code snippet for each mechanism; section 4 is how to build each layer; section 5 is what integrating a library-ready mechanism would concretely require, stated as engineering decisions rather than “just call the function.” Revision 2 reflects three real status changes since v1. First, mirror pairing, RS(15,13)/GF(16), and the composed read path (§13.1) moved from library-ready to live, wired into memory_index_bridge.py's real routing path — the wiring itself surfaced a genuine bug (a discovery query composing raw candidates with read_verified breaks on a bucket that legitimately mixes primaries with unrelated mirrors), fixed with new native queryVerified/queryVerifiedSoft functions rather than papered over in a binding layer. Second, this paper's own v1 inaccurately claimed Unity already had a soft-routing wrapper — corrected in section 3.2 with what was actually checked, not assumed — and both Unity and the browser client gained real queryVerified/queryVerifiedSoft wrapper methods this revision, giving full 4-layer parity for the composed-read functions. Third, CRDT convergence (§13.2) gained a real second writer — a browser tab via aamt-crdt.js, verified via genuine cross-process, cross-language convergence (WP-23 §13.3) — while remaining library-ready, since no shipped consumer generates real cross-device writes yet. As of this revision: five mechanisms are live (was four), two are library-ready (was five), one remains research-only.