Turn too many projects into one protected portfolio.

Project Portfolio OS is the decision layer for project sprawl. It chooses one primary project, keeps a small active set, parks the rest, and forces a proof gate before you open another front.

Simple layer. The board captures everything; the portfolio decides what deserves capacity. Use it when sessions, projects, learning resources, client work, and company work all feel equally urgent.

The generator reads local session import, refresh signals, Watchtower, weekly review, company builder, pipeline, delivery, cashflow, presence, learning, and Life Compass files. It writes Markdown, JSON, and a cockpit import.

Run the portfolio OS

node work/life-os-project-portfolio-os.mjs
# or
node work/life-os.mjs projects

# then open:
outputs/life-os-command-center/project-portfolio-os.md

Use the project states

PrimaryThe one project protected before any new front.

ActiveUp to five secondary projects with weekly capacity.

ParkedGood ideas with a written reopen rule and no execution.

Merge/KillItems that need one 20-minute decision, not more work.

Decide with the matrix

revenue adjacency
emotional load
proof gate clarity
session pressure
client usefulness
capacity honesty
risk and privacy

Import into the cockpit

outputs/life-os-command-center/project-portfolio-import.json

Proof from this run: Project Portfolio OS writes 30 portfolio items, 6 active projects, 12 parked projects, 5 merge/kill candidates, 7 decision criteria, 8 dependencies, 7 weekly capacity rows, 5 review cadence rows, 7 next actions, and 9 cockpit captures.

Guardrails

This system does not delete, archive, rename, move, publish, or externally change projects and sessions. It is a local decision map; irreversible choices remain manual.