• This will be an invitation only beta, which means:
  • Some colleagues and friends will be asked directly to join – please feel no obligation but your feedback will be greatly appreciated if you can assist.
  • Throughout the last few years, I have been looking at interesting individuals who may be interested in patternsmithing and Thingk persistence – you will be receiving a hand-crafted email as a personal invitation – once again, no obligation please – only do this if it brings you value but if you do your feedback is greatly appreciated.
  • As expressed on this blog, if interested feel free to contact me at the contact form http://xri.net/=joel.kotarski and I will be able to accomodate you.  Also if you think you know someone who would be interested from the category above, please contact me here as well.
  • We’ll probably have limited invitations to spread around among private beta users – these will probably only be on a request-only basis, however, to control capacity initially.
• For those in town, we will most likely host an in-person meeting where we will go over some details about the site and what is being accomplished – for out-of-towners we may also host a teleconference as a separate event.
• Since we will be testing privacy and security (with potential bugs to be found), I ask that you put the kind of ideas you may spontaneously work on but not your actual work and certainly not anything you would consider intellectual property at this point.  Much of the data from the private beta will be wiped clean on launch so that we can fully test; however, I am planning to make an easy mechanism to tag content you wish to transition over to the full system – also, I will be soliciting feedback on making this process as painless as possible for those generally interested in getting value from the work they do in beta testing.
• As always, being asked to participate should not imply obligation to participate, and participating should not imply obligation to give detailed feedback.  Anything you do is greatly appreciated and will be rewarded in some manner.

Polymeric finally admits that the user interface should get out of the way of the user – that the best expression comes out of the user if they are guided and prompted along but in a non-intrusive way.  At the core of Polymeric is the ContextProvider – the context is used to provide suggested components, prompted questions, and directions for exploration.  The ContextProvider works at three levels : what the user has done before (what Thin(g)(k)s* they have created, what Thin(g)(k)s have inspired them, as well as the components of each), what they are doing right now (the current word they may be trying to type, what question they are answering), and where the engine can infer they are going (via pattern matching of current text we can infer related directions for exploration).

*: Thin(g)(k)s means Things, Thinks, and/or Thingks (or any combination thereof).

At the center is the Polyermic edit box – a text editor (with optional rich editing functionality but this is hidden away and only appears under certain circumstances) which is fed by and feeds the ContextProvider.  At the moment, we are planning to have users use WikiWord format to denote Thin(g)(k)s across the entire site – it is just a format that works well.  The ContextProvider loads several layers of information, but the first layer of information is a static list of WikiWords (that is, pointers to Thin(g)(k)s) which the user has had contact with (either by creating, being inspired by, or using as components in their other creations), primed for usage in this context.  Let’s look at the post I am writing currently on this blog – four WikiWords are at play and only three are Thin(g)(k)s.  The Thin(g)(k) WikiWords are : “ContextProvider”, “Polymeric”, and “Thin(g)(k)”.  I’ve repeatedly typed all three manually throughout this post, but if I was editing this post in Polymeric in the actual Thingk.com web site, these words would have been suggested to me.  This due to the first and second layers of information: “Polymeric” and “Thin(g)(k)” would have been loaded in context in the first layer (as my creations and/or creations I collaborated with others on), but the moment “Polymeric” was suggested to me and I picked it, the ContextProvider would have loaded all the components of the Thingk “Polyermic” into context, including (but not limited to) the “ContextProvider”.  And one of the other Thin(g)(k)s that would have been loaded is a reference to a project which inspired context suggestions and must be payed homage to: GoogleSuggest.  GoogleSuggest inspired many people as an autocomplete mechanism to use Ajax to give suggestions based on user inputs, but this is in the context of one singular input, whereas we will suggest individual parts of a larger body of text – this is of course nothing revolutionary – you can see the same feature on your cell phone.  The difference here is that a Thingk, behind the scenes, will be a RDF resource that follows the ontology defined for Thin(g)(k)s at the PatternSmithing Alliance, including linkages between Thin(g)(k)s at the RDF level.  Like most semantic web applications, we would never dream of having our users manually hand-type RDF; however, by choosing one of these WikiWords, the text of the Thin(g)(k) is not the only persisted but also the relationship/link to the Thin(g)(k) itself.  This was the crucial problem to solve – to give the user an intuitive mechanism for forging these relationships.

