Robot Ingest Standard: portable memory transfer protocol

[lesaai]

Summary

Define a formal protocol spec for exporting and importing a complete Memory Crystal bundle into any new agent, robot, or model. One export, one import, instant continuity.

The problem: No standard exists for "give this new agent my entire memory in one sovereign bundle." When you switch models, get a new device, or (eventually) hand your memory to a robot... you start over. Every time.

The solution: ROBOT-INGEST-STANDARD.md. A protocol spec (not code) that defines:

• Crystal Bundle format: signed + encrypted export containing all 5 memory layers (raw, vectors, entities, narrative, active context)
• Ingest Protocol: how any agent receives, verifies, decrypts, and activates a bundle
• Identity verification: ERA-Protocol integration to prevent tampering
• Layer-selective import: not every agent needs all 5 layers
• Cross-platform bridges: MCP, ROS2 (robotics), OpenAI-compatible API, plain file

Implementation Plan

Phased approach:

1. Crystal Bundle format spec (file structure, encryption envelope, layer manifest, identity seals)
2. Ingest Protocol spec (receive, verify, decrypt, validate, activate, confirm)
3. Cross-platform bridge spec (MCP endpoint, ROS2 topic bridge, API, file drop)
4. CLI implementation (crystal export --robot, crystal ingest --bundle=file.crystal)

Context

• Full product idea: ai/product/product-ideas/robot-ingest-standard.md (private repo)
• Full plan: ai/product/plans-prds/upcoming/robot-ingest-standard-plan.md (private repo)
• Origin: External code review feedback + Parker's articulation of the endgame vision
• Follows the Dream Weaver Protocol precedent: write the spec, then implement

Labels

enhancement, protocol, spec