# The T100's own code: clean-room record Status (14 Nov 2026, exhibit 0.2.0): **the machine's own code is `clean-room: true`**, and so is every component it pins. No file of the package is listed as written with another emulator's source read. ## The rule the package was written under `t100/SOURCES.md` lists every source, labelled **spec** (manuals, data sheets, magazine articles: what the machine does) or **implementation** (someone else's emulator or firmware code). The code was written from spec sources only: - Toshiba's T100 Technical Reference (Toshiba Australia, 1985), the Maintenance Manual PAD8120-1, the Owner's Manuals and the Programmer's Reference PAD8111-1; - the ASCII Technical Bank book on the Pasopia (*Pasopia no naibu kouzou*, 1983), its hardware chapter 1 and the opening of §5-3 only: the chapters on how T-BASIC works inside were not used; - the Zilog Z80, Z80 CTC and Z80 PIO documents, Intel's 8255A, Hitachi's HD46505S and NEC's µPD765 data sheets; - the C. Itoh 8510A manual and the printers package's own sources for the printer port; - Creative Computing, November 1983: the review and Ahl's benchmark. **Not read:** MAME's `pasopia*.cpp` and `bus/pasopia`, EmuPIA and the Common Source Code Project, the `beijingduckx` `*.z80` listings. **The ROM was run, never disassembled**; where a fact came from observing the running ROM, `t100/SOURCES.md` says so ("Observed on the running ROM"). ## Tests against other models The Z80 was verified against test data only: the SingleStepTests Z80 cases (MIT, JSON) and ZEXDOC/ZEXALL run as programs. MAME's pasopia driver was foreseen as a black-box oracle (a trace comparison, never its source). The timing of the T100's WAIT state is fitted to Ahl's benchmark as owners measured it (68 to 72 s; Creative Computing printed 1:09). ## The components Each has its own record in `components//rpk.yaml` (`clean-room-record`), recorded on 14 Nov 2026 when the part left this package: `chip.z80`, `chip.z80-ctc`, `chip.z80-pio`, `chip.i8255`, `chip.upd765`, `periph.floppy-drive`. Each was moved unchanged in behaviour; the medium interface and the drive of `periph.floppy-drive` were written for that package from the same model. The repository's other 765-class controllers (`chip.i82077`, `ibmpc/src/devices/fdc765.ts`) and CRTC models were not used for them. ## What follows - `node rml-ui/tools/rsl-pack.mjs t100 --source` may write the T100's RSLc (the kit with its source). - The vendor data sheets named above are not in the media store yet (a desideratum of the T100's library); the components' `docs` cite the two documents the library holds, the Technical Reference and the ASCII book, for how the T100 uses each chip.