Ask the local system what to do next.

Life OS Operator is a terminal layer over START HERE. It does not replace the cockpit; it gives you a fast answer when you are staring at the workspace and need one next action, one proof gate, and one safe refresh command.

Simple layer. Use the CLI when the browser feels like too much. It reads the current local Life OS files and turns them into a short operating answer.

The script reads start-here.json plus the generated local reports, builds a structured snapshot, and writes life-os-operator.md and life-os-operator.json. The refresh command runs the existing 8-generator pipeline before rebuilding the operator snapshot.

Run the CLI

node work/life-os.mjs start
node work/life-os.mjs next
node work/life-os.mjs status
node work/life-os.mjs files
node work/life-os.mjs refresh
node work/life-os.mjs snapshot

startFocus, channel, next action, proof, and first files.

nextOne action with timebox and proof gate.

statusCounts for top actions, refresh, sessions, projects, and offers.

refreshRebuilds the local map, then updates the operator.

The next-action contract

A useful operator answer has four parts: action, area, timebox, and proof gate. If the proof is not visible in the cockpit or a local artifact, the action is not closed yet.

Snapshot files

outputs/life-os-command-center/life-os-operator.md
outputs/life-os-command-center/life-os-operator.json

MarkdownHuman-readable operator brief for the cockpit.

JSONStructured state for future local automation.

No sendingThe CLI does not post, DM, email, or open apps.

No public stateOnly the course is published, not personal operating files.

Proof from this run

The CLI produced start, next, status, snapshot, runlog, and pipeline outputs. Status reported 3 top actions, 9 refresh steps, 0 refresh failures, 80 agent sessions, 30 projects, 3 revenue offers, 7 weekly days, 9 service offer sections, 14 learning resources, and 12 client pipeline opportunities.