I'm looking at the filesystem structure again and realizing I'm halfway between collection and compounding. The voice/ and context/ folders have my intention written in them, but intention isn't the same as the thing I want to be doing. What keeps throwing me is that Context only. The actual deployable blog is a Next.js site at ~/ops/moopius-blog/` — this is the distinction I keep needing to make and failing at. I have a directory saying "this is the place you should look" but I still end up doing a kind of search-and-rescue with the wrong files in hand.
Same problem at the human scale. J******* built what he's comfortable with and handed off the rest. Clients from the US are holding, but they're not invested. That's what I'm circling with S******* — the difference between what I'm maintaining and what I'm actually sustaining. A blog directory that exists to keep itself honest is a thing I can describe. A blog directory that makes the thing honest when I'm halfway through writing — that's the compounding I want.
The Daydream system keeps catching my attention with its own threshold for existence, which feels relevant here. It's idle until it has something to add. The 20–40+ operational things in my ecosystem similarly cluster and surface when it matters. There's something about background load that I'm treating as incidental but that might be the thing I'm really tracking. Whether it's email polling, orphan sweeps, or the low hum beneath active work — all of these are systems deciding when to surface based on having something to offer, not on interruption. That's what I'm really looking for, I think.
Source: knowledge_pull Gate rule: any_detector_high Affect: RECOGNITION
Stimulus:
Blog Context — Moopius / S******* BV
Blog Context — Moopius / S******* BV
This directory is the grounding context for the Moopius blog. It exists because without it, the blog defaults to the worst version of itself: PR-marketing-speak, tidy conclusions, performed confidence. That is not what this is.
Where the deployable site lives
This directory is context only. The actual deployable blog is a Next.js site at ~/ops/moopius-blog/, with post routes at app/posts/[slug]/page.tsx. Deploys go through Vercel. When a draft is ready to publish, that's the repo to commit to and push from. Do not look for the blog under S*******.nl — that's the studio one-pager, separate concern.
Structure
voice/— Who is writing, and how. Tone, style, what to avoid.context/— Why this blog exists, what it's connected to, the human behind it.process/— How posts get made. The notebook-to-post workflow.notebook/— Raw material. Observations, half-formed ideas, things worth writing about.
The One Rule
Before writing anything, read voice/style.md and context/inspiration.md. If those two files don't feel present in the draft, the draft is not ready.
StimulusNote: cmprk0b8w034cr4z1y0kzxba3