There are a couple of things I’d like to touch upon this week, and they revolve around the content and sessions that I’ve been hosting and sharing this week.

We’ll start with a thought…

Delegate busywork, not genius

This is one of the main conclusions that we reached in the Hermes Workflows workshop that I hosted on Friday…

Agents, when you provide them with the context from your Obsidian vault, i.e. SOPs, your thoughts, your daily history, become very very good at executing the set admin tasks that you do on a daily basis.

For example, in the workshop, I demonstrated how I hardly ever touch any other surface aside from Obsidian and Hermes anymore, besides some very final touches before content or marketing emails go out.

This is because Hermes can connect to MCPs and APIs, and do all of this tiresome work for me.

What it can’t do right now is substitute for what I’m calling personal ‘genius’.

Us humans work in a unique way – we’ve got worldviews, opinions, emotions, and an entire life history that an agent will never have, and this is what we’re having to draw upon more and more in a world where generated text is a commodity.

Thus, substitute your agents in for the busywork, but never, ever delegate genius.

We’ve also been writing about this recently…

The assistant-and-intern model

Before Friday’s workshop, I also published an article around the setup relating to how I think about using the two different types of agent in my stack…

​https://medium.com/obsidian-observer/an-assistant-and-intern-both-ai-run-my-operations-now-a7a05611b59f - click this link to read!

The idea now is that I follow a heuristic to figure out how I delegate work to my agents, local (Claude or Codex) and cloud (Hermes).

The local agent is my intern, it helps me with all the tasks that I’m normally doing myself, locally, with me there to oversee what it’s researched and generated from my vault.

The cloud agent is my personal assistant, taking care of the admin and the busywork (the kind that you’re delegating to leave more room for genius).

And as for myself and PARAZETTEL?

A community and Premium update

I announced a few days back, in email, that we’re altering things slightly in Premium in terms of pricing tiers and structure.

You might also have seen, if you’re already inside the Community, that the next event is a ‘New Intro Course’.

This is correct, and I’ve closed the front of the Community to reflect this. It’s been a bit of a journey figuring out the structure that I want PARAZETTEL to take, alongside the other projects I’m working on, but I know something…

I want there to be more material and more opportunity to learn about PARAZETTEL for an easier entry point than what exists right now.

Hence the new Intro Course, which is going to be so much more than just the sequences of emails that I used to offer in the past.

In due time I’ll email you with more details, so keep an eye on your inbox for my name!

•••

In other news, it might be a little quiet on my front this week as I’m attending a campus designed to give Italian engineering students an immersive experience in English.

I’m in Trentino, in the Dolomites in northern Italy, and the days are pretty packed with exercises and activities.

However, I’ll see what I can get written and sent out regardless, especially regarding the new Intro Course.

Talk soon,

– Theo

More from PARAZETTEL...