Skip to main content

FluxPoints Project

265 words·2 mins
Joel Kotarski
Author
Joel Kotarski

FluxPoints Project
#

A FluxPoint:

  • has an authorative and established identifier that gives it an identity
  • has a physical location that hosts it 1
  • has a structure and set of behaviors that define it, otherwise it is neither active nor static

This last criterion, which defines whether the pattern [virtual] representation (not necessarily the underlying pattern itself) is static also defines whether it can be active introduces the notion of active pattern. In consciousness (the cognitive domain), a static pattern becomes active when cognition is actively operating with that pattern to produce transformations in the pattern itself or other patterns. If the sole purpose of the endpoints project was simply to reflect the products of consciousness as virtual representations, then endpoints would be a proper name; however, the purpose of static pattern engineering is to operate on and transform these patterns — in the transition states they are active patterns. With the tremendous potential of a global network, if the endpoint were designed to release the pattern in a way that allowed it to be activated by bidirectional information flow according to its orientation and exposure then there would be many opportunities for the pattern to become an active pattern (not just for consumer but for creator and aggregators). Thus, we are most interested in the flux through the endpoint — and the sole purpose of the endpoint is to serve as a FluxPoint.

flux


  1. in the first implementation, this will be a hosting location I will provide; however, the infrastructure will be designed from the bottom up that this location can vary for each endpoint ↩︎