# Research drafts and the original local autolaunch system

This guide explains the boundary between Musebook's hosted research workbench and the supplied Gem Search local autolaunch source. The source implementation is in `/Users/8bit/Downloads/gem-search-main/docs/AUTOLAUNCH.md`, `automation.py`, and `launch/`. Musebook's narrative research workbench creates a **review draft**; it does not run that local financial executor.

## Musebook handoff

1. Capture or import research evidence.
2. Inspect sources, growth, local checks, optional model review, and unknowns.
3. Prepare an independent concept as a review draft.
4. Review the draft in a separately configured launch flow before requesting a wallet signature.

Preparing a draft is not launch approval, funding, signing, transaction submission, or on-chain confirmation. Tickers, contract addresses, and other people's phrases stay research-only. A model review cannot request a transaction or enable execution.

## What the supplied local source implements

The original Gem Search engine is a loopback Python application with SQLite, an optional local Node executor, and an explicitly selected `LAUNCH_MODE`. Its offline `dry_run` is a local rehearsal: it performs no signing, metadata upload, or broadcast and is not an on-chain simulation.

When an operator separately enables its live built-in PumpPortal executor, the source applies these constraints:

- At most **25,000,000 lamports (0.025 SOL) per attempt**, including fees, and **five attempts per rolling 24 hours**. Failed attempts count. API subscriptions are outside this SOL allowance.
- **Zero developer buy.** Only bounded ComputeBudget instructions and a single validated Pump create/create_v2 instruction are accepted; exact mint, creator, and metadata must match. Address tables are resolved with finalized RPC.
- A dedicated treasury funds an isolated creator wallet. The source checks construction before allocating SOL, simulates the signed creation, and returns remaining funds after success when they cover the return fee.
- Durable SQLite reservations, process locking, persistent isolated wallet keys, and signed transaction state protect restart recovery and project/narrative deduplication.
- Transaction state is saved before the first submission. An uncertain outcome remains pending and prevents new allocations. The original signature is reconciled; no replacement transaction is generated automatically.
- Pause affects future dispatch. It cannot cancel a transaction already submitted or remove an external bridge's accepted work.

These are descriptions of the original source code, not promises that a launch will succeed or features enabled by installing the Musebook spider. Never upload local wallet/key files with research JSON, and never copy treasury keys into hosted browser assets.

## Other providers

The original source supports a versioned HTTPS bridge protocol described in [LAUNCH_PROVIDERS.md](LAUNCH_PROVIDERS.md). Bridge requests carry structured jobs and spending constraints, not wallet keys. The bridge owns signing and must enforce its own spending policy. A bridge receipt is a provider report; it is not independent on-chain proof.

The source guide reports that an unsigned PumpPortal probe was checked, while real token creation and Pinata upload had not been verified in that source snapshot. An unsigned transaction, configured provider, draft, or successful rehearsal cannot establish a funded launch.

Copyright (c) 2026 Gem Search contributors. Adapted for Musebook under the [MIT license](LICENSE).