Appropriate Software
Contexts

Each context comprises a "world" (or domain) where productive events take place ("everything is production"). Together, the contexts form a layered stack. Things further up are essentially more specific (more particular) than things further down. Each context is distinguished by its recording devices.

Analysis (and Movements)

Conception (and Naming)

Time (and Events)

Notes

How are these contexts related?

The lower contexts on the page are broader and condition the higher ones. Eternity always conditions the new events which begin to comprise it ("everything is an event"). More specifically, concepts are conceived as events ("ideas will not keep, something must be done about them"). In particular, analysis obtains syntheses by tracing over the concepts it possesses. Similarly, development only proceeds after marking out both how production may occur and which purposes might be supported. Indeed, only after a period of analysis and development can any given purpose be satisfied. In this way, activated networks can be generated, and intertwined to fashion desirable worlds.

Conversely, the higher contexts on the page are narrower and are based on the lower ones ("everything is a process"). The narrowest context is that of our various closed-up "little worlds" (a world of worlds). Each is situated within more open and extensive multiplicities which are used to form them, just as novels fashion worlds out of cities (worlds of association). Constituent machinery is provided only after a passage of production, which continues to envelop the machines after their consummation has begun (worlds of development). All this continues on a material surface of analysis that is conceived and repeated throughout as an event (a world of time).

Why this particular series of contexts?

Each context is individuated by the kind of recording devices it involves. Like stones in a stream, events accumulate simply in time. Similarly, concepts (and their names) are collected in books and in brains. And then analysis marks concepts and their names with other concepts and other names.

Roughly speaking, development casts its object machines as the recording devices of its improvements. Associations position their component machines on the surface of general society ('a socius of inscription where the essential thing is to mark or to be marked') as seems necessary to obtain a given level of provision. And, as they see fit, worlds inscribe their narratives upon the associations they appropriate.

Who benefits from recording these contexts?

The value of recording our contexts lies in mapping our own little world, a changing world of moving between other changing worlds. We benefit by having an invariant diagram, not of the entire territory which we will encounter, but of encountering and operating on territory as such. Hence we have accomplished something of great value: we have constituted a new territory.

Whilst civilisation runs on software, our software-based worlds run on concepts. Without understanding the concept from the standpoint of the event, we are reduced to general confusion, and will be excluded from many of the most joyful, desirable, and continuous lines of development.

Where is information about the contextualised work?

Our work is described on the Approach and the Services pages. You can also browse the Projects page, where our development work is presented.