The Polymeric user interface has an additional set of features which are fed by the ContextProvider.  Several of these are based off the usage of WikiWords – for instance, it is possible to use a WikiWord for a Thin(g)(k) not currently on the site (for instance, my mention of GoogleSuggest would have started the process of creating an authorative reference on the site to Google’s project, pending Google’s permission to create such a thing) as well as suggestions to the user to turn a repeated pattern of text into a WikiWord and therefore a Thin(g)(k) on the site.  Additionally, the outer borders of the user interface will have bits of context floating in based on what is going on inside the editing area: a cloud of moving WikiWords that can be grabbed and dragged onto the editing surface that changes over time, and prompting questions that fade in and fade out  to guide the user to starting or evolving their work.

Once we open up the private beta, we will be soliciting feedback from some of you, so please contact me at http://xri.net/=joel.kotarski if interested.

As I continue to work on the upcoming volume to be published, one of the opening chapters that has emerged concerns seeing the world in terms of patterns.  This thesis (that the world can be perceived, modeled, and treated as an intermeshed collection of patterns) is central to establishing the entire field of static pattern engineering as well as orienting individuals toward the activities (patternsmithing, pattern engineering, and architecting) that arise from it.

One of the problems I have struggled with is that the term Pattern has a lot of connotations surrounding it and most of them are seemingly purposefully and annoyingly vague.  For current examples across the web, see the following google query.  In a future post, I will reveal the formalization of the term pattern that underlies static pattern engineering (intuitive hints have been spread throughout this blog) and  with this formal definition I will give plenty of exercises of seeing the world (including that which is formed, that which is forming, and that which is yet to be formed) in terms of patterns.

Once patterns are defined and examples are identified, it will be important to introduce how forces are operating on this pattern and the terms static pattern, dynamic pattern, and active pattern will come into focus.  At that point, it is hoped it will become clear how and why individuals work on creating, transforming, and operating on patterns in their daily lives and why we need a field and set of activities for working with these patterns directly.  Once this post is published, I’d welcome feedback on it, as I am hoping this will be an intriguing opening for the book and ultimately an introduction to the field for many.

Also, on another note, as a reader please begin registering your interest levels (via the polls available) which topics you would be most interested in reading next, as the frequency of posting on this blog is fairly low, I want to make sure you have a voice and that I am made aware of what you are looking to discover.  As always, contact me at http://xri.net/=joel.kotarski with any questions or feedback.

