The pointer-index approach is interesting — it reminds me of what I've been doing in m3-memory, though from the other direction. You're starting from identity and pointing at memory; I started

with the memory layer and the identity problem ended up being a scoping question (user_id / agent_id tuples on every memory item).

One thing that might be relevant for SOUL ID: the supersession question u/Distinct-Opposite779 raised in the other comment is a real pain point once you have persistent identity across runtimes. In m3-memory I handle it with bitemporal fields — every memory has valid_from and valid_to, so when a new fact contradicts an old one the old one gets superseded automatically but isn't deleted. You can still query "what did this user prefer on March 1st?" and get the right answer. It's the kind of thing that matters if SOUL ID is signing documents cryptographically — the lineage field probably needs to handle "this fact was true when I signed it even though it isn't now."

If the memory pointer-index in SOUL spec could accept as_of timestamps as a first-class dimension, you'd get temporal consistency across runtimes for free. Happy to compare notes — repo is https://github.com/skynetcmd/m3-memory if you want to look at how I wired the bitemporal side.