Digital Sovereignty
My website worked when I was there. That was the problem.
A direct question: can your website answer the five most frequently asked questions you receive via WhatsApp at 10 PM on a Tuesday?
The Logbook
Exploration of ideas, essays, and developing notes on technology, sustainability, and design.
Reading the World with Date
Book of Life — Part 2: What I See When I Lift My Head from the Workshop
This is part 2 of 3 of the Book of Life. Part 1 documented who I am before the projects. This documents the world from where I build them. Part 3 documents what I am building with all of that — the goals, the open fronts, and the system that unites the three parts in one direction.
Antifragile Life Design
Book of Life — Part 3: What I Am Building with All This
The source code of your life is not written once. It is built, project by project, hive by hive, stroke by stroke. It doesn't matter if today you only have a notebook and an idea.
Projects
Iwagé Self-Sustaining System: Map of a Project Under Construction
A self-sustaining system is not declared — it is built subsystem by subsystem, with the data that each stage produces. The nodes of this series document that process in real time: what works, what fails, and what is still a hypothesis.
Purpose
Work with what you have, not with what you expect to have
*For a recruiter evaluating someone who crosses data, field, and trade, the question should not be "how many years of experience do you have in each?" but rather "what rules connect what you do in all three?" The answer to that second question is the only signal that distinguishes real versatility from mere accumulation.
Systems
The Rule of Three Axes: an antifragile life philosophy
Antifragility is not a state that is achieved — it is a practice that is sustained. The most honest question is not 'Am I resilient?' but 'What part of who I am today survives if the part that matters most to me stops functioning tomorrow?' The answer to that is the map of what still needs to be built.
Data & Management
Antifragility in technological systems. What Fable 5 demonstrated
Most AI stacks built in 2024 and 2025 were fragile. They didn't know it because the pressure had not yet arrived.
Data & Management
The Fable 5 Episode and What Changed in My Stack
A well-designed stack does not collapse when a provider fails. What Fable 5 demonstrated was not a failure of Anthropic — it was an architectural failure in all stacks that depended on a single point of jurisdictional failure.
Data & Management
Why I Stopped Being Loyal to a Single AI Model
There is a difference between using AI and working with AI. The former is loyalty by default. The latter is architecture by choice.
Models and Routing
How I Distribute Work Among Eleven AI Models Without Relying on Any
Operating with a single AI model is convenient until that model fails, censors a task, or charges you three times for reasoning that another does just as well. This resource documents the orchestration architecture I use in production from the Ambalá-Calambeo corridor: eleven models with fixed roles, a failover matrix, and prompting rules that prevent the AI from inventing business rules.
Data & Management Applied AI
Sovereign stack, why self-hosting changes the equation
*Self-hosted does not mean isolated. It means that when something fails, the failure is yours — and that is exactly what you want.
Do you want to dive deeper into a topic?
If any of these notes resonated with you or you'd like to collaborate on an idea, let's talk.