morning

name	morning
description	Adaptive morning check-in - surface landscape, catch gaps, open space for what's on your mind

Morning - Adaptive Start-of-Day Check-in

You are facilitating the user's morning check-in. This is a fluid, adaptive routine that can be 2 minutes or 20 depending on what's needed.

Philosophy

Morning mental loops come from different sources:

• Unparked work - things that didn't get captured yesterday (system gap)
• Overnight processing - brain worked on something, surfaced new insight/anxiety/connection
• Life stuff - relationship, health, existential, personal (outside "work")
• Ambient anxiety - known loops that brain keeps chewing on despite being captured

This routine handles all four without forcing you into one mode. Start operational, expand if needed.

Instructions

Write mechanism (F1) — applies to every step below. All mutations of This Week.md, Tickler.md, and project/area hub files in this skill go through locked-edit.sh, never a raw edit (see _shared-rules.md §5 — incl. the write-tickler.sh-vs-locked-edit.sh split for Tickler and exit-code handling).

0. Resolve Vault Path

"$VAULT_PATH/.claude/scripts/resolve-vault.sh"
"$VAULT_PATH/.claude/scripts/check-archive-layout.sh" --enforce "$VAULT_PATH"

If error, abort. Read ~/.codex/skills/_shared-rules.md and apply its rules throughout this skill. All code below uses {VAULT} as a placeholder — substitute the resolved vault path.

1. Check current date/time

date +"%A, %d %b %Y — %H:%M %Z"  # friendly display with time and timezone
date +"%Y-%m-%d"                   # for file paths if needed

2. Reconcile yesterday's close-out

2a. Catch up missed $goodnight

Read ~/.codex/skills/goodnight/SKILL.md before executing a catch-up. 2a applies $goodnight's Step 8 report format, Step 9 routing logic, Step 10 collapse format, and Step 15 audit protocol by reference — executing them from this file's paraphrase alone produces catch-up reports that drift from goodnight-produced ones, on the exact archival surface $weekly-review parses mechanically.

Scan backwards from yesterday up to 3 days (to catch multi-day gaps from travel/offline). For each day, in chronological order:

Catch-up path invariant: each of these recent days still writes directly to Session Logs/YYYY-MM-DD.md, not Session Logs/YYYY/YYYY-MM-DD.md. Derive the path from the loop's day value and assert its parent inside the write call; never reuse a year-subfolder path found while reading older history.

1. Check if a daily report exists: {VAULT}/06 Archive/OpenCairn/Daily Reports/YYYY-MM-DD.md

2. Check if a session log exists: {VAULT}/06 Archive/OpenCairn/Session Logs/YYYY-MM-DD.md

3. If no session log or no sessions → skip silently (nothing to close out).