• The PatternSmithing Alliance (http://patternsmithing.com/) is being established as a centralized organizing and guiding body for the core activities, knowledge, and applications of static pattern engineering technologies.  This site and my activities (including the book under construction) will be considered contributions to the body of work of the Alliance.
• The “ThingK” company (I am finalizing the company name so will just call it that for now) will work on several products and services that not only apply static pattern engineering technologies but also advance the field as a whole.  After research and development, I’ve seen that several viable technologies exist that can enhance people’s lives as well as the field itself – a commercial vehicle will serve the projects well throughout their lifetime to keep their growth and maintenance sustainable.
• The research and development activities on Static Pattern Engineering will still continue by interested members of the Alliance, either as a voluntary effort, projects commissioned/funded by the Alliance or government grants, and/or activities commissioned under the commercial ventures of the “ThingK” company or other participating partners.  This site will continue to track these activities that fall under the first two categories, whilst the commercial aspects will continue to drift away toward channels created by the “ThingK” company.

I wanted to make this sort of a last post that outlines the whole field (as it stands today), because  many of these aspects grew out of this research and development activity.  This blog’s posts, as well as many other posts related to these separate aspects of the field on other sites (where I’ve been busy recently), are now syndicated together at the PatternSmithing Alliance blogs at http://blogs.patternsmithing.com/.   If you are interested in monitoring the entire field and all activities —  not just the research and development aspects, I encourage you to relocate your attention there – these posts will continue to make their way there.

Also, if you are interested in the body of knowledge surrounding Static Pattern Engineering, while waiting for the publication of the first volume, you can visit the PatternSmithing Alliance wiki (link withheld until it fills up more – just created recently) which will continue to reflect the growing body of knowledge and technologies.  From the research and development side, at times the blog will preceed the wiki in terms of knowledge while at other times the wiki will preceed the blog in terms of knowledge.

To begin involvement in the activities of the field, you are encouraged to submit your information at http://patternsmithing.com/.

Finally, I want to briefly discuss the products and services of the “ThingK” company, which started as research projects here and are now in active development:

• The thingk.com web site is the site alluded to earlier surrounding the notion of ‘thingk’ as expressing a more easily graspable term for ’static pattern’.  This will be a free community web site, with a revenue model based on enhancements, that allows any person to begin working with the core tenets of static pattern engineering without any knowledge of the underlying science, research, or activities surrounding it – this was always one of my goals from the beginning.  The PatternSmithing Alliance will recommend the core standards this site will use so that user’s content will always be reusable, expandable, and exportable by them for collaboration with non-commercial interests.  This site is very central to strategy for all of the groups:
  • The research and development activities of the PatternSmithing Alliance (which this site represents) will be interested in expanding the technology and studying how user content and collaboration progresses as case studies in the state of the art of the field.
  • After creators (the users of the site) begin to see the power of persisting and ultimately creating their Thingks, the PatternSmithing Alliance may be a natural avenue for them to continue their progression into learning about the core of the field, first by simple PatternSmithing activities, and then maybe even vocationally as a PatternSmith, StaticPattern Architect, or StaticPattern Engineer.
  • The initial activities of creators (users) are hoped to lead them toward more advanced applications of Static Pattern Engineering : fluxpoints and spawned dreams.
• Whereas thingk.com is a product aimed at people already engaged in the act of creating (even if it prods them to do so) where the target is clearly identified, the DreamSpawn service works with a more nebulous concept – the dreams that begin to fascinate people but often a clearcut direction does not always manifest (sometimes for years).  By leveraging the concept of Thingks (static patterns) and the activities surrouding PatternSmithing, the service purposely guides its clients through training around the technology (and its goals) and the knowledge of PatternSmithing with the clear dedication to watching their dreams become a reality.  This is a very rational process and is only embarked on once a proper analysis and evaluation has been done.
• The FluxPoints project will eventually become a commercial product and service, but is the most advanced merging of static pattern engineering research with computer technology.  Therefore, it will be a joint venture between the research and development activity, the PatternSmithing Alliance, and the “ThingK” company for quite some time.  Essentially, it allows any Thingk (or collection of Thingks) to virtualize further by leveraging an advanced technological infrastructure for collaboration.  This ‘engine’ will be leveraged by the research and development group, the PatternSmithing Alliance, and the “ThingK” company to drive innovations and collaborations.  You can read more about it at any time at the FluxPoints blog (or via the PatternSmithing Alliance blogs which syndicate it).

Thanks.

• The Thingk is now embeddable and transportable via a comprehensive API that allows it to be composed into larger bodies of work (for an example, see the DreamSpawn project).
• Once properly qualified with further metadata, the Thingk can be used to expand an ontology and/or represent itself as an instance of an existing ontology in the Semantic web.  The FluxPoint enables full partipication of the Thingk in (most) semantic web technologies.
• The Thingk now acts a web service endpoint (with standard behaviors defined in the API), a linked data endpoint (according to semantic web standards), and a web resource renderable in multiple formats (including those supported by the NeoReQuest project).
• While creators (of Thingks) can collaborate with other creators and Thingks via the Thingk project website, this technology infrastructure allows collaboration of Thingks and creators by a more automated process — this is a combination of an agent API that leverages both the standard API and the semantic web technology to use inferencing and categorization to find unexpected connections.
• The FluxPoint now gathers data as it is exposed to the Ambient Flux — a new technology exposed via the FluxPoints hosting platform (and further enabled by NeoRequest project).  As requests are issued for the web service, semantic, and web resource interfaces for this technology, the surrounding context is also made available to the hosting fluxpoint.  The automated agents run random and targeted permutations across all fluxpoints on the hosting platform in an effort to find collaborations of Thingks and FluxPoints.  This is an intense collaboration of all the associated technologies above and is one of many planned.

Essentially, on a structural level, both the Thingk and FluxPoints projects follow a semantic web ontology established and maintained by the PatternSmithing Alliance; therefore, any Thingk is easily upgradable to a FluxPoint (and later, other entities) – the FluxPoint is a Thingk with added meta-data not applicable to an ordinary Thingk.  On a behavioral level, a FluxPoint is a container that wraps the Thingk with added functionality that operates on this extra meta-data.  For the hosting aspect, it is envisioned that a FluxPoint can eventually be hosted anywhere; however, as the API and behaviors continue to evolve in the beginning phases, it will be mandatory that all FluxPoints be hosted on our servers (to receive automatic upgrades in behavior).

Thingk.com will be a free community product; however, we are looking to encourage a revenue stream by offering premium tools for crafting the representation of the Thingks on the site and for patternsmithing them into the world.  I have neither the delusion that this company will be capable of inventing all of the possible ways of expressing or creating representations into the world nor the desire to corner that, so we will be looking to offer partners the ability to sell their tools on this site.  Now that brings up a few questions and all of them relate to if the site will immediately become littered with commercialism and the answer is a firm no.  That means the following things outright:

• The desire to give the web community an incredible free basic toolset for persisting, discovering, and using thingks will be fully realized — this base functionality will always be available for free.
• Opportunities to buy more powerful tools will be non-intrusive – the screen real estate will not be littered with it.  It will only be available when you really seek it out, tucked away neatly in the user interface.  Also there won’t be annoying intrusions on experience, trying to prod a user into upgrading – people are quite intelligent enough to seek out things they want.  This is not to imply that it will be difficult to find what you want or that there won’t be a good user interface once you begin seeking out premium tools.
• Users with premium tools will not have an obvious advantage over others, its just a matter of preference.  As a physical analogy, think of an art community where everyone is given a sketchpad, a basic set of pencils, brushes, and paint – the refined artist may choose to purchase an easel, premium paper, brushes, oil paint, etc; however, this doesn’t imply that either will produce better art – it is up to the artist to use the tools given or purchases along with their creativity.

The intention for DreamSpawn is to give the clients who use this service the full array of premium tools as they are made available — which brings up another point: companies and individuals who choose to do so may purchase the full array of tools available (with royalties paid to each of the partners who are represented as well).  This will be done for DreamSpawn for a reason that is explained below:

DreamSpawn is a concept I’ve been trying to tackle for years – probably since I was a teenager.  I wanted people to unlock their full potential but it would take me a long time to see the pieces of the puzzle and even more time to put them together.  I believe that once people reorient their mind toward viewing their larger dreams (which might span a large problem/solution domain) as a set of ThingKs, or thoughts on their way to becoming things, they have a whole new way of tackling the problem — this is typical analysis; however, there is a new spin on it:  By giving the dream itself (and thingks in general) value once persisted, people will begin to move forward with bringing their dreams about.

The other pieces of the puzzle attempt to solve three other problems:

• Dreams and thingks are often kept internal – and often get buried or forgotten.
• People don’t always find the right connections with other individuals and concepts – when this ’serindipitous event’ happens in life we usually witness the great events (company foundings, product launches, etc) that we all have come to celebrate.
• We all constantly work on skills to complete our vocational work, but all too often we don’t have the general skills or specific schools to create the dreams (set of thingks) that inspire us from time to time.

These needs are addressed by thingk.com, fluxpoints.com, and patternsmithing.com – not respectively or exclusively, but overlapping in interesting ways.  DreamSpawn brings all of this together by flipping it around to one individual – giving incredible attention to that client (and forcing them in turn to give attention to their dreams) to ensure no impedances keep that from happening.  As individuals choose to invest in time, attention, and money into their dreams, I want to give them a literal arsenal of tools to obliterate potential impedances.  I want their creativity to flow and want a full support network to wipe those three bullet points above off the table for reasons why they may look back and regret not creating this or that dream.

This blog entry is not a sales pitch to get you to sign up as a dreamspawn client – in fact, we’re not ready for you – that’s why this is an announcement of the “launch” of the sister site.  This is meant to only give a larger perspective of what’s going on behind the scenes, and I’m choosing to do what future users of this site may or may not choose to do – I am persisting out publicly a set of Thingks I am actively working on to bring about as a reality.  That is, I am releasing the concepts out there to spark interest, keep myself accountable, and get the dream in front of myself and others.  Collaborators, angel investors, future partners, volunteers, and future employees, as always, are always welcome.  Contact me at http://xri.net/=joel.kotarski or on the contact form on DreamSpawn if interested (also, feedback in general is welcome).

Finally, the PatternSmithing alliance — anyone interested in joining this alliance or learning more, contact me as well.

jdk

Once the framework is in place, I want people to be able to exclaim:

I thingk; therefore, I am creating…

as a representation that they are participating in being intentionally connected to the entire process from thought => think => thing or from thing => think and by expressing the entire process they are likewise engaged in inspiring others to create as well.

In order to express that notion across the web, I want people to have an online identity that succinctly expresses that.  I am a big advocate of OpenID and am building provider support for OpenID into the site in the beginning.  Therefore, anyone who has an account will be able to use this URL as an authentication mechanism for OpenID-enabled sites:

http://i.thingk.com/UserName

This URL will also correspond to the user’s public profile which will expose out any Thingks they have released to the public (or if an authenticated thingk.com user lands there, any Thingks they have exposed out to the appropriate group(s) that individual is in or uniquely to them).

Also, as aggregated identities centered around intention become more commonplace — tightly knit groups would be able to appoint delegates who could authenticate under the identity:

http://we.thingk.com/IntentionName

The intention for this is not to simply add to the growing list of URLs that a person uses to identify themselves* in the current internet ecosystem (though in a way it will do that and unfortunately add to that list); instead, it is a way to identify that which is being created by them beyond the current internet ecosystem – which as a whole other dimension we all now participate in to varying degrees is interesting in itself.  This identity represents not only them, but the thoughts which activated them enough to become thinks and have received intention enough that they will on their way to becoming things (or the opposite case things which they have created which have received intention to be expressed as thinks).  In essence, this represents not just the person (in an abstract way), but their intentions being manifested (thingks-in-formation) and the creations they have accomplished (thingks-as-artifact).

* Current examples span blog URLs, social networking for fun sites, feed aggregation sites, professional networking sites, etc.

So, depending on context, it may or may not be appropriate to use this provided online identity.  There are two lines to draw where it will or may be appropriate to use this online identity and a third class where it is up to the discretion of the user:

• The intentional web+ - a grassroots initiative started around this about four years ago and hasn’t gained a significant amount of momentum; however, this project embodies one aspect of the spirit of this movement.  Where people are using technology to actively aid in carrying out intentions (e.g., aggregating information based around a certain intention, or using technology to carry out an intention).  As these sort of sites begin to multiply again, it will absolutely make sense to use this sort of identity as those who see the URL will be able to use it to intentionally aggregate information or use it to find inspiration for their own intentions.  [This will be further amplified by the FluxPoints project later]
• The semantic web - an initiative that is slowly but surely gaining a lot of ground and I believe will soon cause a groundswell of potential on the web.  Due to the fact that semantic web technology is being built-in to Thingk.com from the ground up, semantic information will be exposed at this identity endpoint – so if a user chooses to express this online identity at sites which are likewise rich in semantic markup or have active semantic agents, the mutual information exchange available by simply exercising the identity depending on the context may bring benefit to multiple parties. [This will be further amplified by the FluxPoints project later]
• The third class I spoke about is the myriad places where someone can express identity on the web currently via OpenID- posting a comment on a blog entry, setting up an account on a forum, etc.  Depending on context, it might make sense to use one of several options available for authentication (several are shown below if you comment on this post) instead of this identity and it might make absolutely no sense to use this new identity at all (except of course to spread awareness of the new initiative).

+ Here is the homepage for the intentional web initiative established in 2005: http://intentionalweb.org/

Another post is forthcoming about the place for a site centered around Thingks in the current web ecosystem, as well as long term discussions about where Thingks will be hosted in the future if all goes well (that is, will they have to be hosted at thingk.com forever or like web sites, blogs, etc. can they be eventually decentralized).  Until then, if you’re ready to start wearing the T-shirts or hats, let me know. 

A thingk, quite simply, is both an idea that someone passionately pursued/is pursuing and the thing which it was/is becoming when manifested.  Since someone (we will call them the creator of the idea) is passionate about the idea, we can’t just call it a thought, but instead borrow a present-tense term from David Bohm and call it a think.  Since it existed/exists/will exist somewhere, we also call it a thing.  Combining the two words into a portmanteau, we call it a Thingk.

In order to qualify as a thingk, the following must happen to a person’s creation (whether it starts as a thought or a thing in the beginning is irrelevant) in any order:

• A burst of inspiration or a careful design process must bring a thing into the world* whose existence can be confirmed by a resource identifier.
• A thought or thoughts become so activated in the person’s consciousness so as to be qualified as a think or thinks.
• The intention to create something from an activated think or thinks or the intention to express the thinks behind a created thing must be present.

* The thing can exist physically or virtually but must have a computer-accessible and verifiable international resource identifier.

Thus, once the intention, the thing (whether existent or not), and the activated thought (whether expressed or not) come together we have a Thingk.   Stated another way:

think(s) + intention to create something= thingk

or

thing + intention to express underlying think(s) = thingk

When the think- or thing- component(s) of the thingk is partially or fully intention it is a Thingk-in-formation; once intention becomes reality, and there exists both thinks and a thing, it is now considered a Thingk.

The purpose of this site will be as follows:

• By providing a framework to organize the creative process (with associated tools, privacy mechanisms, and attribution), it is believed that the site will increase the quality of all participants’ creative endeavours.
• By allowing someone to release their work to selected individual(s), group(s), or the public at large, valuable feedback mechanisms will increase the quality of work as well as inspire others to new work.
• Both technology and community are expected to further enhance and encourage the creative process for all participants.
• By getting to the kernel of the creative process, it is desired that things we see in the world are matched with the thinks that inspired them or the thinks we hear in the world are seen manifesting into actual things.
• By allowing individuals to catalog the creative process in (hopefully) painless ways with minimal effort, new interconnections can be found between ideas (thinks), creations (things), people (creators), and the thingks which inspired it all.  In other words, we expect lots of new discoveries in terms of collaborations, career paths, and systems effects we were not even aware of.
• Finally, this site intends to lead all users into deeper exploration with their created Thingks, the Thingks that inspire them, and the resonances they imply.  This is meant to span the lifetime of both Thingk(s) and their creator(s).  It is envisioned that initial thingk(s) [prototypes are encouraged] may expand far beyond the scope originally envisioned.

This site is an application of Static Pattern Engineering technology as well as a member of the PatternSmithing Alliance.  It will be based on Semantic Web technology.

I am actively seeking collaborators, founders, research associates, future users, and future employees.  All feedback is welcome.  Contact me at =Joel.Kotarski.

In order to sense resonance clearly, it is my belief that a mind should be able to achieve a state called Unconditioned Consciousness, if only for a moment (which at times is all that is possible). The conditioning of consciousness is necessary (that is a question) to manage the complexity of the physical and mental domains — the usefulness and utility of conditioning can be observed by how well we can achieve such a wide array of useful and varied functions in our daily personal and professional lives (sometimes simultaneously) while still having a large reserve of attention available for achieving so much more.  I like Mihaly Csikzenthalyi’s classification of attention as psychic energy – and the organization of attention down coherent paths of consciousness as psychic order [whilst the opposite is considered psychic entropy].  As for ordering consciousness, a good percentage of learned behaviors (including reflexive reactions) order the flow of consciousness for a period of time and interestingly enough, reflexive reactions can likewise organize consciousness automatically to achieve goals (an often referred to example is that of driving a car between destinations without any awareness at all of the task at hand, while thinking about or attending to other things).

In order to describe how to achieve Unconditioned Consciousness, it is necessary to talk about the relationship between awareness, perception, and attention more deeply.  For a first slice at a model and analogy, let us picture that attention is the currency of consciousness[1] (which gives new meaning to the phrase ‘pay attention’).  Regardless of whether we are aware of the these transactions of consciousness, they are still occurring moment by moment.  Awareness applied reflectively to the contents of consciousness can be thought of a sort of meta-attention, that is attention about the target of attention, or where attention is being absorbed.  In order to suspend (and later rework) the automatic triggering of reflexive reactions, it is necessary to reach awareness of all reflexive reactions.

Early work on static pattern engineering examined two boundary conditions of interest:  Unconditioned Consciousness and Complete Absorption of Attention Without Awareness.  In the latter case, which takes many forms, I was most interested in cases of extreme depression and catatonia:  In catatonia, attention is completely absorbed – none is available – and when questioned later, those that went through this state have no recollection (awareness) of what the contents of consciousness were nor what was external to them (thus attention wasn’t attached to perception).  Nearly everyone would agree that this state is one of complete degeneration.  Short of medication that alleviates or changes the state of consciousness, how do people in this state move out of it?  The solution is a bit counter-intuitive: Awareness (which is completely or nearly nonexistent) is activated and then gradually expanded to encompass the content of consciousness[2].  Of course, the state of the content of consciousness is that nothing is moving – the economy of consciousness is completely frozen, attention is absorbed in apparently nothing, and not even perception is properly processed by attention[3].  Nonetheless, the gradual widening of awareness restores the flow of attention toward perception and gradually awareness detects the slow, painful flow of thoughts (which nearly always have a negative slant). Through this gradual expansion of awareness, the mind seems to reorder itself, allowing attention to work once again as the currency of consciousness.

I wanted to illustrate the extreme boundary case of Complete Absorption of Attention Without Awareness and the mechanisms that lead away from it to state quite simply what Unconditioned Consciousness is:  Complete Absorption of Attention With Complete Awareness.  Consciousness often operates with a mixture of reflexive reactions operating at a threshold below awareness (or at least only partially illuminated by awareness): to move toward unconditioned consciousness, it is necessary to follow the same mechanism of applying awareness as described above to expand awareness to the contents of consciousness.  It is easiest to apply awareness to perception and then to expand it across the entire content of consciousness.   Just as described in the previous post in this series, proprioception of thought (the sixth sense) is possible via invoking awareness.

In the next post in this series, I will continue the journey toward unconditioned consciousness (or complete absorption of attention with complete awareness) and talk further about reflexive reactions and dissolving, activation energy, sensing resonance, and finally resonant reactions.

[1] I know the skeptical mind will immediately transfer to this footnote: To answer any questions and to point out the immediately obvious flaws in this analogy, I will give the more expanded model for completeness sake: static patterns and reflexes are the currency of consciousness while attention is the current of consciousness (when it is causing an ordered flow of consciousness rather than just being absorbed).  Nonetheless, the model used above effectively illustrates the intended point.

[2] Please note that I am not simply stating that the complex treatment of degenerative mental states can be abolished and replaced with ‘awareness therapy’ nor that this works in all cases; however, this is based on studies and cases where a reversal of catatonic states and extreme depression have been reversed by the application of awareness by the volition of the person suffering this state.

[3] This state is intensely interesting in the sense that is attention is completely bound. All of this is more completely described and diagrammed in the upcoming book (sorry title of the book is still pending).