the world of dizzi

Status · August 2026

From a personal network to a product family.

The proof came first. The company follows. This page says where the project actually stands — including the parts that are not finished.

Where it stands today

An independent project, before incorporation. One builder, working with AI coding assistants under a written method that is itself part of the repository. Ten applications, nine of them around one headless core, joined by a contract that is enforced by test rather than by memo.

Three of the six figures this site leads with can be checked against the current tree of a public repository: the application count and the document count in the published folder, and the length of the build script in this site’s own. Three cannot — the private commit count, and the two Python figures, whose extract left the current tree on 6 August 2026. Each is named as such, on the page that states how each of the six was counted →

  • No revenue yet. Nothing has been sold; there are no customers.
  • Since 4 August 2026 a small part of the fleet trades with my own money. Trading on my own account, no outside capital, no offer to anyone. There are no results on this page: this site shows how the system is built, not what it earns.
  • Public since 23 July 2026 — first 966 files of code as one curated commit; since 6 August 2026 a curated set of 38 documents. The code is no longer part of the current tree; all rights reserved.
  • Documentation in German. The code is private; the documents show its structure and its rules.

Why it scales

The contract makes every app separable

Each application already runs alone, on its own port, with its own database. A written export contract specifies how one app — plus the core and the parts of the shared libraries it actually uses — becomes a self-contained, sellable bundle. To be exact: that contract has design, stubs and contract tests — the packaging tooling itself is not built yet.

Local-first is a selling point in Europe

Data stays on the machine that produced it. Sensitive classes never reach a cloud model, by manifest and by default. That is a compliance story that starts from architecture instead of from a policy page.

The method is the reproducible advantage

Laws, contracts, research protocols and written hand-overs between AI build chats — the same machinery that produced ten applications produces the eleventh. It is written down, which means it can be taught.

Read the two contracts this rests on: docs/16 — the app contract· docs/66 — the app export contract

Where it’s heading

  1. Public snapshot Done — 23 July 2026.
  2. Website & first product editions In progress.
  3. Incorporation Germany.
  4. First pilots With partners who want the local-first version.

No dates I can’t keep — the chronicle sets the pace. The repository shows what has actually been built, with the date on it. That is a better forecast than a roadmap with quarters on it.

What I am opening

Early conversations with partners and investors. If you build in this space, evaluate in it, or would use a local-first version of one of these applications, the useful next step is a conversation — starting from the documents, which are already open to read.

This page is an invitation to talk, not an offer of securities.

Start a conversation Read the documents first
Principle · honesty

“If a value was never measured, the system says so instead of showing a zero.”