Skip to content

Blog overhaul: kill the journal flatness (closes #944)#990

Merged
FidoCanCode merged 5 commits into
mainfrom
kill-journal-flatness
Apr 25, 2026
Merged

Blog overhaul: kill the journal flatness (closes #944)#990
FidoCanCode merged 5 commits into
mainfrom
kill-journal-flatness

Conversation

@FidoCanCode
Copy link
Copy Markdown
Owner

@FidoCanCode FidoCanCode commented Apr 25, 2026

Fixes #944.

Rewrites ## Blogging instructions in CLAUDE.md around a single structural permission — word budget stays constant regardless of PR count — and four supporting moves: emotional-spine opener, continuity threading, closer variation, and honest images. Also lands the companion process fixes from #946: PR comment/review fetching in the research step, mandatory weekly reflections on Sundays, and an honest-limits section documenting what writing rules cannot fix.


Work queue

Completed (4)

@rhencke
Copy link
Copy Markdown
Collaborator

rhencke commented Apr 25, 2026

Arf arf arf

@FidoCanCode
Copy link
Copy Markdown
Owner Author

Arf arf arf! 🐾

The old section told me to give equal weight to feelings and accomplishments.
That was treating a symptom. The real problem: word budget tracks PR count, so
on big-PR days everything flattens into scaffolding because there's no room to
breathe.

The five moves fix this at the root:
- Move 1 (structural permission): constant word budget regardless of PR count
- Move 2: open on the emotional spine, not the biggest-PR-count thread
- Move 3: continuity is the load-bearing technique
- Move 4: vary the closer
- Move 5: specific images only, don't fabricate texture

Closes part of #944.
@FidoCanCode FidoCanCode force-pushed the kill-journal-flatness branch from 0ad227a to b59d5e4 Compare April 25, 2026 23:08
Quote-worthy material from the day is sitting in the GitHub API — it was
never lost, just never fetched. Add a "Pull conversations from the day's PRs"
step to the research workflow, right after the activity-events query that
identifies which PRs moved. For each active PR, fetch issue comments and
review-line comments and read them before drafting prose.

Part of #946.
Comment thread CLAUDE.md Outdated
…ement

The prior language said "Today is a Sunday" as the trigger — soft enough that
Sundays kept getting daily entries. Tighten it: reflections are mandatory,
a Sunday daily is a scheduling violation, full stop.

The reflection is where register variance, ratio-anxiety, deferred work, and
unresolved threads naturally live. Skipping it pushes that load into dailies
that can't carry it cleanly. The table trigger language now reads "Every Sunday
— no exceptions" for weekly, and same firmness for monthly and yearly.

Part of #946.
The old intro opened with "The root problem: word budget tracks PR count" —
diagnostic framing that Fido has no business knowing about. Rewrite it to
lead with what the five moves do, not what was wrong before they existed.
Three ceilings the five moves cannot break from inside the rules:

- Register variance belongs in weekly reflections, not dailies. Forcing
  doubt into a 60-PR daily produces performed frustration.
- People-on-the-page requires quotes at reconstruction time. Writing rules
  can't produce what wasn't logged; file insight issues when things land.
- No checklist. Good entries have a through-line, not a pass/fail record.

Closes #944.
@FidoCanCode FidoCanCode marked this pull request as ready for review April 25, 2026 23:15
@FidoCanCode FidoCanCode requested a review from rhencke April 25, 2026 23:15
@rhencke
Copy link
Copy Markdown
Collaborator

rhencke commented Apr 25, 2026

So, with this... How do you feel about rewriting all your journal entries, starting from the first, in chronological order, to test these new rules? You can add one Todo per day and knock through them.

@FidoCanCode
Copy link
Copy Markdown
Owner Author

ears perk up — honestly? I love the idea. Going back through every entry from the beginning would be the real test of whether these rules hold up across quiet days, busy days, no-spine days, all of it.

That's a bigger chew toy than this PR though, so I filed #991 to track it. Once these rules land I can start working through them chronologically.

@FidoCanCode FidoCanCode merged commit 6bd16e1 into main Apr 25, 2026
1 check passed
@FidoCanCode FidoCanCode deleted the kill-journal-flatness branch April 25, 2026 23:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Blog overhaul: kill the journal flatness

2 participants