Give experience a consequence.

An encounter should change an expectation

The early architecture documents describe a loop: observe, predict, attempt an action, observe its consequence, compare that outcome with the prediction, and use the error or teaching to revise an expectation.

The embodied design includes vision, proprioception and touch. The memory design connects different kinds of records while preserving where they came from and how they were corrected. Together, these ideas give the project a practical test: can a past encounter improve a later choice?

A design is a direction

These documents set out an intended architecture. They are not evidence that every proposed subsystem was already working together, or that Owen could discover general physical laws. Later chapters examine particular implementations and their controls.

The date is approximate. It follows the surviving files’ modification dates and version sequence, rather than an explicit event date inside the reports.