Visual Intent
This diagram gives the memory architecture a public-facing security shape without exposing implementation-heavy vocabulary first. The reader should see that an access request is tested against identity, purpose, boundary, and scope before context is restored. Refusal is part of the design, not an error path to hide.
Use this visual beside memory and continuity pieces where the prose distinguishes persistent records from permissionless retrieval.