Minimal line diagram suggesting staggered intervals across a vertical guide
Illustrative graphic; not a timetable you must follow.

Structure page

Names before numbers

We start labels with verbs or outcomes so a calendar reads like a story. Quantitative targets appear only after the purpose is legible to future you.

This page offers general informational ideas. Adapt wording to your environment; nothing here is a directive about health or personal safety.

Lenses

Three checks before locking a block

Use them as prompts during planning—not as a scorecard.

Visibility

If someone else scanned the entry, would they understand the intent without a meeting transcript? Ambiguous titles create silent drift.

Dependencies

Note inputs you are waiting on and outputs you owe. Dependencies belong beside the block, not buried in chat threads.

Boundaries are described, not dramatized

A boundary statement might read: “No new requests after 4:30 p.m. except incidents tagged urgent by the on-call owner.” Plain language reduces negotiation loops.

Carry the thread into a sample day

The Routine page stitches these naming habits into a walkthrough. It remains illustrative; substitute your own labels freely.