iii · The Practices

A structured conversation for the moment before a roadmap exists, when somebody has a feeling about an idea but has not yet figured out what they actually believe about it. It refuses to evaluate the idea. The only thing it tries to do is help the person hear themselves think out loud, in enough detail that they can stand behind what they say next.

Thymos is not a chatbot, and it is not a coach. It is a discipline disguised as a conversation: a way to make the questions that should already have been asked get asked, in a setting where the person answering them is the one for whom the answers matter most.

Lives inside the Praxeum conviction platform.

A workspace for writing the strategy down once you know what you believe, and then handing it to a second AI that has no context, no history, and no patience. Only what is on the page.

The premise is simple. If the thinking you have committed to does not survive a fresh set of eyes (eyes that share none of your assumptions, none of your enthusiasm, and none of your political reasons to be polite) then it is not ready. Telos is the test of whether a conviction has become more than a feeling.

The long middle. The strategy is written. The work has started. Decisions accumulate, priorities shift, the product slowly becomes a different product, and nobody in the room is quite sure when it happened.

Praxis is the part that notices. It reveals where the original conviction sits relative to what is actually being built now, and surfaces the divergence in a way that the people responsible for the work can act on rather than only see in hindsight. It does not enforce; it shows.

Keeps the things that should not get loose. Secrets, credentials, environment variables, documents: encrypted, scoped per project, with an audit trail.

API keys are read-only by default; the narrow write path is its own thing. The point is not that Phylax is a vault. The point is that the secrets and the audit live in the same place, so a question about what was accessed, by what, and when, has an answer.

Live at phylax.praxeum.co; invite-only for now.

Documentation falls behind the code it describes within a week, and nobody trusts it within a quarter. Lexeum is an attempt to keep the record of what a system does close enough to the system itself that the gap stays small.

Built first for our own use across the Praxeum projects; not public. The discipline is the same regardless of audience: write down what you know now, so the version of you that comes back to it later can pick the work up without having to reconstruct it.

The rule against which the others measure. Engineering practices, review patterns, the contract for how AI agents are asked to behave inside a project. Every new project I start now starts from it. This site did.

Kanon is opinionated in the way a careful editor is opinionated: not about what you should say, but about how the saying should hold together so it can be read, returned to, and trusted. The same idea, applied to engineering.