I’m doing some tiny experiments in the new year, starting with this one.
Background
For periodic Obsidian notes in my PKM system, I have a Day cluster with Plan, Log, Health, Journal, Review, Actions, and Links. I have a similar cluster model for other time horizons: Week, Month, Quarter, and Year. It also creates visual tools that support my day with View, Base, Board, Canvas, and Drawing. Also, an Claude AI Analysis of Plan vs Log using Plus-Minus-Next, as well as Diabetes Review note is generated to supplement my Review.
My knowledge system model for temporal notes about time have vertical hierarchy and horizontal connections. They include navigation wayfinders to previous, next, and higher time horizons.
I create these linked notes with customized properties and consistent content structure with templates using Python services, shortcuts, or hotkeys.
I have created a Neo4j graph database with a knowledge graph of a model of my Knowledge System Architecture (KSA), which I use to generate Obsidian notes for my PKM system such as my Day cluster.
I'm developing and using PKM services with Python scripts, services, and API endpoints with shortcuts, hotkeys, menus, links, buttons, Siri voice commands and dictation, and Swift user interfaces.
My PKM services include functions for:
- Neo4j graph database access via Cypher graph query language (GQL) for creation, updates, and queries.
- Obsidian PKM services for notes, folders, files, and commands.
- Health services from diabetes data from Glooko and Dexcom apps and websites with glucose, insulin, food, and activity data and reports from my CGM and insulin pump.
- Claude AI review services that generate Day or Week Analysis of my Plan intentions and actual Log activities using Plus Minus Next for my Day or Week Reviews.
Observation
Previously, it took a lot of time trying to manage all the Obsidian metadata properties, template scripts, and consistent structural formats across my temporal notes.
I was constantly reinventing the wheel and still unable to find key knowledge objects in my PKM system.
So I'm currently have been using a new Day workflow that leverages my PKM services. Each day begins with a Day Startup shortcut than runs automatically at 6 am so it's ready to use when I wake at 7 am.
This includes a Create Today service that creates a Day cluster with all the customized linked notes that I need for each new day.
It also does a Morning Review that generates a Diabetes Review, as well as a final AI Analysis for yesterday's Review, and then opens the Plan for today.
I'm using my Day cluster notes throughout the day, and capturing thoughts, questions, actions along with field notes and procedures of what I actually do each day so I can review and refine my periodic workflow practices with automation if possible.
Hypothesis
These are options for ideas, projects, skills, activities, and routines that I might I want to explore as tiny experiments in 2026. Maybe I would...
- Create a Plan for each Day with my top priorities, key actions, and scheduled events.
- Log what happened each Day, including field notes on observations.
- Journal thoughts and feelings about my Day.
- Record Actions that I can do to improve my notes, efforts, or life.
- Capture Links that can be used for various apps, topics, concepts, efforts, or outputs?
- Generate Claude AI Analysis of my Plan intentions and Log activities using Plus Minus Next
- Generate a Diabetes Review from Glooko and Dexcom apps and websites with CGM and insulin pump data.
- Create a Review for each Day with reflections, insights, and next steps.
- Create Workflow automations using shortcuts, scripts, services, and APIs.
Experiment
Initially, I will focus on creating my Day cluster that I can use for my workflow each day to explore how I can simplify and streamline the process. For now, I will specifically work on option 1 about my Plan for each day. So this is my experiment for this week.
> I will use a Day cluster in Obsidian for 5 workdays.
I will post the results of each trial and results after this first week of my experiment.