Skip to content

History / Roadmap

Revisions

  • Wiki review: remove the dependency framing; flag the plan pages as stale Removed every non-historical 'sister project' reference (Home, Glossary, two Architecture rows, the Roadmap objective, Testbed's dependency section) and the two tracker rows that presupposed adopting another project's code - DC-085 and DC-123. ttd is built from scratch and is MIT, so there is no upstream to track and no code to adopt. Flagged rather than rewritten: Roadmap.md, the milestone pages and most tracker rows still describe the retired DatacenterEngine plan, and Architecture.md's sharding section says expert parallelism while what shipped divides layers. That is a planning decision, not a cleanup.

    @Pummelchen Pummelchen committed Sep 19, 2026
  • wiki: rewrite the project tracker to the task-table standard

    @Pummelchen Pummelchen committed Sep 18, 2026
  • Roadmap and tracker: D12 is decided (D31), so the open list is the tok/s measurements

    @Pummelchen Pummelchen committed Sep 16, 2026
  • Tracker and Roadmap: DC-108 and DC-109 are closed, so stop calling them open Both were named as what M1 and M2 leave open. The install verifies from Python now and the sharded generation CLI exists; the Roadmap says what actually remains, which is D12 and the tok/s measurements.

    @Pummelchen Pummelchen committed Sep 16, 2026
  • News + tracker + Roadmap: all four machines run one forward (D27), M3 under way Full mesh, every node bit-identical to the single-node trace (58518422914cfe2b...). That is M3's functional half; its 3x throughput gate needs a quiet farm and a sharded generation CLI (DC-109).

    @Pummelchen Pummelchen committed Sep 16, 2026
  • News + tracker + Roadmap + Testbed: M2's gate passed on the real 35B model Same digest as the single-node baseline (b0d382dbabf36df0...), 83 tensors and 40 discrete decisions checked by trace_diff on both machines. Phase table Done, new M2 milestone row. DC-045 closed; DC-109 opened for a sharded generation CLI, which the tok/s gates need.

    @Pummelchen Pummelchen committed Sep 16, 2026
  • Roadmap: P3 (M2) is under way, not unstarted

    @Pummelchen Pummelchen committed Sep 16, 2026
  • M1's gate passes: re-established after D15/D16, three stale claims corrected Correctness re-verified against a freshly re-run contract (identical digests, same as the original gate run). Generation 0.108 tok/s cached / 0.0374 uncached, identical tokens. Peak memory 348.6 MB. DC-108 opened for the install-path contract gap; the checkpoint contract step's swap incident recorded.

    @Pummelchen Pummelchen committed Sep 16, 2026
  • Tracker: DC-104 -- M0 is complete, and six documents said otherwise docs/m0-gate.md records status: passing on Qwen/Qwen3.5-2B with 40,683,520 bytes of trace data identical to the contract and every discrete decision matching the reference. Every M0 task is Done, so the answer to "what is next for M0" is nothing -- and the work became correcting my own status rewrite, which called it "fixture scale" without reading the gate doc. The correction also names the 2B-vs-~1B deviation and the renegotiated oracle half.

    @Pummelchen Pummelchen committed Sep 16, 2026
  • Wiki: the status claim corrected on Home and Roadmap, and it now names the toolchain Home said "no source code, no build system and no release" -- the extreme AGENTS.md had already recorded as wrong. Roadmap said "nothing on this page is built yet ... design phase". Both now state what is measured: Swift 6.4 / Xcode 27, clean build, 105 Swift tests, 163 stdlib Python tests in CI; M0 met at fixture scale, M1 run on the real model with its gate open; no releases, no tags. DC-102 records it, and the trap entry now requires any status claim to name the toolchain.

    @Pummelchen Pummelchen committed Sep 16, 2026
  • Tracker: D1-D7 recorded, M0 staged, the model verified before it is built on DC-020 closes with D1 and DC-002 closes with D7. M0 becomes three stages with one variable each, because D1's model is a chunked Gated DeltaNet rather than the conventional transformer the milestone was designed around (R12) — and because the 4-bit path should not land in the same step as the first bit-exactness proof. The Target models page and the Roadmap carry the same staging, and the decisions themselves live in the repository at docs/m0-decisions.md so the reasoning survives outside this wiki. What is still missing from the Gated DeltaNet contract — the intra-chunk algorithm, the conv boundary handling, the l2norm reduction, the full-attention module — is listed explicitly rather than left to be guessed.

    @Pummelchen Pummelchen committed Sep 15, 2026
  • Bootstrap the wiki: project pages and the task tracker The wiki held a one-line Home stub. It now carries the project's plan, its status and its design, so that no later commit has to invent them. Pages: - Home — what the project is, the expert-parallel thesis, the milestones at a glance, non-goals, the sister project and the licence. - Roadmap — P0..P6 (M0..M5) with the objective, the deliverables and the gate of each phase; the bit-identity gate at M2 is named as the real one, and the rule that a gate is renegotiated openly, never quietly. - Project Tracker — the tracker the repository did not have: 51 stable DC-nnn tasks across seven phases, a phase/status board, nine risks and traps, seven open questions, the closed record and a parked list. DC-001 (this bootstrap) and DC-082 (the README/wiki/tracker sync rule) are the only two closed items; no source code exists yet. - Architecture — the design as written: expert versus pipeline parallelism, the four invariants (bit-reproducibility, discrete decisions, faithful ports, transcode-don't-requantize), the role-based IR and thin importers, the shard policy, transport, and the stack. - Testbed — the target configurations, what a node must provide, a readiness checklist and the sister project as a dependency. - Glossary — model, distributed, runtime and project terms. Also the sidebar and footer navigation, in the style of the sister project's wiki. Deliberately absent: host names, addresses, credentials and any measured number. Nothing in the repository runs yet, so every page states that the claim is design intent, and the risks say which ones are unproven.

    @Pummelchen Pummelchen committed Sep 15, 2026