Pre-populates the user's weekly Self-RADAR by pulling daily memos, version-control commits, calendar events, call/meeting notes, and the MythOS authoring inventory (delta_sync) for the prior Sunday→Saturday week, then drafting the factual sections (Spiritual Capital, Natural Capital, Social Capital, and the factual portions of Emotional Capital) and leaving felt/reflective sections blank for the user to complete by hand. Runs on or around Saturday; the formatting contract lives in the Self-RADAR Pre-Population Template agent notes — this memo is the workflow runbook. Status: shareable runbook.

Purpose

The Self-RADAR is a weekly relationship-with-self check-in — see 📝Self-RADAR with MythOS for the conceptual overview and the 📝Self-RADAR Setup Memo for the on-ramp. The practice is structured around the 📝Types of Capital framework with one local extension (Emotional Capital). The SR moves somatic → productive → material → social → relational across five sections: Spiritual Capital (by-day quality time with self and others), Natural Capital (labor for financial-capital generation, split Studio / Community / Agency), Financial Capital (money, manual), Social Capital (gatherings + introductions, both work and personal, with Work and Personal sub-bullets), and Emotional Capital (relational substance with Others per partner and Self with sub-buckets — Meta Review anchored in 📝Relational Sovereignty).

Pre-population removes the blank-page friction so Saturday morning opens to a draft already shaped from the week's tracked artifacts. The user's AI agent drafts the factual surfaces; the user writes the felt surfaces and approves the commit. The split is intentional — the recipe never auto-fills Financial Capital balances, Emotional → Others relational substance, Activations, Acknowledgements, Meta Review, or Action Points.

Three artifacts work together on every pre-pop pass: (1) this Process Memo — the discoverable workflow runbook; (2) the Self-RADAR Pre-Population Template — the SR memo's structural skeleton (content field) plus the formatting contract (Absolute Rules, Discriminator Rules, repo→bucket map, tag→bucket map) in its agent notes; (3) the week's SR memo — the populate target.

Prerequisites

• MythOS MCP — get_context, read_template, read_daily_memo, search_memos, read_memo, delta_sync, update_memo, create_memo.
• Self-RADAR Pre-Population Template — read via read_template({ name: "Self-RADAR Pre-Population Template" }) (or the user's customized "My Self-RADAR Pre-Population Template" if they've forked).
• Version-control CLI — e.g., gh for GitHub authoring activity.
• Calendar — e.g., gcalcli, Google Workspace MCP, or another calendar tool.
• Call/meeting notes — e.g., Bluedot or Granola MCP (list/metadata only).

Process

Step 1 — Confirm the SR window

• SR week is Sunday → Saturday. On Saturday the week is today's Sunday through today; otherwise the most recent Sunday → most recent Saturday.
• Announce the start/end dates and target memo title (SR - <Saturday> in Month Day, Year form) before fetching.

Step 2 — Locate the SR memo and read its current state

• search_memos({ tags: "self-radar", limit: 20 }) to find the current week's SR and the prior week's SR.
• read_memo on the current week's SR. Inventory existing content per ABSOLUTE RULE 7 in the template — reshape and bolster, don't regenerate.
• If a memo titled SR - <Saturday> already exists, update_memo it. If not, create_memo with that title and the Pre-Population Template's templateId.

Step 3 — Pull data sources in parallel

