Crosswalk the W3C memory interop scope onto the evidence profile

[Silentpartnercoding]

Crosswalk only. No new fixtures, no schema change, nothing sent anywhere.

The W3C AI Agent Memory Interoperability Community Group is chartered to specify portable agent memory. Its published scope covers cell shape, identity binding, encryption envelopes, audit anchors, sharing contracts, cryptographic erasure, and crosswalks to regulatory and protocol ecosystems.

Two distinctions this directory already carries sit inside "portable memory" and are named by none of those areas:

Derivation	Three validly signed cells derived from one observation are three sources to any consumer that does not carry derived_from. Nothing is forged; the count is wrong.
Search coverage	A query that reached 1 of 26 partitions and found nothing transports as "not found" without search.coverage.

W3C-MEMORY-CROSSWALK.md maps each scope area to the field that carries it and to the failure that becomes unobservable when the field is absent, with an existing fixture on every row.

On the left column

The group has published a scope, not a specification — there is no field vocabulary to map onto yet. So the left column quotes the group's own scope page rather than field names, and says so. A crosswalk whose left column was imagined would assert a correspondence it never checked, which is the failure these fixtures exist to catch. The document states what should replace it once field names exist.

Read from https://www.w3.org/groups/cg/ai-agent-memory-interop/ on 18 Aug 2026.

Checks

• python3 interop/memory-evidence-profile-v0.1/validate.py → PASS: 4 examples; 8 adversarial cases rejected
• Every fixture cited in the crosswalk was opened and confirmed to say what the row claims
• Minority Prophet named only as where the cases were found, not as a dependency

Draft: nothing here has been sent to the group, and doing so would be a separate decision.

🤖 Generated with Claude Code