One session for every machine, verified as far as it was.
A printer, a router, a phone and a power supply are all devices with channels. A driver speaks one channel's protocol, and the catalog says how far each driver was tested.
Case study · the drivers catalog
57 drivers, none past loopback yet.
The run read packages/domain/world/drivers.js, the one list of drivers. A driver at loopback passes its tests against a software fake of its protocol. bench and hardware each need a report of the steps done on a real machine, and there is none yet. So no driver says more.
- implemented and verified to loopback
- 44
- implemented, at none: screen capture, USB webcams, microphones
- 3
- planned, with no code yet
- 10
- at bench or hardware
- 0
cloud://home/user-commandagi/case-studies/drivers/catalog.call.jsonRun runs/20261104t163739z-catalogTool drivers.js, the catalogRan on This computer (dell-gb10-1)When When there is no machine
A simulator for each format, never the hardware.
In a simulated run, a channel's driver is a simulator of its format. It implements the same session as a driver, never opens a real port, and its records say sim. A simulated result never counts as physical evidence.
- simulators: G-code, servo bus, state, camera, firmware, servo hub, computer and verbs
- 8
- implemented
- 8 of 8
cloud://home/user-commandagi/case-studies/drivers/catalog.call.jsonRun runs/20261104t163739z-catalogWhen Bring a machine.
Pick its driver from the catalog. Run it in simulation first, then commission it on the bench.