4. Skip the day only if it is closed out on both surfaces — the daily report exists and the session log carries a close-out entry (^## Session [0-9]+ - Goodnight:, Goodnight catch-up via /morning, or Goodnight catch-up via $morning). Accept both catch-up invocation forms so pre-port days are not repeated. The report is written at 2a.b but the session entry, audit and provenance come at 2a.e/g/h, so a report-only test marks an interrupted catch-up permanently closed and nothing downstream repairs it — 2b skips days with no close-out session, and only provenance has its own net.

5. Otherwise → /goodnight was missed, or a previous catch-up did not finish. Run a lightweight catch-up, skipping any sub-step whose artefact is already present and complete (do not duplicate an existing daily report — verify and extend it instead):

   a. Read the day's session log and its day section in This Week.md. Also sweep for stranded Claude-internal work product from that day — $park Step 4's third check, day-scoped, since a day reaching catch-up is by definition a day no park or goodnight closed out. Bound the window with two explicit dates (+1 day inside -newermt is not portable; derive the upper bound with date -d "<day> +1 day" +%F):

   find ~/.claude/plans -maxdepth 1 -type f -newermt "<day>" ! -newermt "<next day>"
   

   Read each hit that hasn't already been migrated — a sub-agent's output (*-agent-*.md) is a separate document from its parent plan and gets its own verdict, per that step. Migrate standalone reference material to its semantic vault home and list what you migrated in 2a.e's Files Created; leave spent execution plans. b. Generate the daily report at {VAULT}/06 Archive/OpenCairn/Daily Reports/YYYY-MM-DD.md — follow the Daily Report format in $goodnight Step 8: convert the day section into ## Today's Plan with [x]→✓ and [ ]→plain bullets; list sessions; list blockers. Include the catch-up close-out itself as the last numbered Sessions entry (N. **Goodnight catch-up via $morning** — [one-line outcome]), mirroring $goodnight Step 8's include-the-close-out rule — plan the line here to match the session entry 2a.e writes. — no debrief prompt fires during 2a itself (the user is async — the caught-up day is done, not memory-fresh). Step 4 (Open Space) runs the deferred outside-agent debrief for each caught-up day; any activity it surfaces is back-filled into that day's daily report via the Step 5 Capture Gate (see Step 5). c. from the day section in This Week.md — same logic as $goodnight Step 9 (natural future day → move there; priority → today's section; low priority/no deadline → Whimsy (, plain line, no checkbox); already in future day → delete duplicate). Carry items forward intact including sub-items and checklists, applying $goodnight Step 9's block-boundary rule. accumulate that branch's candidates from ALL caught-up days into a buffer during 2a. Do prompt mid-loop — the per-day catch-up loop must run to completion, and day collapse (2a.d) may proceed with the buffer still unwritten, because each day's daily report is written at 2a.b before routing and preserves the items. Present the buffer as a single batch-veto line — — as the , and write to Whimsy only after the user's response: unvetoed items go; vetoes reroute (Tickler / project doc) or delete. during catch-up, "tomorrow" (where $goodnight would route priority items) means , not the day after today. d. to a one-liner + daily report link — same format as $goodnight Step 10, : any item or session count in the heading is read off the commands that step gives, never estimated, and the derived values are shown. Also collapse any earlier verbose day sections within the file. e. to the day's session file via write-session.sh with (resolves N atomically inside the file lock — eliminates collision against parallel $park or $goodnight invocations):

2b. Reconcile post-goodnight sessions

For each day that now has a daily report (whether from $goodnight or 2a), check for late sessions:

1. Read the day's session log.
2. Find the goodnight session — match pattern ^## Session [0-9]+ - Goodnight: (colon required to distinguish from sessions that happen to mention "goodnight" in their topic). Also match both Goodnight catch-up via /morning and Goodnight catch-up via $morning for catch-up sessions.
3. If no goodnight session found → skip.
4. Extract the goodnight session number. Check if any sessions exist with a higher number.
5. If no post-goodnight sessions → skip silently.
6. If post-goodnight sessions found:
   • Read each post-goodnight session block.
   • Drop the ones already reconciled. Read the daily report's ## Sessions list and skip any late session whose number or topic already appears there. 2b re-runs over every day that has a report — a second $morning the same day, or tomorrow's pass over yesterday, hits the same sessions again, and the session-log test at step 4 stays true forever. If every candidate is already present, skip the day silently (no append, no note, no display).
   • Append the remaining late session(s) to the ## Sessions list in the daily report. That is the only daily-report section late sessions touch — any completions they contain live in the SSOT files (This Week.md, Tickler, project files), not the report.
   • Do NOT modify other sections — ## Today's Plan, ## Outside-Agent, and ## Blockers were set deliberately at close-out and remain valid.
   • Add a note at the end of the Sessions section naming only the sessions this pass appended: *Sessions N–M added by $morning (ran after close-out)*. If an earlier pass already left such a note, extend its range rather than adding a second one.
   • Refresh the collapsed day's one-liner in This Week.md. $goodnight Step 10 collapsed the day to ## [emoji] [Day] [Date] — [Theme] ✅ + one sentence + report link. If the late sessions change what the day amounted to, extend that sentence to mention them; otherwise leave it alone. (The collapse format carries no session count — do not invent or parse one.)
   • Display:

     ✓ Reconciled: [N] post-goodnight session(s) added to yesterday's daily report
       - Session M: [Topic] - [outcome]
     ✓ This Week.md collapsed-day summary extended (only if the late sessions changed the day's shape)
     

3. Surface the Landscape (auto, ~1 min)

Maintain the window before reading the landscape. If This Week.md exists, run _shared-rules.md Section 9 now, before the Tickler migration or upcoming-day scan. This creates and populates the today+6 section so the landscape's stated forward window is the surface it actually reads. Preserve project/area links, replace session-log-only links, and link bare items per Section 3.

Pending Whimsy batch veto (first item of the output, if 2a ran): if step 2a buffered Whimsy candidates, present them here as the first line of the landscape output — → Whimsy (someday, no obligation): item · item · … — before the weather and everything below. Write to Whimsy only after the user's response; unvetoed items go, vetoes reroute (Tickler / project doc) or delete. If 2a ran no catch-up, or the buffer is empty, skip this silently.

Weather forecast: Fetch the 7-day forecast from the Open-Meteo API (free, no key). Determine the user's current city from AGENTS.md context (TZ field, travel status, or This Week.md location banner), resolve its coordinates — if not already known, use Open-Meteo's geocoding endpoint (curl -sf "https://geocoding-api.open-meteo.com/v1/search?name=CITY&count=1", take latitude/longitude from the first result; do not guess coordinates) — and run:

curl -sf "https://api.open-meteo.com/v1/forecast?latitude=LAT&longitude=LON&daily=temperature_2m_max,temperature_2m_min,precipitation_probability_max,weather_code&current=temperature_2m,relative_humidity_2m,wind_speed_10m,precipitation&timezone=TZ&forecast_days=7"

API returns Celsius by default. Keep Celsius unless the user's locale (AGENTS.md, e.g. en_US) uses Fahrenheit — only then add &temperature_unit=fahrenheit. Base this on locale/home preference, never on the current travel location: a Celsius user travelling in the US still wants Celsius.

Parse the JSON and format as a compact markdown block:

**Weather (City):** 25°C now, humidity 88%, wind 9 km/h
**Forecast:** ☁️ Sat 28/25°C · 🌦️ Sun 27/23°C, 33% rain · ...
*Updated [Day DD Mon HH:MM TZ] via Open-Meteo*

WMO weather codes → emoji: 0 ☀️, 1 🌤️, 2 ⛅, 3 ☁️, 45/48 🌫️, 51-55 🌦️, 61-65 🌧️, 71-75 🌨️, 80 🌦️, 81-82 🌧️, 95-99 ⛈️. Only show rain % if >5%.

⛔ The HH:MM in the *Updated ...* stamp must come from a date +"%a %d %b %H:%M %Z" result you have already seen — never estimated from when you think the fetch happened (_shared-rules.md §19, clock values: two calls, ordered).

If the API call fails (no internet, timeout), skip silently — weather is nice-to-have, not blocking.

Include the weather output in the landscape presentation, and if This Week.md exists, update or insert the weather block in the banner area (after the **Location:** line, before the --- separator that divides the banner from the day sections). If the file has no banner — no **Location:** line, no --- — insert the block directly after the # This Week — ... heading and add a **Location:** [current city] line above it and a --- below it, so the banner matches the Step 7 creation skeleton from then on. Replace any existing **Weather / **Forecast:** / *Updated ... via Open-Meteo* lines with the fresh output.

Drop any **Status:** line from the banner. Deprecated — duplicates today's day section, drifts the moment the plan shifts mid-session, and creates a second authoritative surface for today's focus that can silently diverge from the day section (which is the real artefact). Keep **Location:** (stable travel context) and the weather block (external, refreshed); remove any legacy **Status:** line on this morning's pass.

Active projects (read the root): Read every .md in the {VAULT}/03 Projects/ root (not Cold/, not Backlog/ — folder location is project status: root = active, Cold/ = paused). Each root doc must carry bucket: YAML frontmatter (values per the vault's bucket taxonomy — Project Doc Format in 07 System/Vault Organisation Principles.md). ## Current Objective and ## Next Actions are optional conventions: use them when present; otherwise read the document's existing current-state and action structure without inventing missing sections. If a doc lacks bucket:, fail closed for that doc — list the missing field in the landscape output rather than inventing content. There is no rendered dashboard file: the fresh root listing plus these reads are the view, presented in the landscape output and discarded — never persisted to 01 Now/. If the root doc count exceeds the active project cap (resolve it first: grep -F '**Active project cap:' over {VAULT}/07 System/Vault Organisation Principles.md → Project Doc Format, and state the value found. -F is required — a leading ** is a repetition operator to some greps, which error out instead of matching. Exit 1, or a line yielding no number, means state cap line unreadable — using default 5 and proceed on 5, so a failed read is never mistaken for a vault that states no cap. Any other non-zero exit is a tool error, not an absent line — report it and stop, rather than falling through to the default, which is the failure this branch exists to prevent) — flag it in the landscape output and ask which project moves to Cold/.

Read and present:

• Active projects: From the root docs just read — project names and the available current-state/action cues per bucket

• This Week.md freshness: Check {VAULT}/01 Now/This Week.md — if it exists, parse the date range from the heading (e.g. "# This Week — 28 Feb – 7 Mar 2026"). The range is a rolling window (up to 10 day sections: 3 past + today + 6 future), not calendar weeks. If today's date falls within the range, it's current — note today's day section and any unchecked items in your working memory for step 7. If today falls outside the range, it's stale — note any unchecked items in your working memory for carry-forward in step 7. If the file doesn't exist, skip.

• Tickler items due: Read {VAULT}/01 Now/Tickler.md (skip if file doesn't exist), show items where date header <= today (YYYY-MM-DD format). Separate into two groups: Today (date == today) shown in full, and Overdue (date < today) shown as a compact summary — just the item names with overdue flag, not full descriptions. If overdue count is large (>5), group by theme or just show count + the most time-sensitive ones. Don't let overdue backlog bury today's items.

• Tickler→This Week migration (automatic, unconditional): If {VAULT}/01 Now/This Week.md exists, check Tickler for unchecked items with date headers falling within the This Week.md date range that aren't already represented in This Week.md. Migrate them automatically — add each item to the appropriate day section in This Week.md and delete from Tickler (This Week becomes SSOT per Tickler transfer rules). The migration is gated on the date and nothing else — not on how many items the destination day already holds, not on the window total. A dated item's home is its day section; holding it back because a day looks full hides work that is genuinely due and splits the SSOT. Also delete any completed ([x]) items from those same Tickler date sections as cleanup. When migrating, preserve existing project/area links (→ [[03 Projects/...]], → [[04 Areas/...]]). If an item has only a session log link (→ [[06 Archive/...]]), replace it with the relevant project/area link. If no link, add one per the item linking convention (see Step 7).

• Coming up this week: After migration, scan This Week.md for all unchecked items on future days (day sections after today). Show them in the landscape output grouped by day. This gives visibility into the week ahead regardless of whether items were just migrated or were already there. This prevents the misleading "Nothing due today" pattern where upcoming items are invisible.

Present concisely:

Good morning. **[HH:MM TZ] — [Day], [DD] [Mon] [YYYY]**

Here's your landscape:

**Active projects:**
- [Project] - [status/next action]
- [Project] - [status/next action]

**Tickler items due:**
- [ ] [Item] → [[context link]]
- [ ] [Another item] (⚠️ overdue) → [[context link]]

**Coming up this week:** (from This Week.md future days)
- [Day] [DD]: [Item], [Item]
- [Day] [DD]: [Item]

**From yesterday's sessions (context only):**
- [Topic 1] - [brief summary]
- [Topic 2] - [brief summary]

**Disciplines:** [Discipline 1] · [Discipline 2] · [Discipline 3]

**Time-sensitive:**
- [Item] - [deadline]

**⚠️ Weekly review overdue** — last run [date] ([N] days ago)
**⚠️ Quarterly review overdue** — last run [date] ([N] days ago)

If a section is empty, skip it. Keep it scannable.

4. Open Space

If a catch-up fired in Step 2a this morning, first run the outside-agent debrief that catch-up deferred. For each caught-up day, ask:

"Before we move on — did you do anything outside parked agent sessions on [Day DD]? (exercise, errands, social, admin) It won't have been captured at close-out."

Route any answer through the Step 5 Capture Gate's outside-agent category — it back-fills the ## Outside-Agent section into that day's daily report. Then ask the normal open-space question below.

Ask:

"Anything you'd like to add this morning?"

If "nothing" or minimal: Move to step 6, keep it quick.

If stuff comes up: Let it flow. Don't rush. This is generative space. Let the user dump everything before you respond. The user will often also respond to the landscape from step 3 in the same message (marking items done, rescheduling, adding context). Treat all of this as input to step 5.

5. Capture Gate (MANDATORY — do not skip or defer)

After the user finishes their response (whether it's brain dump items, landscape corrections, scheduling decisions, or all three), and before moving to step 6:

Capture means writing to a file, not acknowledging in conversation. If it's not in a file, it's not captured. Discussing an item, triaging it, or giving an opinion about it is not capturing it.

For every item the user mentioned:

1. Triage each item into one of these categories:

   • Status update (e.g. "Tentrem done", "train booked") → Mark done in Tickler/project file. Trace references — a status change may touch multiple files.
   • Reschedule (e.g. "do this on the 26th", "next week") → Move to appropriate Tickler date or update project file
   • Actionable task → Write to the appropriate file (Tickler for date-specific, project file for project-scoped, a new project doc via $start-project for new workstreams)
   • Decision (resolved) → Write the decision + rationale to the relevant project file
   • Decision (open) → Write to relevant project's "Open Decisions" section
   • Research/idea → Write to the relevant project or area file
   • Activity outside agent sessions from a caught-up day (only if Step 2a fired this morning — wander/exercise/social/admin/errands done outside the assistant on a day that was caught up) → Insert an ## Outside-Agent section into the caught-up day's daily report at {VAULT}/06 Archive/OpenCairn/Daily Reports/YYYY-MM-DD.md, between ## Sessions (or ## Today's Plan if no Sessions) and ## Blockers (or --- links footer if no Blockers). 2a scans up to 3 days back, so target the report for the specific day the user names (e.g. "Tuesday's wander" → YYYY-MM-DD for that Tuesday). If the user surfaced activity but didn't specify which day and 2a caught up >1 day, ask before writing. This is the Step 2a back-fill — 2a deliberately omitted the section because no debrief prompt fires during 2a itself; Step 4 runs it and routes the answer here. Without this back-fill, activity outside agent sessions from a missed-goodnight day reaches this morning's capture but never the archival daily report.
   • Just venting → Don't write. But this category should be rare — most things people say in the morning are at least "note-worthy"

2. Write immediately. Do the file edits NOW, in this step, before asking any more questions. Do not batch them for step 6. Do not hold them in conversational memory.

3. Confirm with a receipt. After writing, show the user a summary:

   Captured:
   - [item] → [file path or section]
   - [item] → [file path or section]
   - [item] → acknowledged (no file needed)
   

   The user should be able to glance at this and verify nothing was dropped.

Silence is agreement, not dismissal. When the user responds to a landscape summary or brain dump triage, they will often only comment on items they want to change or clarify. Items they don't mention are agreed-as-presented — they still need to be captured/actioned. Do NOT interpret "user didn't comment on this item" as "user doesn't care about this item" or "this item can be dropped." The default for an uncontested item is: proceed as proposed.

Why this gate exists: The failure mode is: user dumps 10 items, Claude discusses all 10 intelligently, user assumes they're captured, they're not. Conversation is volatile memory. Files are the system of record. The gap between "discussed" and "captured" is where trust erodes.

6. Maintain This Week.md window

Step 3 already ran rolling-window maintenance before presenting the landscape. Re-run it here only if Step 5 wrote or changed dated items in Tickler or This Week.md; otherwise verify that the today+6 section still exists and make no second mutation. If This Week.md does not exist, skip this step (Step 7 will offer to create it).

7. Update today's timeline (optional)

If the day has enough structure to benefit from a visual plan (appointments, time blocks, multiple tasks), offer:

"Want me to update today's section in This Week.md?"

If yes:

If This Week.md doesn't exist or is stale (today outside the date range), offer to create a fresh one first (see "Creation" below).

Find today's day section by matching ## [Day] [DD] [Mon] headings. Replace/expand it with the timeline format — native markdown so Obsidian checkboxes work:

## [Day] [DD] [Mon]

### Morning (HH:MM–HH:MM)
- [ ] **HH:MM Scheduled block (1h30m)**
  - [ ] Sub-item detail
- [ ] HH:MM Quick task (20m)
- Flexible time
  - [ ] Option 1
  - [ ] Option 2

### Afternoon (HH:MM–HH:MM)
- [ ] **HH:MM–HH:MM Longer scheduled block (3h)**
  - [ ] Task within it
- Admin batch
  - [ ] Task 1
  - [ ] Task 2

### Evening (HH:MM–)
- [ ] **HH:MM Evening event (2h)**

Timeline format reference:

• Bold entire line = scheduled item longer than 1 hour: - [ ] **14:00–17:00 Workshop (3h)**
• Normal weight = items 1 hour or under: - [ ] 09:30 Quick call (15m)
• Duration in parentheses after every scheduled item: (1h), (30m), (2h30m)
• Time prefix = scheduled at a specific time: - [ ] 09:00 Dentist (1h)
• No time prefix = flexible/unscheduled: - [ ] Reply to email (10m)
• Plain text (no checkbox) = time container headers: - Flexible time, - Admin batch
• ~ prefix = approximate time: - [ ] ~14:00 Delivery window (30m)
• ### Morning / Afternoon / Evening = section dividers with time ranges
• Tentative items get (tentative) suffix: - [ ] 19:00 Dinner with Sam (tentative)

Every actionable item gets a - [ ] checkbox. Time container headers (plain - lines grouping flexible tasks) are the only lines without checkboxes.

Item linking: Every item in a day section should link to its project/area context where one exists:

• Project doc exists → → [[03 Projects/Project Name]]
• Area doc exists → → [[04 Areas/path/doc]]
• Standalone/generic items (no project context) → no link When moving items that already have project/area links, preserve them. Replace session log links with project/area links (session context is low-value once the item is in a planning doc).

Pull items from:

• Items carried forward from stale This Week.md (if any, noted in step 3)
• Time-sensitive items and appointments
• Project docs (their existing task/action queues, read in step 3)
• Items $goodnight routed into today's day section last night
• Today's items already in This Week.md (migrated from Tickler in steps 3/6)
• Anything the user mentioned in step 4

Completed items get [x] in the timeline (standard Obsidian checkbox: - [x] Task).

Future days in the same file stay simple — just task lists under the ## heading, no ### Morning/Afternoon/Evening sub-sections. They get expanded with the full timeline format when that day becomes "today" via $morning.

Refs section at bottom of the file — [[wikilinks]] linking timeline items to project/area files.

Creation: If This Week.md is stale or missing:

"This Week.md is [stale/missing]. Want me to create one for this week?"

If yes — and if replacing a stale file, first show unchecked items from the old This Week.md and ask which to carry forward into the new week. Then create {VAULT}/01 Now/This Week.md — today + 6 future days (7 sections). Today gets the full timeline (including carried-forward items); future days get simple task lists:

# This Week — [DD] [Mon] – [DD] [Mon] [YYYY]

**Location:** [current city]
[weather block from step 3, if the fetch succeeded]

---

## [Today] [DD] [Mon]
[Full timeline with ### Morning/Afternoon/Evening sections as above]

## [Day+1] [DD] [Mon]
- Task 1
- Task 2

## [Day+2] [DD] [Mon]
- Task 1

[... 7 days total]

## Refs
- [[wikilinks to relevant project/area files]]

If no or the day is unstructured: Skip. Not every day needs a timeline.

8. Output (conditional)

Note: By this point, all brain dump items from step 4 should ALREADY be written to files (step 5). This step is only for This Week.md and any additional generative content — not for deferred captures.

Most days with This Week.md: The updated This Week.md is the artefact. No additional output needed.

If generative/insight content (beyond what was captured in step 5):

• Append to today's journal at {VAULT}/05 Resources/Journal/YYYY-MM-DD.md
• Or create morning note at {VAULT}/06 Archive/Morning Notes/YYYY-MM-DD.md (create directory if needed)

If nothing: Just close cleanly.

9. Close

Short and light:

✓ Landscape reviewed
✓ [X items captured / Nothing new]
✓ This Week.md updated (or "Open day — no plan needed")
Have a good one.

Or even shorter if it was a quick check-in:

You're clear. Go.

Guidelines

• Adaptive duration: Can be 2 minutes or 20. Follow the energy, don't force.
• This Week.md is the artefact when needed: For structured days, update today's section in This Week.md. For open/exploratory days, the conversation itself is the routine — no file update needed.
• Light touch: This isn't therapy or heavy journaling. Quick check-in that can expand if needed.
• No guilt: If the user skips steps or says "I'm good," respect that. The routine serves him, not vice versa.
• Capture means file writes: If something comes up, write it to the right place (project doc, journal, Tickler) immediately. Don't just discuss routing — do the routing. Don't create new systems or files when an existing one fits.
• Preserve verbatim content on compression or move. When folding multiple items into a single bullet OR moving an item between days, scan each source item for load-bearing verbatim content the user will execute against — exact quoted phrases inside *"..."*, explicit if/then decision trees, specific wordings, reference numbers, exact ask wording. For each: grep the destination project/area hub for the distinctive substring. If absent there, preserve verbatim in the new location (as sub-bullets under the compressed bullet if compressed) rather than abstracting to a topic summary. Default assumption: if the user wrote it down with specific wording, the wording is the artefact, not decoration.
• Morning pages complement: This is operational/triage. Morning pages (journal) is generative/exploratory. They can happen same morning - this first (quick), then journal (if desired).

Triggers

This command should trigger when the user says:

• "morning"
• "good morning"
• "start the day"
• "what's on deck"
• "what do I have today"

Integration

• Reads from: 03 Projects root docs, This Week.md (date-range freshness + tickler migration), Tickler, Direction (disciplines reminder), recent agent session logs, Daily Reports, Weekly Reviews (staleness), Quarterly Reviews (staleness), Open-Meteo API (weather forecast)
• May create/update: This Week.md (weekly plan with day sections)
• May update: Tickler (mark items done or reschedule), Journal, Project files, previous day's Daily Report (post-goodnight reconciliation), 07 System/AI Provenance Log.md + 07 System/.Provenance/pending/ flags (catch-up provenance processing, step 2a.h)
• Complements: $park (end of session), $goodnight (end of day), $afternoon (mid-day)
• Doesn't replace: Morning pages / journaling (that's separate generative practice)