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 current 28-generator pipeline before rebuilding the operator snapshot.Run the CLI
node work/life-os.mjs start node work/life-os.mjs now 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 node work/life-os.mjs guide node work/life-os.mjs company node work/life-os.mjs life node work/life-os.mjs projects node work/life-os.mjs pipeline node work/life-os.mjs proposal node work/life-os.mjs outreach node work/life-os.mjs diagnostics node work/life-os.mjs proofassets node work/life-os.mjs resources node work/life-os.mjs agents node work/life-os.mjs delivery node work/life-os.mjs presence node work/life-os.mjs relationships node work/life-os.mjs cash node work/life-os.mjs actions node work/life-os.mjs proofs node work/life-os.mjs ritual node work/life-os.mjs watch
startFocus, channel, next action, proof, and first files.
nowOne command, one file, one timebox, and one proof gate.
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, now, next, status, snapshot, runlog, guide, actions, proofs, ritual, company, life, pipeline, proposal, outreach, diagnostics, proofassets, resources, agents, delivery, projects, presence, relationships, cash, and watch outputs. Status reports 3 top actions, 28 refresh steps, 0 refresh failures, 12 Now Command Console cards, 10 now commands, 12 now proof rows, 12 Guide Router routes, 42 Action Queue items, 36 Proof Ledger slots, 7 Daily Ritual blocks, 12 outreach rows, 8 outreach message packs, 10 diagnostic conversation slots, 0 logged real diagnostics, 7 diagnostic questions, 6 diagnostic scripts, 12 proof assets, 6 case studies, 10 content derivatives, 8 sales proof rows, 18 routed resources, 6 routes, 8 resource decisions, 10 learning moves, 4 agent roster entries, 16 agent orchestration units, 12 agent session decisions, 8 agent handoff prompts, 10 agent proof gates, 6 proposal briefs, company roles/KPIs/assets, 8 life domains, 30 portfolio items, 12 client pipeline opportunities, 5 delivery phases, 30 presence posts, cashflow target/forecast/invoice queue, and Watchtower session signals.