Content pipeline — background

Part of Content production and marketing pipeline. Earlier framing and evidence, moved here on 2026-10-20 when the project page was restructured after the LTP. Kept for history and source links; where it conflicts with the project page, the project page and the LTP report are current.

Earlier handoff (September)

Execution handoff: pipeline work briefing. The bounded plan is in Beads under handoff:content-pipeline, with who:ai, who:collab, and who:rufus execution labels. Default model recommendation is Sol; Astra is optional for difficult synthesis. The Beads descriptions and dependencies supersede the earlier generic planning sequence.

Reported examples — 2026-09-23

These are Rufus's examples from the planning conversation, sufficient to sharpen the problem but not a verified inventory or diagnosis. Release status, analytics, owners, and remaining work have not been independently checked.

These examples distinguish selection, deciding how to release, and carrying out publication and follow-up promotion. The April course clarification shows that “awaiting an editorial decision” is too coarse: much of the unresolved choice concerns the release package, not simply whether the material is worth publishing. The strategy supplies criteria about audience, purpose, channels, and desired engagement; the pipeline needs to translate those criteria into a proportionate set of deliverables and complete them. A landing page or dedicated collection can help people find and use the material over time, so supporting work includes more than promotional assets.

Working hypothesis: decide what the material should become, then deliver it

An explicit editorial and release brief may bridge strategy and execution: what to make from the material, for whom and why, where it will live, which main and supporting outputs are needed, and who will produce and approve them. It can begin before recording when the intended use is known, or be formed after reviewing raw material. Confirm enough direction before substantial post-production to guide the edit and avoid unnecessary work; allow the brief to evolve as the material reveals its possibilities.

The brief should distinguish requirements for initial publication from worthwhile follow-up, so optional supporting work does not become an accidental release gate. Selecting an excerpt, publishing a whole interview, assembling a series, reusing material elsewhere, or deferring it are possible outcomes; recording something need not commit us to releasing it.

This is a candidate approach to test against the April course and Emergent Dialog cases, not a decision to add a formal approval meeting or create a landing page for every release. Whether reusable defaults for courses, interviews, or event recordings would save repeated decisions remains open.

Proposed refinement to the diagram

The original drawing remains source material. This working refinement makes the editorial decision visible before post-production, while accommodating both planned and emergent material:

Main and supporting outputs can progress in parallel where their inputs are available; clips may depend on an edit, while a page or announcement can begin earlier. Only supporting outputs designated necessary for the initial release gate publication. Review standards can differ by output and destination. This model is a proposal to validate against actual work, not a claim about the current process.

Candidate outputs

• Content-team organisational chart and approval pathway.
• Organised task and production flow.
• A way to decide and deliver proportionate release packages, including where content lives, announcements, supporting material, and follow-up.
• Clearly designed and structured content pipeline, with appropriate automation.
• Decisions and operating procedures for supporting systems where the delivery needs justify them. DAM, CRM, automation, course distribution, and event ticketing are candidates, not a required implementation package.

Sequencing detail (2026-09-23)

We can inspect current queues, clarify decision ownership, improve handoffs and edit notes, define output-specific review standards, locate current assets, and test completion and follow-up on already-intended releases using a provisional brief for each case. For example, the Elizabeth Debold series notes in #190 identify reconstructing edit notes for four recorded episodes as concrete work; 2RCon #215 already identifies release preparation and supporting-material choices. These issue descriptions are evidence to inspect, not proof that their old dates or state are current.

Choices that depend on strategy—programme identity, long-term channel architecture, major new content commitments, or investment in a new public destination—remain explicit local decisions or are deferred as appropriate. Their uncertainty need not block unrelated workflow improvements. Operational evidence feeds back into strategy as a better account of capacity and effort.

What the pipeline diagram contributes

The original Excalidraw drawing and PNG export are now available here. The filename dates the drawing to 2026-06-24; it was added to this repository and inspected on 2026-09-23. It shows:

Ideas → Pre-production → Production → Post-production → Marketing content → Distribution.

The main stage flow, redrawn from the original (as drawn, not as proposed; the refined flow is below):

Marketing content repeats the same shape on a smaller scale, drawn as a separate sub-pipeline (not connected to the main flow above):

Dotted diamonds are QC checkpoints. The drawing notes that QC "does not exist properly"; yellow means pass with notes for next time, green pass with no issues, and red is undefined. The sub-pipeline's own QC positions are not drawn. See the original drawing for the quality questions, the 2RCon example and the content calendar.

The September 13 interpretation captured this sequence accurately. Direct inspection adds emphasis to these distinctions:

The newsletter twice-monthly and YouTube daily annotations are historical planning inputs, not agreed current targets. Named guests and examples on the calendar do not establish a current release schedule. The linked external video and Substack examples have not been independently assessed in this pass.

Hypotheses as of September (superseded by the LTP)

• Publication and marketing may be the main constraint; the specific limiting step needs evidence from current pieces and handoffs.
• Unresolved release/prioritisation decisions and limited follow-through after publication may be separate constraints. The reported examples support investigating both; they do not yet establish whether the underlying cause is direction, ownership, capacity, or production friction.
• Repeated decisions about release destinations and ancillary material may need explicit ownership and reusable defaults. A release brief is a candidate bridge between strategic intent and production work, not yet an approved process.
• Better asset discovery and continuity may reduce friction, but DAM has not been established as the highest-value intervention.
• AI-assisted hooks and marketing packages may help if they reduce total effort and rework while preserving quality and source fidelity. The AI fit map (2026-10-20) rates each production step for AI fit from Asana evidence; its strongest candidates are operations automation and a single episode package skill. Asana evidences per-piece steps only: it misses most of the backlog, ideation and pre-production, and production is deliberately limited at present (Rufus, 2026-10-20).
• An overview of everything in the content production factory, built from Asana (where Media House work lives), may fill a gap identified on 2026-10-13 by Rufus and Uriel. Not yet scoped or decided.
• An episode record linking sources, edits, marketing outputs, and publications is a preserved candidate design; neither a new catalogue nor a tracker has been selected.

Evidence needed for the next refinement

Current working cases are Emergent Dialog and 2RCon, selected with Rufus on 2026-09-23. The initial case evidence records the existing 2RCon issues, board observations, missing Emergent Dialog identification, and a compact comparison. This is a partial investigation, not a verified inventory or a completed walkthrough.

Use the reported cases above as starting points. The April course and upcoming Emergent Dialog interviews can expose the unresolved choices about where content lives and what accompanies its release; 2RCon offers a backlog case, and Dougald Hine a case of follow-through after publication. Follow both the main output and supporting outputs: what was intended, who owned the decisions and work, what actually happened, and what is still missing. Distinguish time spent working from time spent waiting. Record unknowns rather than inferring them from old task timestamps.

These cases feed the existing queue-evidence task lip-93f.2.1, whose wider scope remains 5–10 pieces and one end-to-end walkthrough. The strategic brief is already tracked by lip-93f.1.1. The diagram and reported examples supply context for the existing SCQ and issue-tree tasks; they do not complete their evidence gathering or human review.

Sources

• Rufus's reported backlog and promotion examples in the planning conversation, 2026-09-23; captured above with unresolved identification and status questions.
• Original pipeline drawing and PNG export.
• September 13 content strategy and pipeline framing, including grouped job stories.
• Pipeline diagram interpretation.
• DAM research checkpoint.
• Earlier episode-record exploration — candidate design, not approved implementation.
• [MASTER] SoR 2026 Objectives and Key Results — PROJECT: 2026 Rebrand Run-up Phases