MEMGen

Developers

Introducing the .MEM format

A MEM is a memory as a file: the moments, the lines, the order, the people as roles, and the values that make it play well. One file carries a version for every person in it; that viewer-conditioned rendering is patent pending. Any tool can open it, any reader can verify it, and a model can write from it. Format version 1.0. These 11 chapters walk through it, from why a memory should be a file to the engine API and the agent tools that build on one.

  1. 1What is MEMGen?The site in one page: drop photos, get a MEM, share a version made for each person.2 min
  2. 2Introducing the .MEM formatA memory as a file: one file, a version for every person in it. Patent pending.3 min
  3. 3A memory as a fileWhat a MEM holds in human terms: moments, order, lines, people as roles, arc, music.4 min
  4. 4Inside the containerThe shape of the file: a manifest, media by content hash, an optional timestamp proof.4 min
  5. 5The manifestmem.json field by field: what a reader gets from the package, the assets and the hints.5 min
  6. 6Values travel, methods don'tThe file carries outcomes, never the engine; why that protects both family and format.3 min
  7. 7One file, many viewersViewer-conditioned rendering, the claimed idea: roles, not names; a version for each.5 min
  8. 8ProvenanceThe manifest hash and the OpenTimestamps proof: when it existed, unchanged since.4 min
  9. 9Tiers and profilesPortable or full; bundled or linked. A 3 KB linked file is enough for a model to use.4 min
  10. 10Verify and build oneThe engine API in three calls, plus the SDK seed and MCP server an agent can use today.5 min
  11. 11Status and roadmapWhat exists now, what M12 adds, what Family Intelligence makes from an archive of MEMs.3 min