myclawMykleos is the project of an assistant: not a chatbot, and not an "autonomous agent" in the sense in which that expression has by now been drained of meaning — but a system designed to act on the user's behalf, and, with the same care, to know when to stop. The interesting part of such a system is not the code: it is the definition. To write, before writing the code, how it ought to be made, which limits it honours, and in what vocabulary it addresses the human who uses it. That is the part which code, on its own, could never produce.
Neighbouring ideas have already been explored by openclaw and zeroclaw. It is from them that this project draws courage, and to them goes, first of all, my acknowledgement. Mykleos does not wish to be a clone: it is a starting point for experimenting with a few specific ideas — the distinction between laws and ends, the separation between whoever proposes and whoever judges, the care not to turn usefulness into intrusion. A testing ground, not a solution.
Not the code. Good code, someone will write better than me — and that is fine. Here you will find the documents: the architecture, the decisions, the days of reflection. The process of definition, not the product. A reader of these texts receives, on closer look, a more durable object than any implementation: a set of motivated choices, and a way of reasoning that can be reused elsewhere. And in the end, yes, also the code — but only the code that is needed to reassure the author and the reader that ideas must, sooner or later, find their way into reality.
This project has been written with the constant help of an artificial intelligence system. Much of what you are reading, the SVG figures of the documents, the tables, the microdesign pages, were born from a dialogue with a machine that held the pen when mine grew tired. It is not merely a confession: it is the point of the project itself. Mykleos imagines an assistant that gives wings to the one who uses it, so that they can focus on analysis rather than on execution. Building its definition with an assistant is already, in miniature, a proof of concept. A recursive experiment.
Roberto and The Other, in four Giornate. From how the need for ultimate ends first arises, to the cardinal sentence — the Constitution does not judge; teleology does. Not fiction: only the structure is dialogic, the content is real.
EnterIf you would like the how after the why, three other doors:
One HTML document per component of the architecture. Rule: a component is not implemented before its HTML exists and has been approved. Today there are 21 approved documents, covering the full Phase 1 design and the subsequent extensions.