0. Introduction Because software on a computer system is normally designed and developed by a number of people and evolves in a "piecemeal" fashion over years, there has classically been a tendency toward systems with a low level of consistency between the parts. One finds that the functions we use split between what the user views as independent programs (Schneiderman[1982]). We feel that the understanding of many kinds of computer applications has progressed to a point where we can now address the integration of the applications. We would like a family of applications to appear to the user as a set of facilities applying similar operations to different data domains, as opposed to monolithic appplication programs each with its own conventions and database. What do we mean by "integration"? We forward that integration is two different but interdependent qualities, which we will call internal consistency and external consistency. [insert Jim's definition paragraphs here]. 1. Structure We have embarked upon an experiment to produce a system integrated in the sense of both internal and external consistency. The basis for internal consistency is a shared database system and package for interaction of applications. The basis for external consistency is a common high-level paradigm for the user interface and a package to facilitate the use of that paradigm. [What we've got: Cedar, Cypress, Squirrel, Walnut, Hickory] [Other similar work, how we differ in goals] Êk˜head1šÏa˜Ibody˜ìLšœ}Ïe œü˜„Lšœžœžœ˜¯Lšœ*˜*Kš ˜ L˜øL˜;L˜,—J˜—…—Î?