← Polymath.OS // Captain's Log

Daily update

2026-07-11

Github Repos only have about 2gb of space. Probably should transition the blog posts to their own repos, like I have the projects set up in the matrix. Project showcase may have been a better choice of words. Or project array. matrix is definitely better than array. thinking about a 6 way or 9 way rock paper scissors type game but it's procedurally generated based off of content. so each rock/paper/scissors is associated with a generated logic statement and you can find the right answer comparing all of them. Not explaining this too well.

Site updates not coming along as well today. Still working tho

Update Log — Build‑Time Note Formatting Reset

Summary: The entire note‑formatting system has been rebuilt from scratch. Formatting + tagging now happens automatically during the site’s build pipeline — not inside Obsidian. Wasted too much time on this

What Changed

1. Formatting moved out of Obsidian entirely

The old setup (Templater triggers, vault scripts, hotkeys) is gone. The new system lives in:

Code

scripts/note-format.mjs
scripts/generate-content.mjs

Every deploy:

2. Notes can be written however you want

Your workflow is now:

  1. Write notes in Obsidian — messy, broken, untagged, whatever

  2. Sync/push normally

  3. Deploy

  4. The site auto‑cleans and auto‑tags everything

Your vault stays raw. Your site stays polished.

The module is deterministic and idempotent — running it twice produces identical output.

New Features

4. Massive tag expansion (16 → 59 tags)

The tag vocabulary now covers:

need more tags still, enough to cover every skill. I'll be happy enough when I have 1000 skills and ~3000 tags.

5. Optional “clean the actual files” command

If you do want your vault’s .md files cleaned once (instead of only at build time), you now have:

Code

bun run format-notes

This:

You also have a single-file version:

Code

bun scripts/format-notes.mjs <path-to-note>

This gives you the “run once per note unless I want to rerun it” workflow.

Why It Runs Every Build (and why that’s good)

The build-time formatter:

There is no downside to running it every build. It’s pure text processing — cheap and safe.

If you want the “once per note” model, use the CLI command above.

Deployment Instructions

Code

cd "C:\Users\c\Claude\Projects\Resume Website"
bun run format-notes      # optional: clean your actual note files once
bun run generate          # optional: preview build
git add -A
git commit -m "Build-time note cleanup + expanded auto-tagging + on-demand formatter"
git push

Cloudflare will run the build-time formatter automatically.