Content pipeline — LTP diagrams

Generated from content-pipeline.ltp.yaml; the YAML is the source of truth, see also the report. Diagrams are generated, not hand-edited: python3 scripts/ltp_to_mermaid.py docs/plans/ltp/content-pipeline/content-pipeline.ltp.yaml --view <view> --markdown.

How to read: arrows point from cause to effect (or from condition to what it is necessary for). Solid arrows are asserted; dashed arrows are contributes-to links, which in the current reality tree are candidate causes agreed in chat but not verified. Box colours come from each entity's role: red undesirable effects, orange root causes (thick border for the three critical root causes Rufus named), grey observations or evidence.

Goal

Current reality

Conflict clouds

Not linked

• c-e-pk-promote-later: Pieces that do well get fuller packaging later through a promote step (possible for some pieces, such as Dougald Hine on Illich).
• c-e-bs-system-time: A regular slot of system time is set aside, for example with support from Asdra, as chosen in the project-management infrastructure cloud.

Future reality

Prerequisite

Transition

Not linked

• t-e-sop-checklists: Write the SoR publication SOP checklists (Episode, Fast release, Promote). (lip-93f.2.10)
• t-e-workflow-reality: Post-production runs with confusion because no piece has a brief.
• t-e-uriel-pipeline-task: Uriel's Asana task Develop Content Production Pipeline (due 1 November) already maps stages, owners, hand-offs, a pre-publish QC, a release brief template and an approval pathway, tested on Debold episode 1.