Dream → Idea Vault Bridge

Full HTML reader

Read the full artifact

Extracted abstract or opening context

--- name: dream-idea-bridge description: Bridge connecting Dream Weaver bloomed dreams to CC-Idea-Vault for research tracking homepage: https://github.com/diomandeee/clawdbot user-invocable: true command-dispatch: bridge-dreams metadata.clawdbot: {"requires_orbit": false, "background_capable": true, "pulse_integration": true} --- > _"When dreams bloom, they become research. When research matures, they become claims."_ This bridge connects the **Dream Weaver** incubation system to the **CC-Idea-Vault** research management system, creating a unified pipeline from fuzzy idea to verified knowledge. | Command | Description | |---------|-------------| | `/bridge-dreams` | Sync all bloomed dreams to Idea Vault | | `/bridge-dreams --dry-run` | Preview what would be synced | | `/bridge-dreams --force` | Re-sync already bridged dreams | | `/bridge-dreams <id>` | Bridge a specific dream | | `/bridge status` | Show bridge statistics | | Dream Field | Idea Field | Transformation | |-------------|------------|----------------| | `spore` | `text` | Direct copy | | `status` | `status` | blooming→inbox, fruiting→workbench | | `keywords` | `tags` | Array copy | | `synthesis` | `notes` | Full synthesis text | | `current_strength` | `confidence` | Direct (0-1) | | `journal` | `history` | Event log |

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.