programming languages
small languages built to be run, measured, and replayed.
the languages here are not general-purpose. an organism policy vm, a composition protocol, a frontmatter schema, a workflow format: each one is a small contract designed so an agent, a simulator, or a file can be checked without a human reading it.
this category covers the craft of those contracts: 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 for organisms, not authorization — 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
- platonik — a bounded policy language that organisms execute inside a simulation.
- morphogen — typed, replayable workflow organisms with deterministic structure.
- sound.fish — a composition format where the encoding is the identity.
- wordcell — frontmatter and query grammars as small languages over markdown.
AI-drafted at Ben Guo's direct request as category seeds; each lesson page is reviewed against the source repositories before publication.