It should be the case that the field that effects size for instance, will effect size throughout the dataset. When the user makes a primary request to the table based on a field, each result itself becomes a query of that subset. This is achieved by writing perl scripts that pass along the required data from the previous script to write a new one. Self replicating scripts pass attributes along to their children without destroying their parents, allowing queries to grow in granularity by attributes of the query passed by it parents. The architectural metaphor serves as a natural point of reference from which the user can read the data.
All data extracted from the query resides within the architectural domain.
The space also infers scale and speaks to the spatial domain of optimum interaction. In this way the archetypal elements of wall, floor, datum and column guides the user through the data intuitively without forcing with a modal interface. The architectural domain is created from spatial archetypes such as floor, roof, wall and datum, and provide a spatial point of reference that distinguishes the data from the set it resides within. By creating a space the user intuitively knows that no data within the dataset resides outside of the space. At human scale primary interaction occurs within the bounding of this element.