Content Publishing — Strategy and Delivery

Objective

Establish a clear editorial direction and a sustainable ability to turn it into worthwhile, published and well-promoted content across Life Itself's publishing work.

Two connected projects

Project	Central question	Responsibility
Content strategy and plan	What should our content programme achieve over 6–12 months, and which programmes, papers, courses, and supporting channels will achieve it?	Backlog and future streams, audience, objectives and key results, channel/ecosystem baseline, priorities, and a realistic content programme.
Content production and marketing pipeline	How do we reliably turn new and existing material into worthwhile, published and well-promoted content—from deciding what to make of it through to follow-up—at a quality and pace we can sustain?	Editorial decisions for particular material, people, capacity, production, review, release packages, distribution, reuse, and follow-up.

Strategy gives the pipeline its brief; production capacity and results inform what strategy can credibly promise. The two projects can develop together without waiting for a complete strategy before examining actual delivery problems.

Current sequencing decision (Rufus, 2026-09-23): capture the revised strategy question and an initial issue tree of at most ten questions, then park strategy work and focus on the pipeline. The strategy project now contains nine initial questions and its source-linked starting picture. Pipeline improvement can make substantial progress independently through current cases, clear ownership, handoffs, quality checks, and follow-up. Both projects remain in scope; parking strategy is a sequencing choice, not completion or cancellation.

The bridge between them is the editorial decision for a particular piece or body of material: what should we make of it, for whom, where should it live, and what should accompany it? This can be known before production or discovered after recording, and may need resolving before post-production. It belongs within the pipeline, guided by the strategy; it does not require a third project.

This initiative concerns ongoing publishing. The Seeds of Renaissance launch is a distinct project that can draw on these capabilities; it does not define their purpose or scope.

Overall review

Read the SCQ and compact issue tree in each child project as one framing. The strategy draft asks how to choose where publishing effort goes. The pipeline draft asks how to turn that direction and available material into releases and follow-through. The reported course, 2RCon, Emergent Dialog, and Dougald Hine cases illustrate different parts of this problem; they do not yet establish a single dominant bottleneck.

The strategy recommendation is a 6–12 month programme map linked to objectives and key results, grounded in a current baseline. Rufus reports convergence toward audio with some video and a radio-station-like umbrella with multiple programmes; the programme roster and written/course offer need definition. At the pipeline level, a lightweight editorial/release brief for particular material remains a hypothesis, with clear ownership through publication and follow-up. No new tool is selected.

The next operational investigation should follow a concrete current case, such as Emergent Dialog or the recorded Debold series, with a provisional brief and comparison against backlog/post-publication examples. Resume the strategy investigation when we return to that project; it is not the current working focus. This is a recommendation for investigation, not an instruction to publish or build a page.

Existing Beads own the strategic brief and delivery evidence. This draft advances the framing without claiming their research, walkthroughs, or human decisions are complete; it creates no parallel task queue.

Planning and execution homes

Planning owns the work of defining strategy and improving the publishing operation, with durable context in these project files and actionable work in Beads. Comms owns running the publishing operation: individual pieces, editorial scheduling, release packages, and publication. Supporting implementation belongs in the relevant repository, such as DAM, once its need is established. Each task should have one authoritative home, linked from related projects.

Beads project tracker: lip-93f, with lip-93f.1 for content strategy and lip-93f.2 for the production and marketing pipeline. These trackers link the project context and bounded work of establishing the strategy and improving delivery; they do not represent a permanent queue of individual publications. Use bd list --label initiative:content-publishing for the associated work.

The former comms-l53 design queue was migrated here on 2026-09-23. Its records are closed as migrated, not completed, with destination IDs in their closure notes. Existing planning SCQ and issue-tree tasks were reused, retaining their earlier programme links. Earlier research in comms and DAM remains source material, including candidate solutions that have not been approved. Markdown holds durable context and exploratory questions; Beads holds project tracking and actionable work once defined.

Issue tree

Should strategy and pipeline improvement be distinct projects? ✅ Yes — strategy determines what we publish, for whom, and to what end; pipeline improvement determines how we deliver it reliably.
Should they sit under a shared initiative? ✅ Yes — this initiative connects editorial ambition, delivery capacity, and learning across the two projects.
Is this primarily about the rebranding launch? ✅ No — it concerns ongoing publishing; the launch is a distinct project.
Where should cross-cutting planning live? ✅ Here in planning, with operational publishing in comms and scoped supporting implementation in its relevant repository.
Which publishing activities and brands should the first strategy and pipeline improvements cover?
How will we judge whether the combined effort is succeeding?

Sources

Rufus's framing and scope decisions in the planning conversation, 2026-09-23.
September 13 content strategy and pipeline framing, which previously combined these two levels.
DAM research checkpoint and handoff.

Portfolio integration

Current source documents record an ongoing publishing initiative and a confirmed focus on pipeline improvement. The existing body and source links below/above remain the authority for detailed scope. Original planning note: Status: consolidated review draft, 2026-09-23. The two-level structure is agreed; the child-project SCQs, issue trees, and operating hypotheses are proposed for overall review.