the world of dizzi

Journey

Dated, not narrated

Every node below is a document or a commit in this public repository — or in one of the house’s other public repositories — carrying its date in its own header, its own filename or its own commit. Nothing here is reconstructed from memory.

In short
Every step is dated by a document or a commit, not told from memory.
The oldest public papers are the laws and plans of June 2026; the app contract is dated 12 June.
Public since 23 July 2026, cut back to 38 documents on 6 August.

Milestones

  1. 8 June 2026

    The trading foundations

    The oldest dated documents in the repository: a system overview of the trading AI, fundamental research, and a system-check review. The network began at its riskiest corner, on purpose — if the rules hold where money is, they hold everywhere.

  2. 9–10 June 2026

    Research tooling and the first system checks

    A metrics study, a research tool work package, an improvement backlog, and the migration into a single folder. The habit of writing a check down before running it starts here.

  3. 10–11 June 2026

    Vision, laws, master plan

    Vision and requirements, the system overview, the design system, the master plan and the per-app fundamentals — plus the first research waves for the network itself. Four days of writing before the architecture existed.

  4. 12 June 2026

    The app contract, identity and the security concept

    The single most consequential day. The app contract fixed what every application must answer; the identity service fixed how tiers and tokens work; the security concept named the threat model and the honest residual risks. Everything after this is an application of these three.

  5. 13–17 June 2026

    The validation nights

    Three dated overnight training runs on the trading side. The working rules plan for these explicitly: a big package is written up, the plan is read back once, the human confirms, then the machine works through the night alone.

  6. 15–19 June 2026

    Cross-connections and the monorepo

    The hand-over contracts between applications, the MCP gateway that pulls every tool to one point, and the consolidation into one repository. The health watch came back green after the cutover, reboot test included.

  7. 20–27 June 2026

    Connectivity, the area model, deep audits

    Connectivity as a core goal, the meta connector, the unification of the UI kit, the area-type model, the core’s continuous loop and the future architecture roadmap — bracketed by two deep audits on 25 June.

  8. 3–4 July 2026

    Agents, exports, tax, trading validation

    A dense two days of contracts: the swappable local model runtime, the autonomy ladder T0–T3 with an emergency stop, read-only bank sync, the tax transport path, the area canon — and the app export contract, which specifies a single application as a self-contained, sellable bundle.

  9. 11–20 July 2026

    Chronicle, constitution, interaction physics

    A chronicle kernel with its own audit core; the project’s essence pinned at constitutional rank in the laws, unchangeable by any session or refactor; and version 4.5 of the spin-physics specification.

  10. 23 July 2026

    The curated public snapshot

    966 files, published as one commit. All rights reserved. Some modules deliberately left out. This website is the second step of the same move: the repository proves it, the site explains it.

  11. 27 July 2026

    The website, and the snapshot moves in

    The first public commit of this site: eleven pages of static HTML, one stylesheet and a baker that uses nothing but the standard library — in English, with a German entry page and the two legal pages in German. The same day the curated extract left its second repository and moved into this one, so every source link resolves inside one public repository and is checked on every build.

  12. 6 August 2026

    Curated down to documents

    966 files of code became 38 documents: the network laws and contracts, the architecture papers and one README per application. An allowlist rather than a blocklist, so a document that turns up later stays out until it is named. The two figures that can no longer be reproduced from outside now say so on every page that carries them.

  13. 7–8 August 2026

    One visual system, the phone, two new watches

    One visual system instead of nine, start pages turned from prose into tables and drawn figures, and a mobile pass after which every page fits the phone it is read on — with a hand-written small map for narrow screens. Two watches came out of real faults: eight rules for the in-app browsers this site cannot choose, and a build that refuses to run while a merge-conflict marker stands anywhere in the tree.

  14. 5–6 September 2026

    Two German house pages, a delivery gate, a domain of its own

    Two German pages joined the menu: /balance/ quotes the essence of the house word for word from the document the rest of this site grows out of, and /schwelle/ gives its ten laws for people, without a name, as plain text that asks, sends and stores nothing. On 6 September a delivery gate began comparing every built file with the live site byte for byte, and the site moved to a domain of its own.

  15. 8 September 2026

    Two small libraries, in public

    Two libraries went public as repositories of their own, beside this one: a governance layer for discovered tools and a toolkit for exact decimal arithmetic. Each carried a licence file from its first commit; on 8 October its placeholder gave way to the full text of an open-source licence.

  16. 10 September 2026

    Not knowing, the thanks, and the private words

    Three German pages joined the site: /deckel/ and /deckel/kinder/, on not having to understand everything — once for adults, once for children — and /dank/, the thanks of a house built by two, a person and an artificial intelligence, given without naming a vendor or a model. The baker gained a fail-closed watch over the house’s private words, which live outside every public repository: a hit stops the site from being written, a missing list stops the build.

  17. 17 September 2026

    Two public profiles, and the Impressum that covers them

    The footer of every page now links the two public profiles of this site, in a navigation of its own beside the legal one, and the Impressum names the profiles its answers also hold for. A profile without an address renders nowhere at all: an Impressum that announces what it cannot name would be worse than one that says nothing.

  18. 8 October 2026

    Wording against the current tree, and the language switch

    The sentences about the code extract were reworded to say exactly what the current tree holds; no figure changed. Both legal pages were brought up to date. In the evening the site’s own audit — every page, both languages, every link forwards and back — found a German menu entry that led to the English twin of its page and a wordmark that led to the English front door; both now stay in the reader’s language.

Where the first six weeks left me

Six weeks, measured

Three of these four cannot be checked against the current tree. The commit count sits in a private repository and is stated as a floor; the Python and the test figures were measured on 27 July 2026, in the code extract that left the current tree on 6 August 2026. Each says so on the page that names its method.

Read the network documents The six figures, each with its method

Now & next

Three steps, no dates I can’t keep

  1. Public snapshot Done — 23 July 2026. 966 files, one curated commit; curated again to 38 documents on 6 August.
  2. Website & first product editions In progress. The export contract for a single sellable application is specified and partly built.
  3. Incorporation Ahead. Germany. The proof came first; the company follows.

Independent project — incorporation ahead. I am opening early conversations with partners and investors.

From project to company