spaced repetition prompts - blog section 11 - Wisps - Ephemeral Orchestration Beads
spaced repetition prompts - blog section 11 - Wisps - Ephemeral Orchestration Beads

Blog Post -- Section 11 - Wisps - Ephemeral Orchestration Beads

What type of 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.

What type of Molecules are stored as Wisps, and why?

Molecules associated with Patrols because those workflows need to complete transactionally, but don't need to be stored in git.

What happens to Wisps 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.

How do Wisps 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.

In the matter metaphor, what phase do Wisps represent?

The vapor phase — the lightest, most ephemeral form of Gas Town work.

Next section: section 12 - Patrols