PM infrastructure — current reality tree
PM infrastructure — current reality tree
Generated from pm-infrastructure.ltp.yaml after the team meeting of 12 Oct 2026; the YAML is the source of truth, see also the report.
How to read: arrows point from cause to effect; solid arrows are causes, dashed arrows contribute to, "refines" and "supports" are labelled. Box colours come from each entity's designation role in the YAML: red are undesirable effects, orange are root causes, grey are observations or evidence, plain boxes are intermediate causes. The numbered headings match the goal tree critical success factors (CSFs).
Diagrams are generated, not hand-edited: python3 scripts/ltp_to_mermaid.py docs/plans/ltp/pm-infrastructure/pm-infrastructure.ltp.yaml --view current_reality --groups docs/plans/ltp/pm-infrastructure/crt-groups.json --markdown (see crt-groups.json for which entities sit in which diagram).
Overview
Core structure only; the per-CSF diagrams below carry every current-reality entity and link.
By critical success factor
CSF1 — Plans aren't recorded in a common way
CSF2 — No consolidated weekly or monthly plan; priority changes ad hoc
CSF3 — People don't know where to look or log
CSF4 — Tasks aren't actionable
CSF5 — Records aren't current
CSF6 — No quick views
Candidate core causes
Four points where the chains converge:
- No agreed rule or system of record for where each kind of thing goes and how it is written (
no_rule,no_system_of_record), feeding unclear locations, varied plans, duplicates and stale tasks. - No planning owner or process (an air traffic controller): no owner, slot or generation process for the weekly plan, so priorities reach people ad hoc.
- Two teams in two tools (GitHub for operations, Asana for Media House), each with genuine preferences; this is the conflict analysed in the evaporating cloud on tools.
- Building while running: processes are being built while work continues, under time pressure, the rebrand and the pace of AI change.
Not linked
Entities with no current-reality link yet (kept visible rather than dropped):
r-e-two-kinds: Life Itself tracks two kinds of thing, reference material and tasks.r-e-projects-two-homes: Projects live either in the planning repository as numbered Markdown or in an A10 or similar Google Doc.r-e-beads-cloud: Using Beads from Claude cloud is not yet routine.r-e-one-tracker-overwhelms: One tracker for everything overwhelms people and AI.r-e-github-subtasks: GitHub sub-tasks inside issues are harder to navigate than Asana's assignable, prioritised sub-tasks and weekly overview.r-e-no-shared-place: Less tech-savvy collaborators have no simple shared place to see and discuss work with us.r-e-no-followup: There is no weekly follow-up on where teams got to with their tasks.r-e-asana-structured: Media House tasks in Asana have templates, sub-tasks and assignments that Uriel built.r-e-asana-tasks-only: Asana mostly records tasks; overview epics there link to reference documents kept in Google Drive or in Git.r-e-projects-live-with-initiatives: Project files often live with their initiative, in its Git repository or Drive folder, rather than in the planning repository.
Other views
Generated with the same script (--view goal, --view conflict --max-nodes 5, --view prerequisite --max-nodes 20).
