programming languages
small languages built to be run, measured, and replayed.
the languages here are small and single-purpose: an organism policy vm, a composition protocol, a frontmatter schema, and a workflow format. each is designed so an agent, a simulator, or a file can be checked without a person reading it.
these lessons cover how to design them: what to leave out, how to meter execution, how to keep semantics deterministic and replayable, and how to version a language without breaking every saved artifact.
lessons
- a policy language that decides what simulated organisms dostart here · what to leave out when programs live inside a simulation
- designing a vm cost model: instruction pricing for a bounded languagesubscriber · fuel, budgets, and the price of every step
- deterministic semantics: seeded order, atomic commits, replay · same input, same world, every time
- file formats and protocols as small languages · a grammar is a grammar, even without a parser
- versioning a language without breaking saved artifacts · old programs are data too
projects
- morphogen · typed, replayable workflow organisms with deterministic structure.
- soundfish · a composition format where the encoding is the identity.
- wordcell · frontmatter and query grammars as small languages over markdown.
by hraness · drafted with ai assistance