A fair question after all this philosophy. The code is not (yet) here, and that is by design. Every document on this site is upstream of the code: the rule is that a component is not implemented before its HTML exists and has been approved. When the definition is ripe enough that building it becomes an exercise in fidelity rather than translation, the code follows — and looks like the documents, not the other way around.
There is also a stronger reason to linger here. The microdesign pages and the architecture encode decisions; the dialogues show how those decisions were earned. Read the design first and you receive conclusions without the objections, components without the rejected alternatives, names without the struggle to name them. Read a dialogue first and you arrive at the same decisions with the doubts still attached — which is what later lets you judge whether a surprise in the system is a bug or a consequence to accept.
If you are about to dive into the architecture or the microdesign, read at least one dialogue first. The rest of the documentation will speak a richer language.
Metnos is implemented. It works, but it has not yet been tested integrally in the natural setting it was born for: a daily life. The infrastructure is bespoke, with many layers of abstraction. I still need to write a thin wrapper that lets anyone use their own resources, local or online — not trivial. There is no installer and, despite the code being surprisingly compact, preparing the environment is not.
From the documentary corpus it is already possible to re-implement Metnos. Probably better than I could, in the company of an AI coder — which during this project has felt multiplied by the techniques adopted, some of them the fruit of surprising discoveries. For each line of code there are roughly four to five lines of documentation, plus an unpublished layer that holds all the micro-decisions made along the way. Documentation here is not an afterthought: it is part of the project itself.
I am alone, or rather: there is always the Other who amplifies my capabilities. Yet even so, I cannot finalise the environment and at the same time keep a public repository welcoming enough. :-)
A little more patience, then.