If you're capable and that's what you see, why not integrate it into a conceptual model and then a computational model and then write the code for it? When I say its possible I mean to say that, once you have the right model, you can write any code you want to make it a reality. The capability and hardware are already here today and more is on the horizon. One of the stacks I have lying about are spec sheets and white papers regarding Nvidia's GPU microarchitectures, HSA architectures, latency white papers, etc. I was literally waiting on their new microarchitecture to experiment with some new concepts. Future chips on the horizon make me :) deeply. So, unlike the past, the compute power is there and more is coming quite soon.

I scanned through 194-209. Excellent analysis and construction of a framework. I have hundreds of pages of this kind of analysis that I performed in the initial stages of my inquiry. This is excellent work. The thing is, you need to begin constructing models and theories from it. Start prototyping code and see how it fits together with other subsystems and aspects of your architecture and theory. You really just have to get in there and start stringing together code and start dissecting and trashing things that don't fit and locking in things that do fit.

My perspective is that the paper highlights a fundamental first step of how you approach AGI : By reasoning through your thought process, cognitive functions, and interaction in the world.

I would love to take you up on that offer and will when I return to the bay area. I always enjoy a good conversation on these matters. I'll take tea :)

For now, I'm in a bit of an undisclosed location doing dev. I Decided it would be best to get away from the high noise level in the valley while I focus on my R&D effort.