Skip to content

History / Architecture

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
  • News + Architecture + tracker: DC-083 closed, security posture written down The wire audit found two gaps -- a peer's declared geometry reached a precondition, and a count bound that was per-number rather than per-product. Both fixed and fuzzed; the Architecture page now states what is exposed, what is refused, and what is deliberately absent.

    @Pummelchen Pummelchen committed Sep 16, 2026
  • Tracker: Swift 6.4 on Xcode 27 is the language standard (DC-014) DC-014 closes: the standard is recorded in AGENTS.md, CONTRIBUTING.md, the Testbed page and the Architecture stack row, and it supersedes the earlier 6.3.3 target — the superseded line is written down rather than erased, so a later reader can tell a decision change from an inconsistency. DC-015 is added for the language-feature register. It has to be measured from the real manifest, not copied from a release note, which is the same rule this project applies to every other number. Testbed states the toolchain once, so a node check has something to compare against: Apple Swift 6.4 (swiftlang-6.4.0.34.1), Xcode 27.0 with the Metal toolchain, and swift-tools-version:6.4 in the manifest once it exists.

    @Pummelchen Pummelchen committed Sep 15, 2026
  • Tracker: the scaffolding landed, and the development link is 1 Gbit Ethernet DC-003 closes — .gitignore, AGENTS.md, CONTRIBUTING.md, SECURITY.md, the issue and pull-request templates, twelve repository topics and the seven phase milestones on GitHub. DC-004 is in progress: the Markdown link gate is live and tested, the Swift gates land with the code. DC-002 is in progress with its remainder named rather than dropped — the `Shard` codename, `Macs Minis/Studio's`, and the Qwen target-version mismatch. Recorded because it changes how M2 and M3 numbers must be read: the farm's development link is 1 Gbit Ethernet for now. That is a developer limitation, not the design target, and it appears on the Testbed page, in the Architecture transport section and in R4/Q5 instead of the README, whose transports remain what the design assumes. The all-reduce payload is ~4 KB per MoE layer, so the link shows up as latency before bandwidth. Also parked: the sister project's SECURITY.md points private vulnerability reporting at github.com/drumih/turbo-fieldfare rather than at TinyTitan — found while writing this repository's policy, belongs upstream (DC-085). The closed record gains DC-003 and the three README fixes, with the remainder of DC-002 still open above.

    @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