Personal Operating System

Operations guide · start here every workday

Decide once.
Execute clearly.

Pinnacle sets direction. Linear holds commitments. The calendar protects capacity. Notion remembers relationships. Repo Markdown preserves source truth.

Open in this order: understand the week, choose today's contract, protect the time, then open only the context required to finish.

One system · five distinct jobs

Keep each surface at its proper altitude.

Clarity comes from the handoff between systems. Duplicate lists create the noise.

Decide

Pinnacle

What matters this week? What fits the runway and the current option-building period?

Commit

Linear

What few outcomes and deliverables have actually earned active attention?

Allocate

Calendar

When will focused capacity exist for the work, meetings, health, and recovery?

Finish

Daily contract

What must be true before today can close without carrying the whole system mentally?

Notion remembers people and business context.

Contacts, companies, interactions, opportunities, meeting context, and reviewed client memory.

Repo Markdown preserves source truth.

Strategy, evidence, plans, research, decisions, and durable artifacts. Git wins when mirrors disagree.

The finite daily contract

Define the day before the day defines itself.

The contract is intentionally small. It protects judgment and creates a real stopping point.

01

One must-win

The single result that most changes the week. It must connect to an issue in `01 Now` and have visible completion proof.

02

Up to two supports

Bounded actions that help the must-win or satisfy a real deadline. They are optional when capacity is tight.

03

A protected block

A real calendar commitment with enough time to produce the proof. No block means no honest commitment.

04

An explicit stop rule

Name the evidence that makes the day complete. Open loops get captured; they do not extend the workday forever.

Done means: the promised proof exists, Linear reflects the next clean move, and no hidden task list remains in your head.

Where does this go?

Route the item before you start working it.

Select the kind of item. The guide will show its owning surface and the next decision.

What did you just receive or decide?

Weekly reset · 30–45 minutes

Make the tradeoffs before execution begins.

The weekly reset is the management handshake between Pinnacle, Linear, and the calendar.

Review proof

What finished? What created evidence? What should close instead of carrying forward?

Reconfirm outcomes

Keep no more than three portfolio outcomes visible in Pinnacle.

Limit commitments

Hold `01 Now` to five–seven. Every addition displaces something.

Allocate capacity

Place the focused blocks, meetings, maintenance, health, and buffer on the calendar.

Set Monday's start

Choose the first must-win and leave a clean, obvious opening move.

Operating rules

Small constraints keep the system trustworthy.

Linear

Track selected execution, not every valid thought.

≤ 3active projects
5–7`01 Now` commitments
  • Every active issue has one project, one queue label, one owner, and a clear close condition.
  • `02 Next` holds approved work waiting for capacity.
  • Close or move stale work. Do not let it decay in place.
  • Use artifacts as issues when the artifact is the actual work or unlocks the next outcome.
Notion

Use memory when the work requires memory.

  • Keep contacts, companies, interactions, opportunities, and client context here.
  • Follow an active Linear commitment into Notion when relationship detail is needed.
  • Return to Linear to record the executable commitment and its completion.
  • Do not copy the daily or weekly task list into Notion.
  • Do not begin the workday here.

Codex heartbeat · weekday mornings

Automation prepares the review. You make the commitment.

The heartbeat compares live state, checks drift, and proposes today's contract. It does not silently change your systems.

Read the status first

ClearThe systems agree and the day fits available capacity.
AttentionA due date, missing block, stale record, or small mismatch needs review.
Decision neededA priority conflict, queue overflow, material runway change, or displacement requires your judgment.
Report only

What Codex checks

  1. Pinnacle health, freshness, weekly outcomes, roadmap, pathways, metrics, and runway events.
  2. Linear project alignment, `01 Now`, `02 Next`, due dates, owners, labels, and close conditions.
  3. Today's calendar and whether focused capacity exists for the proposed must-win.
  4. Notion only when an active commitment requires CRM or client context.
  5. Material drift since the prior successful checkpoint.

Change gate: Codex may recommend a mutation batch. Kalen approves before Linear, Pinnacle, Notion, or Calendar changes.

Drift and recovery

When the system feels heavy, reduce it.

Common drift warnings

  • Starting in Linear without reviewing Pinnacle.
  • Turning Pinnacle into a detailed project backlog.
  • Copying the same tasks into Notion.
  • Treating the calendar as a wish list instead of capacity.
  • Adding to `01 Now` without displacing another commitment.
  • Building more operating machinery during execution time.

Five-step recovery mode

  1. Stop intake and open Pinnacle.
  2. Choose one must-win that materially changes the week.
  3. Move unearned commitments out of `01 Now` or close them.
  4. Protect one realistic block on the calendar.
  5. Resume normal planning at the next weekly reset.

Recovery is complete when the next action is obvious and the rest of the system can wait.

Reference

The short answers.

Where do ideas go?

An idea does not enter `01 Now`. Capture durable thinking in the owning repo. Promote it to `02 Next` only after a weekly decision makes it a real commitment candidate.

When should I open `02 Next`?

During the weekly reset, after an active commitment closes, or when a material change forces reprioritization. Do not browse it as a daily menu.

When should I open Notion?

When the current commitment needs contact, company, interaction, opportunity, or client context. Notion is useful memory, not a required daily checkpoint.

What does Codex own?

Codex can inspect, compare, draft, research, prepare artifacts, and recommend system changes. Kalen owns priorities, recipient selection, external sends, material commitments, and approved mutations.

What if today's plan no longer fits?

Choose the minimum viable day: one must-win, one realistic block, and a stop rule. Capture the displaced work and decide its status during the next planning window.