Claudio Torres
A personal project
I have never written a line of this code. I have not even read one.
But I direct it, and the decisions are mine.
Pharos is my hobby: a way of working with AI, for myself, my company and me as a person. I describe what I want. The platform builds it, tests it and puts it to work. I say yes to what matters. Beyond that, I only step in when something did not turn out the way I wanted, and I correct it so the next decision goes my way.
Pharos is a personal project. It is not a commercial product and it is not for sale. This site shows what it can do.
Behind the solution there is a second, separate part: a software factory that runs without me, day and night. It has one purpose, to keep the solution current and free of bugs. I still tap the few decisions that are mine, and it is where most of the depth is.
How the factory works, what it builds and the ideas behind it.
One request, start to finish
From a question to a new ability, by the next day
This is what it looks like in practice, with my assistant.
-
Day 1
Someone asks me: can you send a transcript and have it taken care of? I pass the question on to the platform, in plain words.
-
The platform
Agents build the ability, test it and install it. I write no code, and I do not open any.
-
Day 2
My assistant takes transcripts as part of the everyday work, as if it had always done so.
That is the whole idea in one example. New competence comes from a description, not from a project.
What makes it interesting
-
It learns new things. A wish in plain words becomes an ability. Agents build it, test it and install it, and from then on it is there for every agent that needs it.
-
It keeps itself current. New models, new code, new features in what it is built on. It does not just upgrade. It reads what is new and changes how it works to make use of it.
-
It looks after itself. Every fifteen minutes it walks its own path from start to finish, repairs what it is allowed to repair, and puts the rest to me as a proposal.
-
A person says yes. It makes its own recommendations and follows them. But nothing that matters happens without a person saying yes.
Why I build it
I have built systems for others for more than 25 years. Pharos is the first one I have built to replace myself as the engineer. I do not code. I design, I challenge and I test, and the platform does the rest. Read why
Curious?
I write about what the platform learns and how I work with it. The build log keeps the short version, month by month, and I also write about it on LinkedIn.
All the best,
Claudio