Today
The format is at version 1.0. The container, content addressing, the embedded, linked and hybrid locator model, SHA-256 provenance and verification, the portable and full tier boundary, role redaction, the declared-emotion redaction split, the retrieval hint, and unknown-field tolerance are all solid and exercised by real example files. The engine’s packer, reader and verifier are complete. The SDK seed and MCP server in chapter 9 exist as a worked example.
In this app, every MEM is built, scored and given its per-person versions server-side by the engine, and the package types are the ones in these chapters. There is no export or import button yet. What is still heuristic: description is the owner’s line or caption; segments are grouped by day from takenAt; narrativeSummary and roleGraph are derived deterministically. All are additive outputs, so the container shape does not change as they improve. There is no public spec URL, no conformance suite and no reader in a second language yet.
Coming: M12, the format outward
Export any MEM from this app as a .mem with its own OpenTimestamps stamp: the lockbox hand-off. Import a .mem into your archive, so a memory someone handed you by file becomes part of your own. Publish the format doc and a reference player that opens a portable file and plays it. This is the step another company can adopt, and these chapters are published ahead of it so you can build against the format now.
What an archive of MEMs becomes
Family Intelligence runs over the whole archive, not one drop. A person keeps their identity across every drop; a named face is named everywhere. Every reaction, every added photo and every name is a signal that improves the next suggestion. The more you add, the more it makes. An imported .mem joins that archive and feeds the same loop.
On-device, later
Family Intelligence is model-agnostic by design so it can move onto hardware you own. When it does, a file’s contents need never leave the device, and lockbox:// locators are already in the spec for that day.
How to follow
This wiki tracks the spec. When a field is added it will appear in chapter 4 and the version note here. The additive rule holds: a reader written against 1.0 today keeps working.