\yskip
The world bombards our senses with data, much more than we can process in detail in real time; yet we can't live in a hundred times real time. We survive by ignoring most of that data, or, more precisely, by knowing (almost immediately deciding) what can be ignored. We maintain a set of expectations, against which the incoming torrent is matched. Almost all of it will match those expectations, and we then need merely process the unexpected inputs, the surprising observations. We reserve our computing for those opportunities which promise us genuine new facts, rather than reconfirmation of known ones.” -- COG3. listed under https://www.saildart.org/[AM,DBL]/
We still need to figure out which files compose EURISKO.
More significant* is that his work at Xerox is likely unavailable due to how Interlisp-D worked. When I started to work for Doug on Cyc he had a three-year old band (checkpointed image) he'd been working on continuously on the Dolphin in his PARC office. As you can imagine it was full of lost fossils in memory with completely unpredictable effects on the code. I'm certain that memory image has been gone fro any backup tape for almost 40 years.
Even though we'd overlapped at PARC, when I got to MCC (Cyc), for technical reasons I refused to even use the D machine version and started out with a blank zemacs buffer on a symbolics machine. One major technical reason is that you actually had source code which could be loaded into a fresh memory image. I made sure from the start that always worked.
* what makes it significant, to me, is the technical/cultural implication of the PARC "band" model of Smalltalk and Interlisp-D. I don't mean the early Cyc code base is particularly interesting in and of itself. Interlisp on the -10 usually used files of source code, as you referenced and you would be used to from CommonLisp.
I've always been fascinated by what it could accomplish on such limited resources. It seems possible that the tech would be useful even today.
