expand_less Data and scape engine operators. 
Data engine creates forms of memory specificed by a "word-spec" 
The data engine is the "memory" of the ceptr VM, it's just that there are lots of types of memory, not just RAM accessible by word-sized int.  Instead the machine "word" can be semantic structures, stored natively.
Sort/Limit are kinds of meta-geometry functions on scapes
Geometry functions from spreadsheet, (structural and contextual): existance, isometric maps, next/prev,  orderded, bounded, linearity, rotational, continuous vs stepped, tree, etc..
 
Find: search on data that's allready scaped so it can be retrieved via random access
Match: requires iteration and processing.
 
We took a long walk and explored the issues of "variable equality" of scapes. What it would mean to provide "=" functions that may operate differently at different "resolutions" of scapes. Think of different zoom levels on a map where you'd say two people live in the "same" place at the level of country/bioregion/city/neighborhood/street etc. based on the level of resolution you're working with.
 
In hindsight, it seems obvious that if scapes are used for sense-making and coherence, that different resolutions as well as different modes of comparison are necessary.
Wheeled by Wagn v. 0.15.6