🚀 Amy Rocket Launch Channels — quick-start#

Intent: let Amy listen in one or more normal Discord channels without instantly running every message. Amy adds 🚀; the original author can edit/improve the message; when they click 🚀, Amy launches the final prompt into a new thread and mirrors progress back to the channel dashboard.

🏷️ Naming — Ompcord vs Amy. Ompcord is the omp⇄Discord bridge (product/plugin); Amy is the bot persona it runs. You install Ompcord; Amy is who answers. Rename phases 1–5 are complete at docs/command/runtime/package level: package name ompcord, wrapper runtime ompcordd.mjs/ompcordd.service, and compatibility for amyd.mjs, /amy, /pi-discord-remote, legacy config, and ~/.omp/amy-sessions/. Repo directory stays pi-discord-amy until final filesystem cutover. See the rename plan.*

flowchart TD
  A[💬 Allow-listed user posts in launch channel] --> B[🤖 Amy reacts 🚀]
  B --> C[✍️ User may edit/improve message]
  C --> D{🚀 Same author clicks?}
  D -- no --> X[🛡️ Ignore: wrong emoji/user/channel]
  D -- yes --> E[📊 Amy replies with channel dashboard embed]
  E --> F[🧵 Dashboard message starts session thread]
  F --> G[🧠 Thread runs omp prompt]
  G --> H[🪞 Thread dashboard mirrors progress to channel dashboard]
  H --> I[✅ Done / ❌ Failed]

⚙️ Config#

# 🚀 Channels Amy primes with rocket. Defaults to DISCORD_HOME_CHANNEL_ID.
AMY_LAUNCH_CHANNEL_IDS=1513664007146438666

# ✂️ Future-proof: other emojis can become plan/debug/review later. v1 = rocket only.
AMY_LAUNCH_EMOJI=🚀

🧠 Exact behavior#

🛡️ Safety invariants#

flowchart LR
  A[Reaction event] --> B{Emoji is 🚀?}
  B -- no --> Z[Ignore]
  B -- yes --> C{Message channel is launch channel?}
  C -- no --> Z
  C -- yes --> D{User allow-listed?}
  D -- no --> Z
  D -- yes --> E{User is original author?}
  E -- no --> Z
  E -- yes --> F{Prompt non-empty?}
  F -- no --> Z
  F -- yes --> G[Launch once]

• 🚫 Bot messages and bot reactions are ignored.
• 👤 Only the original allow-listed author can trigger their own message.
• 🧷 Source message id is reserved as pending before awaits, blocking rapid double-click duplicate threads.
• 🧹 If reply/thread creation fails, the reservation is removed so the user can retry.
• 🪞 Mirror edits are best-effort; failing outside dashboard edits never kill the thread run.

🧩 Implementation map#

🖥️ Compact code comments rule#

Keep comments short, practical, and emoji-scannable:

// 🚀 Prime only; user may edit before confirming by clicking the same rocket.
// 🧷 Reserve before awaits so rapid double-clicks cannot spawn duplicate threads.
// 🧵 The channel dashboard owns the session thread, preserving visible source relation.
// 🪞 Mirrors are outside powerpanels; failures are non-fatal Discord I/O.

✅ Verification checklist#

flowchart TD
  A[🧪 node --check] --> B[🧪 bun test]
  B --> C[📚 hugo --minify]
  C --> D{Live daemon idle?}
  D -- no --> E[⏸️ Wait; do not sever active run]
  D -- yes --> F[🚀 redeploy]
  F --> G[💬 Post in launch channel]
  G --> H[🤖 Amy adds 🚀]
  H --> I[👤 Author clicks 🚀]
  I --> J[📊 Channel dashboard appears]
  J --> K[🧵 Thread starts]
  K --> L[🪞 Progress mirrors]

Commands:

cd ~/pi-discord-amy
node --check amyd.mjs && node --check ompcordd.mjs && node --check dashboard.mjs && node --check launch.mjs
bun test

cd ~/funday/dev/docs
hugo --minify

🧭 Future reaction modes#

Do not add more modes until 🚀 is live-smoked and stable.