# The Toshiba T100 and Pasopia as an exhibit package: inventory (EXHIBIT-MIGRATION.md step 1) Status: 14 Nov 2026, exhibit 0.2.0. The third machine on the new line, after the IME 84 and the NeXT. Written from the tree; where an older document differs, the tree is what this page says. The checklist of [MIGRATION-LESSONS.md](../../docs/framework/MIGRATION-LESSONS.md) was followed step by step; what the T100 taught is its section 15. ## Models, variants, options | What | Where it is defined | |---|---| | Two models (project decision of 14 Nov 2026: the T100 and the Pasopia always go together, one exhibit): `t100`, the export version PA7010U of 1982, and `pasopia`, the Japanese Pasopia PA7010 of 1981 | `rsl.yaml` `models`; `t100/src/machine/models.ts` (`T100_MODEL`, `PASOPIA_MODEL`): the same machine with another system ROM, the Pasopia's own character ROM and the kana legends on its keys | | The model menu | the machine's name in its bar (`toolbar: [model, …]`). In a box the choice goes to the box (the contract's `switch` event, `MachineHost.tsx`), which mounts the model afresh and hands it the packs that model requires; the address follows (`?model=pasopia`). On the machine's own page both stay mounted and the panel switches | | The Pasopia's RSL of the stable line | `simulators/pasopia/rsl.yaml` stays for the stable site's own Pasopia page (site/machines.ts) and is never packed or registered; on the new line there is no exhibit `pasopia`, so no address of the new line changes. RML's registry lists `pasopia` as a model of the machine `t100` (`library/registry/machines.yaml`) | | Variants | none | | Settings | `rsl.yaml` `settings`: processor and memory (information), Fast disk, the on-screen keyboard, the printer with its speed, paper and quality | | Media slots | `rsl.yaml` `slots`: `fd0`, `fd1` (5.25 inch drives), `pack1` (ROM PACK), `pack2` (RAM PACK), `cassette`, `printer` | ## The bar, menu commands, help, key map | What | Where | In the package | |---|---|---| | One bar: core's machine shell toolbar (the machine's name, pause, speed, Reset and Power cycle, Save State, Snapshots, Library…, Machine Settings, Printer…, the rail's tools: Media, the keyboard, sound, copy, "?", full screen) | `t100/src/machine/ui/T100Panel.tsx` (`MachineShell`, with `CalcRail` drawing its tools into the shell's toolbar) | inside the mount element; `toolbar: [model, fullscreen]` tells a box to draw no second control, and the bar's full-screen button asks the box first (the contract's `ask` event) | | Help text (keys and notes) | `rsl.yaml` `help:` (plain English); `rml-ui/tools/rsl.mjs` writes `simulators/t100/help.json`, which the "?" reads (`using100.ts` `T100_HELP`); `using100.test.ts` checks every line against the keymap; `rml/tools/help-pack.mjs` writes the help pack `t100.docs.how-to-use` | data | | Key map (computer keys to the T100's, by position) | `t100/src/machine/keyboard.ts` (`PC_KEY_MAP`) | code (data table) | | The Media panel (drives, the box's disks, the visitor's own copies, cartridges, the cassette deck) | `t100/src/machine/ui/media/drawer100.tsx` | the machine's own panel, inside the mount element | | The printer and its paper | `t100/src/machine/ui/printer/`, `@calculator-sim/printers` | inside the mount element | ## The entry and the host contract `t100/src/entry.ts` (`entry.module: "@calculator-sim/t100/entry"`, contract `rsl-host/1`): the box's adapter over the package's machine module, with two additions of its own. | Method | Served by | `supports` | |---|---|---| | `unmount`, `focus`, `state`, `on` (close, copy, attach, switch, running, ask) | the adapter (`box/src/adapter.ts`) | yes | | `insert(slot, medium)`, `eject(slot)` for `fd0`, `fd1`, `cassette`, `pack1`, `pack2` | the adapter through the machine the shell hands over (`core/src/state/hosted.ts`), `T100Control.insert`; a pack's disk becomes the visitor's copy of it (`DiskMedia.insertPackDisk`) | `insert`, `eject` | | `command("autostart", { steps, ready })` | the adapter, RML §5 steps on `T100Control` (`screenText`, `typeText`, power cycle) | `command` | | `snapshot()`, `restore(bytes)` | the entry: the shell's `.calcstate` of the running machine (`Snapshots.capture(undefined, true)`, `Snapshots.resume`), the diskettes in the drives inside | `snapshot`, `restore` | | `command("variants")`, `command("variant")` | not offered: the T100 has no variants | no | | `resize`, `fullscreen(display)`, `power` | not offered: one screen, the machine fills its element by CSS, and it cannot switch itself off | no | The box's disks for the drives (`fetchAsset({ slot })` for `fd0` and `fd1`) are the machine's library in a box (`t100/src/machine/ui/hosted.ts`): a package has no `disks/` folder. One T100 package a page (`mount.tsx` keeps one mounted panel; the entry refuses a second mount). `snapshot()` and `restore()` are the mounted model's. ## Storage (part of the package's public API) The two models keep what they kept as two simulators: the T100 writes at the host's prefix itself, the Pasopia below `pasopia.` (`MachineModel.storageScope`; pinned by `models.test.ts`), and its states area is `/pasopia/pasopia/states`. So a visitor's Pasopia settings, PACKs and saved states carry over into the model of the one exhibit, and the Disk wallet was one for both machines already. Every key is under the host's prefix (`calculator-sim.` on the stable site, in the museum and in the reference box; `?ns=` in a test). Nothing was renamed for 0.2.0. | Key | Where | Content | |---|---|---| | `t100.prefs.v1`, `t100.speed.v1`, `t100.printer.v1`, `t100.deck.v1`, `t100.run.v1`, the shell's settings | localStorage | the panel's switches, the speed, the printer desk, the deck, the shell's rows | | `t100.drives.v2` (and the older `t100.drives.v1`, read once) | localStorage | which copy is in which drive | | `wallet/disk-copy/`, `wallet/disk-master/`, `wallet/tape/`, `wallet-state` | IndexedDB (core's blob store at the base prefix) | the Disk wallet: the visitor's copies of disks (changed tracks over a master pinned by sha256), their own images, their tapes | | `t100.pack1`, `t100.pack2` | IndexedDB | the ROM PACK and the RAM PACK | | the states area `/t100/t100/states` | the browser's file area (core `openFileArea`) | Save State, Snapshots, autosaves | | `t100.wallet.museum.v1` | localStorage, new in 0.2.0 | the marker and report of the migration below | | `museum.wallet` (`calculator-sim.museum.wallet`) | localStorage, the museum's key | the museum's browser wallet; the migration adds entries to it | ### The wallet: what changed in 0.2.0, and what carries over In a box the wallet of packs is the box's: the museum's **My Wallet** (a member's in the database, a visitor's in this browser, merged into the account at sign-in). The T100's shell has no Wallet… of its own there, so the page has one wallet. The stable site keeps its Wallet… as before. - **Changed copies carry over, unchanged.** A copy is a set of changed tracks over a master pinned by its sha256. A pack's disk started from the museum is that master (the CP/M disk of the old library and of the pack `t100.disk.cpm22` are the same image, sha256 `d2cd250c…2d2f`), so the visitor's newest copy of it goes into the drive and their changes go on (`DiskMedia.insertPackDisk`). No key or record was rewritten. - **Kept library disks are named in My Wallet, once per browser** (`media/packWallet.ts` `migrateToMuseumWallet`): for every copy whose master is the image of a pack the box offers, the pack's id and version are added to the museum's browser wallet. Its gate is `packWallet.test.ts`. - **What cannot carry over into My Wallet, and stays in the Disk wallet** (reachable from the machine's Media panel, "Your disks", as before): copies of a library disk that is no RML pack of this box (T-DISK BASIC 1.0, the Personal/Home/Entertainment disk and the rest of the older library, until they are packs); the visitor's own images and blank disks; cassettes. My Wallet holds packs, never bytes. The migration's report (`t100.wallet.museum.v1`) counts them. - **A started pack that is not in the manifest's `requires`** (any other library pack the museum inserts) runs and keeps its copy, but after a reload its drive comes back empty: the machine can fetch a master again only for the packs of its own library (the manifest's slot packs). ## What it needs from its page (`needs`) Nothing beyond the page policy: no WebAssembly, no worker, no range reads. Sound is Web Audio from the page's thread. Storage through core (`createStorage`, the blob store, the file area). React and core come from the shared layer `box-runtime` 1.4.0, which this package did not change. ## Files fetched at run time | File | From | How | |---|---|---| | the Pasopia's system ROM and character ROM (model `pasopia` only) | `t100.rom.pasopia-system` 1.0.0 and `t100.rom.pasopia-chargen` 1.0.0, **public**; without the character ROM the emulator draws its own JIS X 0201 set | by path, as the T100's ROM | | the system ROM, one 32 KB image (or the four 8 KB chips; model `t100` only) | the pack `t100.rom.system` 1.0.2, **public** | by path below the asset base; the adapter maps it to `fetchAsset({ pack, file })`, checked against the manifest's pin | | the disks of the box's library | `t100.disk.cpm22` 1.0.2 (`fd0`), `t100.disk.wordstar-3.0` 1.0.2 (`fd1`), **public** | `fetchAsset({ slot })` lists them, `fetchAsset({ pack, file })` hands one over | | a disk the museum's Software applet starts | any pack the visitor may see | `insert(slot, medium)` | The character generator is drawn in code (no T100 character ROM dump exists). ## Tiers (decided before packaging, MIGRATION-LESSONS §4) Project decision of 14 Nov 2026: the T100, the Pasopia and all their packs are public. (Until then the ROM pack was gated, #1090, and this page did not name it: a document of the exhibit is a public answer, MIGRATION-LESSONS §15.) | Pack | Tier | Decision | |---|---|---| | `t100.rom.pasopia-system` 1.0.0, `t100.rom.pasopia-chargen` 1.0.0 (new) | public | project decision of 14 Nov 2026; the rights are Toshiba's (and Microsoft's for T-BASIC), not ours | | `t100.rom.system` 1.0.2 | public | project decision of 14 Nov 2026 (was gated, #1090): every site hands the T100 its ROM; the rights are Toshiba's and Microsoft's, not ours | | `t100.disk.cpm22` 1.0.2, `t100.disk.wordstar-3.0` 1.0.2, `t100.bundle.cpm22-wordstar` 1.0.2 | public | #1116, 13 Nov 2026 | | the exhibit | public | as before | ## Components (the component rule) `rsl.yaml` `technical.components`, each with its record in `components//rpk.yaml`: | Part | Component | Clean-room | Since | |---|---|---|---| | Z80A and the IM 2 daisy chain | `chip.z80` 1.0.0 | true | 14 Nov 2026 | | Z80 CTC | `chip.z80-ctc` 1.0.0 | true | 14 Nov 2026 | | Z80 PIO | `chip.z80-pio` 1.0.0 | true | 14 Nov 2026 | | three 8255A | `chip.i8255` 1.0.0 | true | 14 Nov 2026 | | µPD765 | `chip.upd765` 1.1.0 | true | 14 Nov 2026 | | two 5.25 inch drives, the medium interface, the sector image | `periph.floppy-drive` 1.1.0 (the optional `readFlux` beside the sector methods) | true | 14 Nov 2026 | | the drive unit's data separator; flux-level images (MFI, KryoFlux streams, SCP) as media | `chip.data-separator` 1.0.0, `periph.flux-medium` 1.0.0 (#1223) | as their records say | 14 Nov 2026 | | HD46505S | `chip.mc6845` 1.1.0, variant `hd46505s` (#1199; the saved state's format 2, format 1 still resumes) | true | 15 Nov 2026 | | memory and bank switch, display interface, keyboard, speaker, printer port, cassette, PACK slots, RS-232C | the T100's own parts (`own:`) | (the package's, `source.clean-room: true`) | | The printers on the cable are `@calculator-sim/printers`, a shared package that is no component yet. ## Gates `technical.gates` in `rsl.yaml`: | Gate | Kind | Media | |---|---|---| | `unit`: `npm test -w @calculator-sim/t100` | unit | the ROM and the three Toshiba disks in the package's own tree | | `fdc`, `floppy-drive`, `z80`, `z80-ctc`, `z80-pio`, `i8255`: the components' own tests | unit | none | | `fdc-board`, `state`, `wallet` | unit | none | | `boot`, `disk`: T-BASIC to Ok; CP/M to A> and DIR | boot | in the tree | | `package-e2e`: the package in the reference box at desk 1440, iPad 1180 and 820, phone 430 | e2e, target package | the ROM and the CP/M disk from the media store (a media runner in CI) | | `t100-e2e`, `shell-e2e`: the machine's own page | e2e | in the tree | | `v2-acceptance`: the museum v2 cases `t100`, `library-t100`, `software-t100`, `wallet` | e2e, target museum | the library's media store | ## What the e2e rely on The test ids `t100-screen`, `t100-canvas`, `t100-screen-text` (the screen's text), `t100-keyboard`, `t100-osk-`, the shell's `t100-shell-*`; `#box[data-box-state]` of the reference box; the entry's `testHook()` (the handle and the running machine's shell parts), imported by the module's URL in the page; the URL parameter `?ns` (the box). The older e2e of the machine's own page also read `window.__t100Shells`. ## Module-level state `t100/src/machine/ui/mount.tsx` keeps the one mounted panel (`shown`); `t100/src/machine/ui/hosted.ts` keeps the box's library and the running machines' shell parts while an exhibit is mounted; the entry clears both at unmount. ## Reach outside the package `t100/src/machine/ui/profile.ts` imports `simulators/t100/profile.json` and `using100.ts` imports `simulators/t100/help.json`: generated data of the exhibit's own RSL, and the package's only imports from outside its folder besides core and the components. Since 0.2.2 the Pasopia's profile is the exhibit's own, seen as the model `pasopia` (its id and storage scope, its title, its library, the machine's name in the settings' help), and no longer read from `simulators/pasopia/`; a test holds it equal to the profile the earlier site's RSL gives, so the go-live gate finds no reach outside. ## Open points - #1098: path B (our own IPL and CP/M BIOS) is no longer needed for a site, since every site hands out the ROM; the idea stays open. - The core (`t100/src/machine`) shares its folder with the page (`ui/`, `runLoop.ts`), so the go-live gate's build-target check finds browser interfaces in "the core"; moving `ui/` beside it is a mechanical step of its own. - The rest of the T100's older library (T-DISK BASIC, the tapes, the Pasopia's programs) as RML packs, so that those kept disks can stand in My Wallet too.