Ephemeral=true so they stay out of sync and can be
deleted wholesale later.
What are Wisps?
- Issues in the main database with the ephemeral flag set — worked on with
normal
bdcommands. - Local by design: excluded from federation push by default
(
federation.exclude_typesdefaults to[wisp]) and not part of the shared audit trail. - Deleted in bulk by
bd purgeorbd mol wisp gconce closed.
Wisp vs Pour
| Aspect | Molecule (bd mol pour) | Wisp (bd mol wisp) |
|---|---|---|
| Persistence | permanent, part of history | ephemeral, purged when done |
| Sync | synced like any bead | excluded from federation push |
| Use case | feature work, anything worth referencing later | release runs, operational loops, health checks |
phase = "vapor" to recommend wisp instantiation —
pouring a vapor-phase formula warns.
The Wisp Lifecycle
Managing Wisps
Forcing a Phase
bd mol bond accepts phase overrides when combining work:
Best Practices
- Wisps for operational loops — patrols, release runs, diagnostics.
- Molecules for tracked work — anything with audit value gets poured, not wisped.
- Squash before you delete — if a wisp surfaced something durable,
bd mol squashpromotes it; burning is irreversible. - Garbage collect regularly —
bd mol wisp gcorbd purge --force.