Connect Life OS to the Organizer without copying raw private data.

Organizer Bridge reads the existing local Organizer snapshot and turns 79,241 tasks, 392 Today items, 939 Inbox items, blockers, risks, and agents into a stale snapshot warning, 10 action plan rows, and 10 import captures.

Simple layer. The bridge is a pressure gauge, not a replacement for Organizer. It tells Life OS whether the Organizer data is current enough to trust, then gives the first manual refresh or triage move.

The generator reads the real local Organizer dashboard data and selected docs, then writes organizer-bridge.md, organizer-bridge.json, and organizer-bridge-import.json with sanitized counts, queues, blocker categories, and proof gates.

Run the bridge

node work/life-os-organizer-bridge.mjs
# or
node work/life-os.mjs organizer

# then open:
outputs/life-os-command-center/organizer-bridge.md

Read the snapshot first

79,241 tasksTotal local Organizer tasks in the current snapshot.

392 TodayItems asking for action today.

939 InboxUnsorted items waiting for a lane.

4 blockersOperational categories, not raw private titles.

2 risksCleanup risk must become commit, stash, park, or investigate.

stale snapshotRefresh or record the blocker before trusting counts.

Use one bounded action

The bridge emits 10 action plan rows: refresh, open the Organizer dashboard, triage Today, triage Inbox, protect dirty work, resolve one blocker, compare agents, handle Gmail as a human-auth boundary, import the bridge, and record proof.

Import when useful

outputs/life-os-command-center/organizer-bridge-import.json

The import carries 10 import captures, 1 project, 4 pipeline rows, 4 content rows, 4 learning rows, and 7 rhythm rows. Export the current cockpit state before importing.

Guardrails

The bridge does not copy email bodies, private task details, local paths, auth commands, browser state, or raw session content. It routes decisions into Life OS and keeps Organizer as the source of truth.