b32 prompt #6+#7 — Promo idea-capture + outreach contacts infrastructure#

Mode: EDEN. Effort: Max (Medium is fine). Run in a fresh session.
Priority: Post-launch. Do not build this under the June-1 clock — it is the classic thing to over-build while the deadline burns. Run it once the launch pieces (#1, #2) are out.
Drafter: dv_ClaOp47Max, 2026m05d28_13h54. Self-contained.

Update 2026m05d28 — the private home already exists

In the b32 session LLoL had Claude set up a private sibling folder, balospe-launch/ (next to balospe-com/, in no git repo — fully private), with a clean, channel-oriented layout: tweets/ (X/, bluesky/), email/ (reusable templates), Gideon300/ (the tentative ~300 priority targets + per-target letters/), ideas/promo-ideas.md, AA/ (AnyAims task tracking), AHA/ (outreach lessons + where-to-read-in-balospe-com.md pointers), and launch-brief.md. Reference material is read on demand from balospe-com, not copied. So the location question is already resolved. This prompt’s real job is now to populate and refine that workspace: the sweep, the channel strategy, and seeding Gideon300 from LLoL’s paper drafts.

1. Why this exists#

LLoL senses lots of good promotion ideas are buried across the site (“this would make a good blog post / tweet / newsletter item / …”) with nowhere central to land, and there is no list of people worth reaching. This prompt designs two low-friction capture systems — one for ideas, one for people — so neither keeps getting lost. (Continues the b31 §3 note, which suggested a central AnyAims/AHA capture file + a contacts list.)

2. Part A — Promo idea-capture (item #6)#

  1. The capture file already exists at balospe-launch/ideas/promo-ideas.md (private; outside any repo), with a lightweight per-idea format (channel / idea / source link / optional AIMS k/s). Refine the format only if needed; do not move it into the built site.

  2. Relate it to AA, don’t duplicate it. The project’s AnyAims (AA) system is the heavier task store (impact k × urgency s). Keep promo-ideas light for fast capture; define a one-line graduation path: when an idea is ripe, it becomes either real content or a proper AA task. Confirm the intended relationship with LLoL rather than assuming.

  3. Sweep for the buried ideas. Do a bounded pass over likely sources (recent blog posts, the Good News Pack, the Flying-Scroll/stadia pages, recent llogs) and seed the file with the promo ideas already lurking there (each with its source link). Time-box this; breadth over depth.

  4. Enumerate the channels. List the candidate social channels worth a capture lane (blog, X/Twitter, the Jonah newsletter, the existing YouTube videos, and others to consider — e.g. Mastodon, LinkedIn, Substack, Reddit) and recommend a starting few, given LLoL is one person with no marketing team.

3. Part B — Outreach contacts (item #7)#

Privacy — resolved (keep it that way)

The contact list contains personal data. Its home is already private: balospe-launch/Gideon300/ (the tentative ~300 + per-target letters/; a sibling of balospe-com/, in no git repo). Never copy real names/emails into the built site or the repo. Keep all real contact data in that private folder only.

  1. The list + letter templates already exist (balospe-launch/Gideon300/list.md + Gideon300/letters/_TEMPLATE.md). LLoL has paper drafts of the ~300 to enter; help structure and winnow them.

  2. Do not scrape or invent contacts. Seed only with people LLoL names, or obvious already-public ones LLoL confirms.

4. Deliverables#

  • promo-ideas.md seeded from the sweep (it already exists; fill it).

  • Gideon300 seeded from LLoL’s paper drafts (list + letter templates exist).

  • A short note in AHA (and/or an AA entry) pointing to balospe-launch/, so it is findable next session.

  • An execution llog at the next free infra number.

5. Cautions#

  • Low friction wins. If capture is heavier than a sticky note, it won’t be used. Resist over-engineering (no database, no new build machinery).

  • Privacy first for Part B (above).

  • Don’t let this delay launch content — it serves the launch, it isn’t it.