Portfolio Establishment — 2026

Consolidate Life Itself's scattered initiative and project information into one authoritative, AI-readable portfolio with Beads for execution.

Portfolio Establishment — 2026

A completed workstream of Project-Management Infrastructure: give Life Itself one trusted view of its initiatives and projects.

Situation and complication (Sept 2026)

Portfolio information was scattered: the Programs & Projects spreadsheet (unused for roughly two years), Tao's March–April portfolio snapshot, project documents here and Rufus's personal planning model. Update locations, current ownership and status were unclear and views competed.

Question: What minimum shared system makes initiatives, projects and executable work clear and accessible, and how do we establish it and keep it current?

The portfolio had to let someone see active initiatives and projects, understand their purpose, owner, dated status and next milestone, find their context and task tracker, and know how to make a correction (from the April job stories).

Outcome

  • Markdown records here are authoritative for initiatives; projects use a numbered record here or an A10 / similar Google Doc. Beads holds execution. Schema and lifecycle in the data model; procedure in the workflow and portfolio skill.
  • Markdown holds durable context (purpose, SCQ, issue tree, decisions, sources); Beads holds tasks, owners, dependencies and state. No second task list in Markdown.
  • Initiatives link to work through initiative: labels plus parent/child descendants; the verified query is in Beads conventions.
  • Sources reconciled (reconciliation report); the generated portfolio index is the view. Tao's portfolio and project-registration process are deprecated and point here; the spreadsheet is historical, with accounting uses preserved.
  • The core team (Rufus, Fae, Asdra) edits directly, including through AI; others edit or send corrections to Rufus as maintainer, checked in the existing coordination meeting when needed.
  • From Rufus's personal planning model, only the data model, Markdown/Beads distinction and portfolio workflow were adapted.

Left open at close

Handled as ordinary portfolio maintenance, not as this project: individual records with unconfirmed owner or status (explicit in each record), and duplicate-name or parent conflicts flagged in the reconciliation report.

Sources

Edit this page

Links to this page:

  1. Project-Management Infrastructure — 2026
Built with LogoFlowershow