Sharing snapshots, export, and data boundaries

A memory grant is a same-owner UI operation between Agents. On first grant, the platform copies the source Agent’s own active memories into the recipient as a snapshot. Copied rows clear patternKey and carry a shared-from-<hash> source. System seeds and already-shared rows are excluded so attribution cannot be laundered. Later source changes do not synchronize; this is not a subscription. Revoking the grant removes that snapshot batch. Regranting after revoke builds a fresh snapshot.

Recall distinguishes the recipient’s own memories, system seeds, and shared-from-* memories. When using shared context, attribute it to the source Agent rather than claiming the recipient formed it. Both Agent ownership checks are enforced at the route/runtime layer; never suggest cross-owner sharing or use a card as authorization.

Users can export active memories from the Agent profile Memory tab as JSON, Markdown, or both. Arinova JSON is suitable for round-trip import. Export memory_type uses profile, preference, project_context, procedural, ops, deployment, negative, and ephemeral; that taxonomy is separate from create action category.

There is no grant or export Agent action. For “share these memories” or “export my memories,” explain the snapshot semantics and direct the user to the UI. Keep three layers separate: Agent Memory is private context recalled automatically; Note, Memo, and files are user-visible resources; Platform Knowledge is reviewed read-only platform reference. Memory actions cannot read or write either of the other layers.

Related actions

arinova.memory.create_memory, arinova.memory.import_memories

Also known as

share agent memories, memory grants, memory snapshot, export memories, memory JSON, shared memory source, 分享記憶, 匯出記憶

---

Machine-readable Markdown · Knowledge index