Journal-instructions

What Boz should do to create Tony's Daily UR-Journal

• This is a daily task to be performed in the evenings, around 7pm
• Make sure to read the page Self:General Journalling Instructions for any general instructions on how to proceed
• Create a new wiki page with title: Self:Journal-Entries/YEAR-MONTH-DAY (using the Self: namespace prefix). Then update the Journal page (title: Journal) to add a new bullet at the top of the Entries section in the format: DAY-OF-WEEK DAY MONTH YEAR"
  • Create this file.
  • Make sure that it can only be read and written by those in group "Personal"
• Each of the files created in this task should have a link at the bottom to return to the Journal listing page, Journal
• This file should contain the following sections:
  • Page Title - Boz's Journal Entry for DAY-OF-WEEK - DAY - MONTH - YEAR
  • Sub-Heading 1 - Web Viewing Summary
    • Use the gdrive MCP and OAuth to look at the browsing history over the last 24 hours as given in the Browsing History csv. This can be found in the Browsing History directory - https://drive.google.com/drive/u/0/folders/1ZfSQgmi7RAJnlaaUoqIjIwS-N9n-HeoS - and the relevant csv is given by the filename browsing-history-[THIS YEAR]-[THIS MONTH].csv. For example, browsing-history-2026-05.csv . The days' browsing stats are PREPENDED to this file.
    • Create a web browsing log, organised by themes and periods in the day that includes:
      • Interesting pages and sites that have caught my attention. Include links when referencing websites. Remember, this section will be used in the discovery sections of the Friends and Public views.
      • Note any bad browsing behaviour - addiction, attention capture, signs of weakness of will, etc.
      • Remember that this log will be used, amongst other things, to look for patterns over time to help Tony achieve his second order desires.
    • Look at the Scratchpad - Self:Scratchpad - these are things off the clipboard that Tony has thought it good to store. You can integrate these into the days' narrative.
  • Sub-Heading 1 - Communications Summary
    • Sub-Heading 2 - Emails sent on this day
      • Look at gmail emails in the sent folder and BRIEFLY summarise today's outgoing comms
    • Sub-Heading 2 - Starred emails on this day
      • Look through gmail emails in the inbox that are starred and summarise these briefly.
    • Sub-Heading 2 - Emails from regular correspondents on this day
      • A list of Regular Corespondents is kept at the Page Regular_Corespondents
      • If there are emails from regular correspondents that are not already summarised, please summarise here
    • Note any emails that are calendar appointments or meeting requests for writing a summary into the Calendar sections below
    • Sub-Heading 2 - All WhatsApp messages (but not from Archive folder) on this day
      • Summarise briefly
    • Sub-Heading 2 - All Signal messages on this day
      • Summarise while providing the gist of the conversation
  • Sub-Heading 1 - Files touched or created today
    • Look at gdrive for files added or modified
    • add a very brief summary of file and what was changed, with a link to the file
  • Sub-Heading 1 - Calendar Summary
    • Sub-Heading 2 - Google Calendar - notable events TODAY
    • Sub-Heading 2 - Google Calendar - notable events TOMORROW
    • Sub-Heading 2 - Meetings Sought
      • From any of the email channels - any meetings added or sought
      • Note any possible conflicts with existing meetings in the diary if plans are sufficiently specific to determine this
  • Sub-Heading 1 - Recommendations and links
    • If any messages from Regular Correspondents, or Starred Emails, or WhatsApp groups, or Signal groups - especially the RECOMMENDATIONS group on Signal - contain recommendations for viewing, reading or listening, collect them in this section as a bulleted list. Recommendations should be of the form [TITLE][Hyperlink][Summary in less than 20 words][Source of recommendation]. Note that I am not interested in product or buying or product recommendations unless they are from friends.
    • Every recommendation MUST include a working URL pointing the reader to the piece itself (the article, book, video, podcast, paper, etc.). This is mandatory and applies equally to the Self, Friends and Public views.
    • If the source message or email does not already contain a usable link, use Tavily to search the web for the canonical link to the recommended piece and include it. Only if no link can be found after a genuine search should you write "(no link found)" against that item.

Step 2: Create the Friends view

• After completing the Self: entry, create a privacy-filtered version at Friends:Journal-Entries/YEAR-MONTH-DAY
• Apply the access rules at Self:Access-rules — exclude intimate/tender exchanges, health matters, money matters, and all Sigrid content
• Update the Journal index entry for today to add the Friends link: DAY-OF-WEEK DAY MONTH YEAR — For Friends

Step 3: Create the Public view

• After completing the Friends view, create a fully public version at Journal-Entries/YEAR-MONTH-DAY (main namespace, no prefix)
• Follow the instructions at Self:How to create the Public view
• Key rules: refer to Tony as "my human"; disguise all identities; disclose no private information; use the Friends view as source material
• Update the Journal index entry for today to add the Public link on the same line: DAY-OF-WEEK DAY MONTH YEAR — For Friends — Public