Operator Guide · Chapter 06

The OPEN: convention

A simple discipline that prevents the most common failure mode in personal operating systems: losing track of loose ends.

The problem

You're in the middle of work. Something surfaces — a vendor to call, a decision pending, a thread to revisit, an unread email that probably matters. It doesn't fit cleanly anywhere. It's not a project. It's not a task on a list. It's a loose end.

If you ignore it, it'll surface again later when it's too late.

If you stop work to file it properly, you lose flow.

If you write it on a sticky note, you'll lose the sticky note.

If you put it in a separate tool ("inbox app," "task manager"), you've created another tool to maintain.

The harness solves this with a one-line discipline.

The convention

Anywhere in today's daily log, type:

OPEN: short description of the loose end

That's it. No formatting, no preamble, no decision about where it really belongs. Just OPEN: followed by what you'd otherwise lose.

Examples:

OPEN: Call Acme Vendor about December invoice discrepancy
OPEN: Decide Q3 marketing budget by Friday
OPEN: Review Hartford policy renewal before signing
OPEN: Follow up with Jamie on the partnership conversation
OPEN: Check whether the cold brew vendor restocked yesterday

You can drop OPEN: lines anywhere in the daily log file. Most operators write them in their own section, but mixed in with Work Completed is fine too. The convention is the prefix, not the location.

What happens to OPEN: lines

Two paths:

Path 1: Resolved by end of day

You handle the loose end. Delete the line, or mark it resolved:

~~OPEN: Call Acme Vendor about December invoice discrepancy~~ — RESOLVED: spoke with them, refund issued

Path 2: Carried to tomorrow

You don't handle it today. Leave the OPEN: line in the daily log.

The next morning, the morning-brief script (chapter 09) scans yesterday's daily log for OPEN: lines and includes them in tomorrow's brief. Your day starts with them visible.

Why this works

Three reasons:

1. Zero friction to capture

The cost of writing OPEN: short description is lower than the cost of opening a task manager. Friction matters because most loose ends surface during flow states where any context switch is expensive.

2. Surfaces, doesn't store

Most tools store tasks. The OPEN convention surfaces them. The difference matters: stored tasks accumulate forever and become noise. Surfaced loose ends either resolve quickly or get promoted to real tasks.

Loose ends that linger 3+ days in your OPEN: queue are signal — either the loose end matters more than you thought (promote it to a priority in BRAIN.md) or it doesn't actually matter (delete it).

3. Reads itself

You don't have to remember to check your OPEN: list. The morning brief reads it for you and surfaces what's still open at 6 AM tomorrow.

What NOT to use OPEN: for

Three failure modes:

Real tasks

If something needs to happen on a specific day, it's a calendar event, not an OPEN: line. Block your calendar.

If something requires a chunk of focused work, it's a priority in workspace/BRAIN.md, not an OPEN: line. Promote it.

The OPEN: convention is for loose ends — undefined-shape items that you might handle today, might handle next week, might decide are nothing.

Operational reminders

If you find yourself writing OPEN: send Friday update email every week, that's a recurring operational task. It belongs in a cron job, a calendar event, or an SOP — not in your daily log.

The harness has automation for recurring work. Don't simulate cron with daily OPEN: lines.

Emotional or strategic items

OPEN: figure out what I want to do with my life is not a loose end. It's a strategic question that won't be handled by an inbox scan tomorrow.

Strategic and emotional items belong in 11-strategy/, in conversation with mentors, or in dedicated thinking time — not as OPEN: lines competing with "call the vendor."

The morning brief integration

The morning-brief script does this each day at 6 AM:

# Pseudo-code
YESTERDAY_LOG = "12-daily-log/YYYY/MM-Mon/YESTERDAY.md"
open_loops = grep "OPEN:" YESTERDAY_LOG

# Pass to AI synthesis as one input among several

The AI sees yesterday's OPEN: lines and may surface one in TOP PRIORITY, BEFORE LUNCH, or OPEN DECISION sections of the brief.

If yesterday's log has no OPEN: lines, the brief just says "Nothing pressing" in those sections — which is honest. A clean OPEN queue is a signal that you're either staying ahead of loose ends or under-capturing.

The 3-day rule

Any OPEN: line that persists 3+ days unresolved gets one of three treatments:

Resolve it now, even if imperfectly. (Most "lingering open loops" are just delayed 5-minute tasks.)
Promote it to BRAIN.md as a priority, with a clear next step.
Delete it — if it hasn't earned attention in 3 days, it probably won't.

Don't let your OPEN: queue accumulate beyond ~10 items. A long queue creates anxiety; a short queue is actionable.

A small habit, a large effect

The OPEN convention is the cheapest discipline in the harness — three seconds to write a line, zero ongoing maintenance.

It's also the discipline that most directly addresses the "things falling through the cracks" pain. After two weeks of consistent use, you'll notice that small items aren't slipping past you the way they used to.

That noticing is the harness compounding.

Next chapter: loop signals — automated monitors that surface decay before it becomes a fire.