⇩ Markdown

Term -- Bead

^ Term -- Bead

A bead in Beads.

There are different types

Pinned Beads:

Backlinks

A type of Bead

^ A type of Term -- Bead

see in context
Glossary

Term Description Kind

Agent Bead A worker's persistent identity in the Term -- Bead data plane bead

see in context
Term -- Epic

A Term -- Bead with children

see in context
Term -- Molecule

Gas Town workflows. Persistent work that is stored as Term -- Beads.

see in context
Term -- Protomolecule

A set of Term -- Beads that act as a template that helps you create Molecules

see in context
spaced repetition prompts - blog section 11 - Wisps - Ephemeral Orchestration Beads

What type of Term -- Bead is not stored in git, and why? ? Wisps are not stored because they describe ephemeral Molecules of work. Storing them would just be orchestration noise.

see in context

How do Wisps behave while they exist in the database? ? They get hash IDs and act like regular Term -- Bead, but are not written to the JSONL file and thus not persisted to Git.

see in context
spaced repetition prompts - blog section 6 - Gastown Universal Propulsion Principle

Which Term -- Bead type is used for GUPP? ? Hook

see in context

What makes a Pinned Bead different from a regular Term -- Bead? ? Pinned Beads float like yellow-sticky notes — they never get closed and don't show up in bd ready.

see in context
spaced repetition prompts - blog section 9 - Molecular Expression of Work (MEOW)

What do you call a Term -- Bead with children? ? An Epic.

see in context

What are the templates used to create workflows in the MEOW stack? ? Protomolecules — made of actual Term -- Beads with instructions and dependencies set up in advance.

see in context

Why do Molecules survive agent crashes, compactions, and restarts? ? Because a molecule is a chain of Term -- Beads which is stored in Git. A new session just finds its place in the molecule and picks up where the last one left off.

see in context