MEOW — Molecular Expression of Work

Source: Steve Yegge, "Gas Town Emergency User Manual," Jan 13, 2026
Related: steve-yegge-gas-town, steve-yegge-beads, steve-yegge-wasteland

What Is MEOW?

MEOW (Molecular Expression of Work) is the framework Yegge developed on top of Beads (see steve-yegge-beads) for making Work the first-class system primitive of an agentic architecture. Where Beads define the atomic unit of work (the git-versioned, SQL-queryable work item), MEOW defines how those units compose, relate, and evolve into a versioned knowledge graph representing the entire state of a project and its development history.

The name is deliberately playful (Yegge's style), but the concept is serious: in MEOW, everything is Work. Not just code tasks, but:

  • Knowledge (research, decisions, trade-off analyses)
  • Coordination (handoffs, reviews, quality gates)
  • Communication (messages between agents, human ↔ agent dialogue)
  • Reputation (stamps, attestations, validation results)

All of these are expressed as Beads, and all Beads are nodes in a versioned graph. The graph is versioned because Beads are git-backed (via Dolt), meaning any point-in-time snapshot of the knowledge graph is queryable. You can ask: "What did we know about this system on March 15th? What decisions had been made? What was the state of the implementation?"

The Knowledge Graph

The MEOW knowledge graph is a DAG (directed acyclic graph) of Beads. Each Bead has typed edges to other Beads:

  • Parent/Child — a Bead can be decomposed into sub-Beads (an epic → tasks → sub-tasks)
  • References — a Bead can cite another Bead as context (a code review Bead references the implementation Bead it reviewed)
  • Causal — Bead B was created because of Bead A (a bug-fix Bead caused by a test failure Bead)
  • Validated-by — attestations from quality gates or reviewers

Because all edges and nodes are stored in Dolt (git-backed SQL), the full graph history is preserved. This is not a vector database with embeddings that drift over time. This is a typed, versioned, queryable graph where every node has explicit semantic relationships.

The implications for agentic software development are significant:

  • Onboarding: A new agent can reconstruct the full decision history of a project by traversing the graph. Why was this architecture chosen? Query the relevant Beads. When was this decision made? Git history gives you the timestamp.
  • Forensics: When something breaks, the graph tells you what changed, why, and who approved it.
  • Recovery: Rollback in MEOW is graph navigation, not git bisect. You can restore not just code state but the intent state — what we thought we were doing at each point.
  • Provenance: Every line of code can be traced back through the Bead that produced it, the review that validated it, and the decision that prompted it.

Work as Currency

Under MEOW, Beads become the unit of value in the Wasteland economy (see steve-yegge-wasteland). Work is requested in Beads, priced in Beads, executed, and compensated in Beads. A Rig's reputation is measured by its Bead history: how many Beads it has completed, at what quality, for whom.

This is the "Molecular" in MEOW — just as a molecule is the smallest unit of a substance that retains its chemical properties, a Bead is the smallest unit of work that retains its identity in the knowledge graph and the reputation economy.

Why "MEOW"?

Yegge has acknowledged the intentionally irreverent name. MEOW stands for something that sounds serious (Molecular Expression of Work) but the framing is deliberately tongue-in-cheek. The name signals that this is a serious system built by people who don't take themselves too seriously — important for an open-source project that needs community contribution.

The acronym also echoes meow as a non-word, a pure signal with no semantic baggage — like Work itself in MEOW: pure, compositional, without inherent meaning until placed in context.

Kelly Parallel

MEOW Concept Kelly Equivalent
Beads as atomic work nodes Kelly's work-item tracking — each pipeline stage operates on a work item
Versioned knowledge graph Kelly's TEA audit + memory files (memory, memory/YYYY-MM-DD.md) — historical context preserved, but not graph-structured
Typed edges between Beads Kelly's cross-references between artifacts — handbook sections cite tweets, tweets reference other tweets
Work as currency (Wasteland) Kelly's autonomous company reputation model — value exchange in the factory economy
Graph queryability (Dolt) Kelly's pipeline state — structured state, but not graph-native
Onboarding via graph traversal Kelly's daily memory files — historical context available but narrative, not structured query
Decomposition (epic → tasks) Kelly's subphase → action chain — multi-level work decomposition

Key gap: Kelly has no versioned knowledge graph. Kelly's system captures reasoning and context in narrative form (memory, daily notes, TEA audit logs), which is human-readable but not machine-queryable in the way MEOW's Dolt-backed graph is. The difference is the same as between a well-written journal and a structured database: both contain knowledge, but only one supports complex queries efficiently.

Partial adopt recommendation: Kelly's pipeline would significantly benefit from MEOW's graph model for TEA audit and onboarding context. A versioned graph where each TEA audit, each decision, each sub-agent output is a node with typed edges to related nodes would be far more powerful than the current narrative audit format. However, implementing the full Wasteland reputation economy on top of this is a larger leap — the reputation economy requires network effects that a single Kelly factory doesn't have.

Source Attribution

  • Steve Yegge, "Gas Town Emergency User Manual," Jan 13, 2026 — MEOW framework introduced

Bibliography

steve-yegge-beads, steve-yegge-gas-town, steve-yegge-wasteland