1. What Happened Today
The day started with some metadata issues and a clear need: putting the human workflow back at the center of the project. In parallel, several accessibility tasks were piling up, so I blocked out three half-days in deep work mode to handle them properly.
We also scheduled a second Letta workshop, this time dedicated to integrating a n8n prompt → Letta pipeline to structure the flow.
Early afternoon, I got to do what I love: lay down the technical foundations. Set up Next.js, created the Supabase database, configured environment variables, installed Tailwind and shadcn… in short, a fresh repo, clear architecture, and that exciting feeling of launching a machine that'll serve us for months.
Then, a big sprint sync with Julie and Louis: the goal was to order all the small tasks so everything flows logically. Timing is tight, so every dependency matters.
Finally, I presented Letta in more detail to Louis. We migrated a first prompt from the old n8n, walked through the Memory Blocks file system together, and how to call agents via API. Louis was very enthusiastic about using all this.
2. Today's Challenge or Surprise
The real discovery of the day:
At first, I'd imagined a single agent responsible for translation/rewriting, with all transformation history documented inside.
But working on my personal project last night, I realized that was a bad idea: managing state creates too many risks of context pollution and makes the system fragile.
The solution became clear:
➡️ one agent per document, isolated, reliable, clean,
➡️ one supervisor agent to coordinate everything.
It's simple, scalable, and much healthier.
3. An Interesting Technical Point
On the technical foundations side:
- Next.js + Supabase give us a solid base,
- shadcn/ui provides a clean interface foundation,
- and of course Letta to manage agents and memory blocks.
So my early afternoon agenda: install Next.js, create a Supabase database, wire up environment variables, install Tailwind, install shadcn/ui.
In short, we're laying the groundwork and it's solid.
It was a day of structure, clarity, and decisions that'll hold up over time.
4. A Human Moment
Watching Louis get excited about Memory Blocks and the agent mechanics reminded me why I love building these kinds of tools.
And working with Julie and Louis on the sprint gave me that rare feeling of collective alignment: same standards, same direction.
See you tomorrow.