⇩ Markdown

Term -- Wisp

^ Term -- wisps

An ephemeral workflow in Beads

category -- ephemeral things

Backlinks

Glossary

Term Description Kind

Term -- Wisp An ephemeral workflow in Beads bead

see in context
spaced repetition prompts - blog section 1 - What the heck is Gas Town?

What benchmark does Steve use to demonstrate Gas Town's ability to handle long workflows? ? The Towers of Hanoi — specifically a 20-disc version that produces a million-step Term -- Wisp.

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

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

see in context

What type of Molecules are stored as Term -- Wisp, and why? ? Molecules associated with Patrols because those workflows need to complete transactionally, but don't need to be stored in git.

see in context

What happens to Term -- Wisp at the end of their run? ? They are "burned" (destroyed). Optionally they can be squashed into a single-line summary/digest that's committed to git.

see in context

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

see in context

In the matter metaphor, what phase do Term -- Wisp represent? ? The vapor phase — the lightest, most ephemeral form of Gas Town work.

see in context
spaced repetition prompts - blog section 12 - Patrols

What is a Patrol implemented as? ? An ephemeral (Term -- Wisp) workflow that the agent runs in a loop.

see in context