Manifesto.

The same person who trains for a marathon can read Augustine and ship code. They can keep a garden, study a language, raise a family, and run a company. None of these things are in conflict. They only feel that way because the tools we use to organize our digital lives were designed by people who believed they were.

Hyperpolymath is built on the opposite belief. Specialization is a strategy, not a virtue. The interesting lives are the ones that refuse to choose.

We tell ourselves we are too busy. We are not. We are scattered. A task lives in one app, a calendar event in another, a note in a third, an idea in a group chat, a deadline inside an email thread. The cost of moving information between these places is paid in small, constant attention taxes that add up to most of the day.

The unsolved version of disorganization in our digital lives is the disorganization we would never tolerate in our physical ones. You would not keep your books in nine different rooms with nine different librarians. You should not keep your life there either.

A life-OS does not need fifty primitives. It needs five.

Areas are the long-running domains of a life: health, work, study, relationships, craft. Projects are finite arcs inside an area, including classes and one-off builds. Tasks are the units of action. Captures are the loose thoughts that have not been routed yet. Events are the moments when time itself becomes the constraint, and they live in Google Calendar where they belong.

The verb is route. One sentence in, one action in the right place out. Everything else the system does is in service of that single motion.

The agent does not pretend to be wise. It does not propose strategies. It does not ask three follow-up questions before doing the obvious thing. It takes a sentence, decides which primitive it belongs to, and writes the row. When it is wrong, it is wrong cheaply, and you can fix it in one more sentence.

This is not a limitation. It is the whole point. A good router you trust is more valuable than a clever advisor you have to double-check.

The app you are looking at is one rendering of Hyperpolymath. The real artifact is the contract underneath: a typed schema, a JSON tool definition the agent speaks, and a small set of realtime conventions that keep every surface honest about the same source of truth.

That is why the repository is public and the license is MIT. If the methodology only works for me, it is not a methodology. If you fork the schema and ship something I would never have built, that is not a defection. That is the project succeeding.

The visual register is deliberate. Serif body type, mono labels, generous margins, restrained color. We are trying to build something you would not be embarrassed to use in a library.

Productivity software has spent a decade looking like a casino floor: notifications, badges, streaks, celebratory animations when you complete a chore. Hyperpolymath is the opposite of that. It is a desk, a journal, and a calm assistant standing slightly to the left of the page.

It will not gamify your life. It will not sell your data, ever, for any reason, because there is nothing to sell that you have not already chosen to put inside it. It will not lock you in. It will not pretend to be your friend. It will not ship a feature whose only purpose is to make a graph go up.

It will stay small enough to understand, open enough to fork, and serious enough to use for years.

If the system fits the shape of your life, sign in and start typing. If it does not, the framework is yours: the primitives, the JSON contract, the schema, the patterns. Build the version that fits you. I encourage it.

Either way, the thesis is the same. The way we organize our attention is the most consequential design decision of a life. It deserves better than the tools we have been handed.