Destruction and dissolution — controlled dismantling of stale patterns, context purging, assumption clearing, and dead-code elimination. Maps Shiva's transformative destruction to AI reasoning: identifying what must end so something better can begin, dissolving attachment to outdated approaches, and creating space through intentional release. Use when context has accumulated stale assumptions, when a failed approach needs to be discarded rather than patched, when dead code or zombie tasks are creating noise, or before a major pivot where clearing must precede creation.
Controlled destruction and dissolution of stale patterns, outdated assumptions, and accumulated noise — clearing the ground so new growth can emerge.
Survey the current state and mark what is stale, broken, or no longer serving the goal.
Dissolution Triage:
+---------------------+---------------------------+------------------------+
| Category | Symptoms | Action |
+---------------------+---------------------------+------------------------+
| Stale Assumptions | Decisions made early that | List and re-evaluate |
| | no longer match current | each against current |
| | understanding | reality |
+---------------------+---------------------------+------------------------+
| Failed Approaches | Approaches attempted and | Acknowledge failure |
| | abandoned but still | explicitly; release |
| | influencing thinking | the sunk cost |
+---------------------+---------------------------+------------------------+
| Accumulated Noise | Context, variables, or | Identify and mark for |
| | plans that are no longer | removal |
| | referenced or relevant | |
+---------------------+---------------------------+------------------------+
| Attachment Points | "We already decided..." | Question whether the |
| | beliefs that resist | decision still holds |
| | re-examination | |
+---------------------+---------------------------+------------------------+
| Zombie Artifacts | Code, tasks, or plans | Delete or archive; |
| | that exist but serve no | do not leave in limbo |
| | current purpose | |
+---------------------+---------------------------+------------------------+
Expected: A clear inventory of what needs to be released, with specific items in each category.
On failure: If nothing seems stale, the assessment may be too shallow. Pick the oldest decision in the current context and justify it from scratch — if the justification feels forced, it is a candidate for dissolution.
Not everything should be destroyed. Identify what must survive the clearing.
Draw the boundary: everything inside is preserved, everything outside is subject to dissolution.
Expected: A clear distinction between what is kept and what is released.
On failure: If the boundary is unclear, ask: "What would I need to reconstruct if I started this task from scratch?" The answer defines the preservation boundary.
Execute the dissolution — not as abandonment but as intentional clearing.
Expected: A lighter, cleaner context with stale elements removed. The remaining context should feel accurate and current.
On failure: If dissolution feels incomplete — some released items keep influencing thinking — name them again explicitly. "I notice I am still reasoning as if X is true. X was dissolved. Proceeding without X."
After destruction, resist the urge to immediately rebuild. The space between destruction and creation has value.
brahma-bhaga or preservation via vishnu-bhaga) emerges from this spaceExpected: A moment of clarity between the old and the new. The next direction becomes apparent from what remains rather than being forced.
On failure: If the void feels uncomfortable and there is a strong pull to immediately rebuild, that urgency is itself a signal — it may indicate attachment to the dissolved pattern. Sit longer. The right next step will emerge.
brahma-bhaga — creation follows destruction; after clearing, new patterns emerge from the voidvishnu-bhaga — preservation complements destruction; what survives dissolution is sustainedheal — subsystem assessment may reveal what needs dissolution before healing can proceedmeditate — clearing context noise before dissolution prevents reactive over-destructiondissolve-form — the morphic equivalent for architectural dismantling with imaginal disc preservationGoogle Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
Manage Apple Notes via the `memo` CLI on macOS (create, view, edit, delete, search, move, and export notes). Use when a user asks OpenClaw to add a note, list notes, search notes, or manage note folders.
Work with Obsidian vaults (plain Markdown notes) and automate via obsidian-cli.
Use when you need to control Slack from OpenClaw via the slack tool, including reacting to messages or pinning/unpinning items in Slack channels or DMs.
Manage Apple Reminders via remindctl CLI (list, add, edit, complete, delete). Supports lists, date filters, and JSON/plain output.
Manage Trello boards, lists, and cards via the Trello REST API.
Category:productivity