• Daily memos — read_daily_memo(date) for each day Sunday → Saturday. Preserve @mention syntax; strip hashtags. Prefer the # Timeline section for work narrative; per ABSOLUTE RULE 2, only - [x] completed tasks may be referenced.
• Version-control commits — platform-specific. For GitHub: gh search commits --author=@me --committer-date=">=YYYY-MM-DD" --json repository,commit --limit 200. Group by repo, capture PR ranges.
• Calendar — platform-specific agenda command (e.g., gcalcli agenda <Sunday> <Saturday-plus-1> --tsv). Group events by date. Exclude subscribed/shared calendars that are not the user's own — e.g., a housemate's or partner's professional/practitioner calendar (bodywork, massage, personal-training, client sessions) the user can see but does not personally attend. For this user specifically, Chase Riner's bodywork-studio calendar (Studio Bodywork, REALIGN Massage, and similar practitioner bookings) is visible but is NOT Brian's — disregard it entirely. Only count the user's own appointments; cross-validate against daily memos when an entry's ownership is ambiguous.
• Call/meeting notes — list only, no transcripts. The user records calls in Bluedot (Granola may be empty); list the week's meetings for cross-validation and presence, not narrative. Cross-validate calls in daily memos.
• MythOS authoring activity — paginated delta_sync(since: <Sunday ISO>, limit: 100) until hasMore: false. Metadata only — no body reads. For a simple total, count memos created and updated in the window (e.g., via get_memo_index filtered on updatedAt); when a bulk operation (a migration or re-embedding pass) has inflated the week, note it inline rather than over-filtering.

If any source fails (auth error, empty result), note the gap, skip gracefully, never fabricate.

Step 4 — Synthesize the draft

• Read the Self-RADAR Pre-Population Template's body + agent notes for the formatting contract and DISCRIMINATOR RULES.
• Treat current SR content as the baseline; layer additively.
• Spiritual Capital (by-day): embodied practices, solo restoration, dates, therapy, quality time, sex, stewardship of space. 1-3 bullets per day. Empty days stay blank.
• Natural Capital → Studio: commits grouped by shipped surface. Project line format @[Project](path) (~N commits across PRs X–Y, ~M memos authored). Standing projects surface every week; empty-week projects get - N/A.
• Natural Capital → Community: community-building work, education events, user onboarding.
• Natural Capital → Agency: group by Partners / Prospective Clients / Client Services / Other.
• Financial Capital: do NOT populate.
• Social Capital (themed; two sub-bullets): Work (work-context networking + work intros) and Personal (non-work gatherings + personal intros). "none this week" if empty.
• Emotional Capital → Others (per partner): factual touchpoint rollups + brief emotional-arc preface (1-2 sentences). Surface partners via calendar dates with non-business individuals, daily-memo mentions of intimacy or relational substance, or call entries.
• Emotional Capital → Self → Household & Life Ops: factual stewardship + self-care touchpoints. Leave feelings for the user.
• Emotional → Self → Activations, Acknowledgements, Meta Review: leave entirely blank.
• Action Points: single empty checkbox.
• Dual-reference activities — sex, dates, therapy, bodywork, social gatherings appear in BOTH Spiritual (by-day) AND Emotional or Social (themed). Don't dedupe.

Step 5 — Review checkpoint

• Do NOT call update_memo/create_memo yet.
• Surface to the user:
• • One-line source summary (e.g. "7 daily memos, ~190 commits across 1 repo, 55 calendar events, 17 calls, 441 memos touched via delta_sync").
  • Any unavailable sources with the reason.
  • Proposed changes (additive — what gets added, NOT a full draft of the whole memo).
  • ONE specific question for the user (not a long triage list). Default-route ambiguous data; surface one focused decision at a time.
  • Self-check confirmation against Absolute Rules 1–7 and Discriminator Rules.
• Ask: "Approve to write, or refine first?" Wait for explicit approval.

Step 6 — Write on approval

• Call get_context, then read_memo for a fresh expectedUpdatedAt, then update_memo (or create_memo if no existing memo) with the approved body and the Pre-Population Template's templateId so the populated memo inherits visibility.
• Return the memo URL in the close-out receipt.

Conventions

• The current week's SR memo typically already exists at run time. Default to update_memo rather than create_memo.
• Slash-form @mentions only (/me/<username>/<id>). Normalize dash-form mentions from daily memos when copying.
• Invocation phrase: "pre-populate my self-radar" — routes the agent here via search; the agent then loads the template for formatting.

Contexts

• 🏷️#self-radar