Jeffrey M. Barber

Tombstone

Adama core: the language and the living-document runtime

Nov 2024 โ€“ Apr 2026 ยท age 42โ€“44

What it was

The compiler and runtime at the heart of Adama. A hand-written parser read a language of records, tables, privacy modifiers, reactive formulas, labelled state machines, channels that wait for people and, from 2026, AI agents. A type checker enforced who may see what, and about thirty code generators emitted Java compiled inside the running process. In the runtime every value wrote a forward and a reverse delta on each change, a goodwill budget of ten million loop checks bounded each transaction, the random source was persisted so history replayed exactly, and each viewer received only the changes they were allowed to see. Hundreds of Adama programs served as gold tests, checked byte for byte against saved transcripts.

Wins, for the age

What it taught

Genealogy

Ancestors: Career Facebook: streaming updates to huge audiences. Evolution eXPeriment: one shared world held by a server. Kitchen: a schema compiler and a scripting VM. Lamancha I: undo as JSON deltas. Lamancha II: the language and runtime themselves. OldSkool: reactive formulas in miniature. osgOpenGEL: an error that remembers where it has been. Play Workspace: a JSON document per game over a log. Vector Register: generating Java wholesale. World Bootstrap: undo and redo as diffed data. Descendants: none on record. Its ideas went out through the farewell, itemised for anyone to take. Part of: Adama.

Epitaph

A document that could not compile if it leaked, could not loop forever, could not forget its dice, and could undo anything it did, including what its AI agents said.