Publications SOP — developing and releasing publications

Define a standard operating procedure for (a) developing publications and (b) releasing and marketing them, using the Wisdom white paper launch as the reference case.

Publications SOP — developing and releasing publications

Parent: Content Production and Marketing Pipeline. Related: Publications initiative, whose "Where work goes" section holds the current routing proposal.

Beads: lip-93f.2.14 (includes the white-paper SOP lip-93f.2.12, the PDF and diagram pipeline lip-93f.2.13, a Wisdom launch retro, a launch formula and the routing decision).

Current SOP (canonical, in 2rbook)

The procedure itself lives next to the papers, not here. Don't duplicate it in this record.

Start with the briefing. All procedures are indexed in docs/procedures.md. What remains here: the launch retro (lip-93f.2.14.1) and the open questions below that the 2rbook doc doesn't settle.

Objective

A repeatable way to (a) develop a publication (white paper, essay, book chapter) to final text, and (b) release and market it, so each new paper starts from a known skeleton rather than from scratch.

Initial analysis (2026-10-07)

Written before the 2rbook SOP existed; kept as background.

  1. One view per publication: yes. That's the real need. Text, cover, announcement and webinar are written together and depend on each other, so one epic fits. Keep the announcement draft next to the essay in the repo (launch-copy.md beside essay.md). Then the copy and the tasks live together.

  2. Home: 2rbook is fine for now, if you treat it as the publications repo. It already holds wisdom, cultural-evolution and noema, not just the book. If papers ever get other authors or their own team, split them out then, not now.

  3. The real risk is collaborators, not tools. Beads works for you and agents. Asdra and Sylvie don't see it. And #263 shows the actual friction: questions for you got pasted into GitHub and pinged in gchat. Fix that, not the tracker:

    • Questions for you become beads flagged for you (bd human, or a who:rufus label). You get one queue of "Rufus needs to decide", and nobody has to chase you in chat.
    • Collaborators get a read-only view generated from Beads, such as an auto-updated issue body or page with their tasks and what's blocking them. They reply in comments or chat, and you or an agent update Beads. Beads stays the only source of truth, and nobody keeps a second list by hand.
    • Or Asdra learns bd. That's fine if she's willing, but don't make the system depend on it.

  4. The biggest win is a template, not routing. Every paper launch is the same shape: lock text, title page and byline, cover, PDF, landing page, announcement, mail-out, promotion, optional webinar. Turn that into a Beads formula (bd formula / bd mol pour white-paper-launch), so each new paper starts with the full skeleton and its dependencies. That is the white-paper SOP (lip-93f.2.12): written as a template rather than a document, it stays in use.

  5. Don't redesign during the launch. For Wisdom, ship from the epic as it stands. Then hold a 20-minute retro: what was missing, what was friction. Turn the result into the template, plus a decision on the routing.

Rufus's corrections (2026-10-07)

  • Asdra does see Beads. Sylvie and Rosie don't, but they mainly do specific, well-defined pieces of work; coordinate them directly or output instructions in a form they can read. Worth noting as a design constraint, not a blocker.
  • Asdra currently knows her tasks, and most now depend on Rufus.

Issue tree

  • How do we develop a publication to final text (drafting, review, diagrams, title page, byline)?
  • How do we release and market it (cover, PDF, landing page, announcement, mail-out, promotion, webinar)?
  • Where does publication work live? ✅ Facts in the paper's front matter in 2rbook; remaining work in the paper's Beads epic (2rbook SOP, 2026-10).
  • How do collaborators outside Beads (Sylvie, Rosie) get readable instructions?
  • How is the PDF produced: Google Doc export, or Markdown rendered through pdf-report-publishing? ✅ Markdown master in 2rbook, built with pdf-report-publishing/typst/build-paper.sh (2rbook SOP, 2026-10).
  • What is the diagram standard, and which logo goes on papers and diagrams? ✅ Seeds of Renaissance leads; rules in the SoR design system (logo.md, diagrams.md); see the rebrand project (2026-10-08).
  • How much marketing push does each paper get? (Strategic question, held in the content strategy issue tree.)

Sources

Edit this page
Built with LogoFlowershow