Dated, not narrated

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.

Where that left me

Six weeks, measured

• 10applications→How the ten were counted
• 2,600+commits in the private working repository behind this snapshot→How the commits were counted, and why this one is a floor
• ~100,000lines of Python, across 632 files→How the lines and files were counted, and when
• 2,667test functions in 309 files→How the test functions were counted, and when

Three of these four can no longer be checked from outside. 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 was withdrawn on 6 August 2026. Each says so on the page that names 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. 2 Website & first product editions In progress. The export contract for a single sellable application is specified and partly built.
3. 3 Incorporation Ahead. Germany. The proof came first; the company follows.