CURATOR — three oxblood ledger books labelled DAYS, WEEKS and QUARTERS, with gold page edges on a black background

CURATOR

Meta Global AI Developer Hackathon
Soundtrack: Chapter by Chapter (Suno, 2:55) by GRooVeMaKeRs

A life, kept chapter by chapter.

Other systems overwrite the past, call the edit done, but a record you rewrite can't say what was once. Change a job, they change the field, the old you is gone, chapter by chapter. The Curator, a Life Content Manager, does the opposite: keeping every detail, nothing lost, nothing overwritten, chapter by chapter. When you write, The Curator finds the subjects in what you wrote and creates a chapter for each subject, automatically — every chapter, every arc, with what, when, and why it changed. So you can ask about a life at any point in time, not just its latest version.

Built Oct 26–Nov 4, 2026 in the Meta Global AI Developer Hackathon.
Worker: Muse Spark 1.3 via Meta Model API  ·  Picture: Muse Image  ·  295 tests pass, 0 fail  ·  13-entry K-record  ·  49-sentence demo story  ·  8 of 11 chapters filed
Watch Muse Spark 1.3 answer through the wrapper →  ·  Full technical report →

Start here: the record

Curator keeps every detail, nothing lost, nothing overwritten, chapter by chapter. When something changes, the old version stays in the record — it is not overwritten. That is the whole idea.

Full record: 13 entries — 12 facts, 1 question. Each entry is labelled, so you can tell a fact from a question. A chapter is only filed when enough separate sentences back it up; until then, it stays grey and open.

Open the full 13-entry record Watch Muse Spark 1.3 in the terminal See the engine code on GitHub

The story below is made up for this demo — Ada Okafor is not a real person — so you can use it without an API key. The record above is that made-up story, written out as a list of facts. The code that writes records like this for real, using Meta's models, is on GitHub.

Step 1 — Seed the story

Edit this story if you like — remove a sentence and its topic loses support. Then pull it apart.

Step 2 — Chapters pulled from the story

One tangled life, eleven threads. Support is counted by the engine: one independent supporting sentence moves a chapter one shade darker, on a 0–9 greyscale. Shades 8–9 are the black band — a chapter gets filed. Below that, it stays grey. This fuller story files the fact chapters, and leaves the open questions grey until the record answers them.

Press “Pull it apart” to see the chapters.

Step 3 — Ask about a life, at a point in time

Now chat. Ask what Ada’s life looked like on Monday, or every job she has ever had and why each one changed — the record answers from the chapters, not just the latest version.

Life chapters

A chapter is filed here only when it reaches the black band. Grey chapters and open questions do not get filed as certain — they stay open, listed below, until the record answers them.

No chapters filed yet.
Pull the story apart, then file the certain chapters.

Ready prompt — update something from the record

This prompt is ready to go, sitting at the bottom. Send it and watch what happens to the grey Wednesday chapter: a new entry is appended, the old uncertainty stays underneath it, and nothing gets edited.

“Update: Priya confirms the Wednesday invoice was covered by the old rule on Thursday, before the new sign-off rule took effect.”

Built during the hackathon: the Curator code. The knowledge-time idea behind it was published on Zenodo on October 4, 2026.

See the evidence underneath this demo: the full record — 13 entries (12 facts, 1 question), generated by the Curator engine.