Mind-Self does what?! Part One
- David J. Hastings PhD

- Dec 15, 2019
- 5 min read
Cognitive-Pathways Model
The graphically presented ‘#Cognitive-Pathways Model’ (CPME) Inbound and Outbound #Mechanisms, which are outlined in the #Mind-Self Task-List (MSTL) resource, are critical to understand because #Cognitive-Pathway determinations literally spirit one’s second-by-second #cognitively tailored (#Cognitive-Pathways generated) #perception of ‘#reality’, coined Movie-of-Your-LIFE (discussed at L9:S3).
Note: The ‘#Cognitive-Pathways Model’ illustration does not contain all #Mechanisms: To support clarity, balance between diagrammatic content and detail was elected. However, to explode comprehension, other illustrations will be provided when appropriate.
Excitingly, comprehending #Mind-Self and #Cognitive-Pathways #Mechanism functions (L5 through L9) will earn you control of YOU back: Subsequently, empowering both you and your #Clients.
Stated differently, understanding #Cognitive-Pathways functions is synchronous with understanding yourself.
Consequently, this Blog introduces how the #Cognitive-Pathways #Model #Mechanisms not only variously ‘handle’ and morph #current-new generated from #Cognitive-Alerts AND/OR #Visual-Sensors (that can rapidly escalate from ‘Nominal’ or unremarkable to #Survival threatening), but also drive #assumptions, #awareness, #thought, #ingenuity, and so much more.
Also, this section introduces how #Passion, emotion or excitement-gradient play THE vital role in not only data-#archived action-#potential density and thus data-#recall effectiveness but also the consequent creation of #beliefs, #personality, #behaviour, etc.: coined #Cognitive-Habits or Experience-#Senses.
Note: #Mind-Self end-to-end functionalities are presented in H300 courses, which parallel the ‘Levels’ (L5; L6; L7; L8; L9) on both the #Mind-Self Module Synopsis (MSMS) and its detailed companions available in the Appendix: #Mind-Self Module #Mechanisms (MSMM); #Mind-Self Task-List (MSTL); and #Mind-Self #Handling-Cycle Descriptive (MSHCD).
Please utilize the resources noted above to track discussion development. They will also assist to properly align perception of the incredible array of #Cognitive-Pathway #Mechanism processes, juxtapositions and transitions.
The ‘#Mind-Self Module Synopsis’ (MSMS) delivers a compact descriptive of the #Cognitive-Pathways Model #Graphic (CPME) showing both Module dependencies, their proprietary #Mechanisms and sub-set #Components. MSMS also performs as a high-level outline of the H300 Course-Series.
Note: The ‘L5’ through ‘L9’ designations, to the right of each Module on the ‘#Mind-Self Module Synopsis’ (MSMS), link both the semi-detailed #Mind-Self Module #Mechanisms (MSMM) and the detailed #Mind-Self Handling-Cycle Descriptive (MSHCD).
Obviously, neuro-physiological processes seamlessly and rapidly transition. The purpose of the CPME and supporting resources separating the many defining #Cognitive-Pathway Modules, #Mechanisms and #Tasks is to clarify the variant, yet #cooperative, functional aspects that drive one to be who they are.
The MSHCD document is dually purposed to not only clarify the CPME #graphic but also provide a progressive discussion outline: From initial #Mind-Self Module Inbound #Mechanisms (i.e., Flow-#Regulator; L5:S1:T1 and #Cognitive-Sensors; L5:S1:T2) to ultimate Movie-of-Your-Life (L9:S3) devised ‘reality’ presentations.
Supporting Mankind’s incredible diversity is #Mind-Self within which is nested the #Cognitive-Pathways Model that depicts #Figure-It-Out’s extreme capabilities.
As discernible from both the MSMS synopsis above and CPME illustration, the #Mind-Self base-plate provides not only its own Inbound and Outbound proprietary #Mechanisms but also Plug-ins for two other interfaced Modules, #Cognitive-Filter (CF) and #Figure-It-Out (FIO), which each provision proprietary Mechanisms as well.
As comprehending #Cognitive-Pathways Model structure is fundamental for grasping all future course discussions, it is recommended to carefully study graphic and descriptive resources.
Globally, #Mechanism functions are stratified into three processing steps: retrieve a previous #Mechanisms Outbound action-potential from the ‘in-box’; #manipulate or data-reconfigure #retrieved action-potential to specific #Mechanism requirements; and deposit adjusted action-potential into a follow-on #Mechanisms ‘in-box’.
Notable is that #Cognitive-Alerts (L5:S1) and #Cognitive-Sensors (L5:S2) are the exclusive initiators of all #Mind-Self #Mechanism processing. Remarkably, as each provides very different action-potential to #Cluster-Works (L6:S1) and #Visual-Works (L6:S2), respectively, they are the only sources that can initiate one’s potential.
#Cognitive-Alert protocols are first to be discussed below.
Flow-Regulator
As #Body-Self has done what it can to ameliorate the #Problematic Bombardment-Event (BE), it calls upon its #Mind-Self collaborator for additional assistance ‘suggestions’.
Flow-#Regulator functions as the only entry-portal or transitional buffer-zone between #Body-Self, which delivers #Cognitive-Alerts, and #Mind-Self, which is purposed to #Solution them. Thus, #Mind-Self is assigned responsibility for providing enhanced assessment and consequent appropriate ‘action-suggestions’ (via Test-Its).
As both types of #Cognitive-Alerts - #Request-Alerts (RA’s) and #Imperative-Alerts (IA’s) are distinctively tailored, #Flow-Regulator appropriately provisions two independent neural-resources or ‘in-box’s’: R-Chan and I-Chan, respectively.
Notable: Just as #Cognitive-Sensor #sensory-acceptance (i.e., ‘Vision’) demand prompt ‘handling, so do the other two forms of #Mind-Self #sensory-acceptance: RA’s and IA’s. In other words, as a #Cognitive-Alert has the same imperative as visual #sensory-acceptance, Flow-Regulator ‘handles’ it expeditiously.
Congruently, Flow-#Regulator’s first-phase allocates Inbound #Cognitive-Alerts to one of two processing channels. MACRO-intensity #Imperative-Alerts are directed to the I-Chan processing-channel, which provides suitably expanded #neural-resources designed to accommodate both MACRO-intensity and short-term retention (about five flexible seconds).
#Request-Alerts on the other hand, which do not require extensive neural-arrays, are assigned to R-Chan, which provides appropriate-to-intensity #neural-resources; however minimal retention capability.
Note: allocation to either R-Chan or I-Chan is established by the quantity of cerebral-neurons activated or triggered by the action-#potential energy-gradient of a #Cognitive-Alert: i.e., MACRO-intensity for #Imperative-Alerts or variably lesser #Threshold-intensity for #Request-Alerts.
Flow-#Regulator, like all #neural-resources have a maximum capacity: i.e., a finite number of neurons dedicated to fulfil its operating protocols. Thus, even when Bombardment-Events inspire copious #Request-Alerts that quickly and continuously arrive at Flow-#Regulator’s in-boxe (as when skiing a new, challenging Black run), Flow-Regulator is ‘normally’ able to cope.
Recall: An #Intensity-Check tailored #Request-Alert is composed of a single, non-survival-threatening #Tag-Cluster; whereas #Survival-Threat differently delivers discrete #Imperative-Alerts merged from many SAME #Tag-Clusters of MACRO-intensity.
Consequently, #Imperative-Alerts, due to both extremely elevated MACRO-intensity and complex configuration, present demanding challenges. Critically, ongoing #Imperative-Alerts can cause a #Flow-Regulator capacity-#overload and thus negative short-term and extended-term BE-assessment difficulties.
#Survival demands priority ‘handling’ of #Imperative-Alerts: Even at the exclusion of #Request-Alerts.
Thus, #Imperative-Alerts will invariably quash #Request-Alerts, which will dramatically alter one’s BE perception. Altering is due to loss of less intense, #Request-Alert BE originated, action-potential ‘clues’ to ‘What-is-Going-On’ Out-There.
Specifically, loss of sufficient #Request-Alerts (due to #Imperative-Alerts usurping all #neural real-estate) will hamper not only ‘normal’ processing but also data-#archiving endeavors, and thus #recall, and thus #perception.
Therefore, #Request-Alert integrity endures as long as #Flow-Regulator is not overloaded; whereas when overloaded with #Imperative-Alerts, the #sensory-accepted ‘clues’ represented by the #Request-Alert are lost; as if the BE’s never occurred.
Thus, no wonder when reflecting on a survival-type situation, recall of less intense BE’s is scarce to nil.
Stated differently, the action-#potential that was provided by less intense #Request-Alerts dispersed because ongoing #Imperative-Alerts usurped all #Flow-Regulator #neural-resources. Thus, to #Mind-Self, the BE’s represented by the turfed-out #Request-Alerts simply never occurred.
Hopefully, #Imperative-Alert barrages are scarce in one’s lifetime: Especially as neither #Body-Self nor #Mind-Self #neural-resources are designed for extended #survival-intensity ‘handling’.
#Flow-Regulators second-phase merges R-Chan and I-Chan Outbounds into a single contiguous FR-packet Outbound, which it streams to #Cluster-Works. Two FR-packet conditions’ are possible. The FR-packet will be comprised of either only variable-intensity #Request-Alerts or both #Request-Alerts and #Imperative-Alerts. (Note: Rare would be only Imperative-Alerts).
Clearly, survival-situations present BE’s, which ebb-and-flow in #intensity and ‘quantity’. Even in catastrophic situations some rudiments of tertiary #Request-Alert BE’s can get processed, although probably distorted by #Request-Alerts being jaggedly interrupted due to #Imperative-Alerts overwhelming #Flow-Regulator #neural-resources.
Interestingly, one can ‘sense’ such an ‘FR-overflow’ occurrence. Correspondingly overwhelmed, when one intuits BE’s are too rapid to grasp, responses such as closing one’s eyes, stepping away, cease listening, ask the presenter to slow-down or repeat material, etc. will invariably occur spontaneously.
Also, to prevent #neural-overload for the next #Mechanism (#Cluster-Works), Flow-Regulator also performs as a #neural-capacity safety-valve. In other words, as its name suggests, it flow-regulates its FR-packet Outbound to #Cluster-Works.




Comments