Programming: Planning, Sessions, Locations & Styles

Back to “Mind Control

Sources: Chainless Slaves |

Before a subject can be programmed, authorization for programming must be obtained. The extent of the programming to be administered and the amount of coercion/deception that are considered acceptable during the process are also determined in this stage.

A Note About Programming Sites

Here is an interesting comparison between traditional physical programming environments and virtual ones. The mind can be located in the physical world externally, but “detained” in the virtual environment in every sense that counts, and that is important to the programming process. Consciousness can be ‘contained’ in the digital environment even while the subject is physically in the same environment as he or she was prior to the programming.

Most of the available documentation about mind control is terribly outdated and a lot of it was written several decades prior to the current state of technology. There are disadvantages to the “digital” programming site; since it is not a “Total” institution, the subject is left in the company of family of and friends who may be supportive. However, the psychological goals of the “digital” programming site are to discourage affiliation with outsiders to the extent that physical detention would not be significantly more effective, because behaviors of avoidance and paranoia are encouraged and facilitated to the extent that the subject avoids these potential support systems of his own accord.

There are other advantages to a digital programming site. It’s considerably more economically feasible, and if addictive patterns are deeply rooted and established in the subject’s habits, they can be subject to constant reinforcement of programming. They are “present” consciously in the “digital site” to a psychological extent that, when mixed with confusion/disorientation/identity degradation and trauma tactics, can achieve the same or even greater degrees of programming impact. Even though the “sustained” presence of the mind in the digital arena is less  intense then the physical detention center, the reduction in intensity is compensated with the increase in exposure.

That is, with a physical detention center, a subject needs to be released eventually. But the “containment” experienced by a digital site can persist indefinitely, and because the brain is very poor at making clear differentiations between the significance of cyber events and the significance of face to face interaction, often very slightly moderated techniques will work just as well for programmers in the digital realm, particularly when a programmer is well versed on taking advantage on the “cognitive blindspots” unique to the internet environment.

The mind is not a representation of the physical external world. Rather, our conscious existence is mediated by the inner world we experience internally, regardless of what’s going on outside of us. The same environment can look very different depending on whether you are a trucker passing through a town in transit or it is the hometown where you grew up and graduated high school. There is no physical difference between these spaces in the physical world. Rather, it is the mental representation of these environments that is altered. If you are constantly “plugged in” and you spend the majority of you conscious existence online, you are in a true psychological sense, a “cyborg”. So long as that world exists for you in the abstract sense of gaining your conscious waking mind’s attention, it is capable of influence and moderating your personality and sense of self no less then any physical environment. Likewise, a skilled digital programmer will be just as effective as a face to face programmer at instigating programming strategies.

The structure of the digital programming site also invites it to serve as a 24/7 reinforcement, because different individuals and timezones can take over duties on shifts. Thus while it has less “immediate” impact, it has greater “sustain” and should by NO means should we discount the programming potential of the digital site. This is a very new topic however, and more research should be pursued in this arena to measure operational differences between these environments .

PROGRAMMERS I

Generally you will find a minimum of two programmers working with any particular subject. One will be designated “Lead” Programmer and the other as “Wing” Programmer (functioning as an assistant).

  • The rule calling for a minimum of two programmers per subject is in order to ensure that the programmers keep an eye on one another
  • If one programmer is too severe or two lenient, the other will step in and make up the difference
  • Also, having a pair of programmers ensures that if one develops to close an emotional investment in the subject his partner will speak up/recognize it. Overstepping such emotional boundaries is typically harder to recognize with oneself then it is to recognize with others.

Specific Purpose: before programming begins, PROGRAMMER ought to have clear objectives/programming goals to plan towards.

Things that should be planned in advance by programmers: Session codes, triggers for parts/alters, session outlines and programming goals for specific sessions, timeline of programming sessions and scheduling.

Planning in advance means that proper preparation can be made, and contingency plans considered in case a subject is resistant to some approaches/strategies initially planned by PROGRAMMERS.

Preliminary Psychological Analysis

      Having a psychological outline of the subject for a programmer to look at in advance can greatly aid in the process of planning the programming sessions and the ideal strategies to be used with a particular subject. A good programmer will cater the goals and approach of the programming to match the individual subject. A working knowledge of the subject’s current values and operative belief systems and their dominant sensory representational system can be of great benefit in the planning stages of programming.

 

PARTICIPANTS II

In one particular programming session, the amount of PROGRAMMERS present will vary based on the goals of that particular session and the current state of the relationship between various programmers and the subject. In general however, a given session may have anywhere from one programmer to a large team of four or more.

The size of the team may depend on the importance of the programming session’s goal – a high priority programming objective may have a more intensive team for that particular session. Another factor which determines the size of the team is the intensity of the subject’s resistance for that particular session. A particularly strong state of unforeseen or difficult to deal with resistance may require a more specific team.

As mentioned before, on average a programming session proceeds with one Lead programmer , on Wing programmer, and one subject.

The Programmer During the Session: a programmer must balance two opposing objectives simultaneously during the programming session…

  1. The programmer must build a relationship with the subject and build trust / rapport while simultaneously
  2. Remaining objective / detached on a deeper level
  3. That is – the programmer must be capable of holding both their connection to the subject and their detachment from the subject at the same time with equal sincerity

     Poor programmers confuse the internal detachment from the subject with the programmer role-playing the affection entirely – ie, they believe that they must merely pretend to care about the subject and be invested in them. But this is not true, and often a subject will be able to eventually detect an insincere connection from the programmer and is unlikely to build rapport with the insincere programmer.

    The affection should not be “an act”. Rather, to be persuasive, the sympathy and anger a programmer directs towards a subject ought to be genuine, however, it must not impede the programmer’s ability to, on a deeper level, apply precise, unaffected programming on the subject.

Changes in Programmers:

  • If a programmer becomes too emotionally involved in the subject they should remove themselves from their position or report their emotional state so that changes can be made if need be
  • For most sessions, the focus of the first part is predominately concerned with developing the relationship between a particular programmer and a subject. This is considered to be even more important then eliciting information from the subject, so the disadvantages of changing programmers is obvious
  • Every time a programmer is changed, the process of building rapport and a relationship between the subject and programmer must be restarted from scratch
  • This, when a “CHIEF PROGRAMMER” is assigned they should ideally be with the subject until programming is over

Session Timing: Resistant subjects should be subject to unpredictable programming schedules so they don’t ever know when to expect attention from the programmer or how long isolation will persist. This state of uncertainty increases tension and is likely to increase compliance in the resistant subject.

Session Content: During the session, PROGRAMMER is engaged in the following with subject

  1. trauma techniques
  2. scripting
  3. coding
  4. fracturing of psyche

END OF PROGRAMMING: Successful programming involves two key processes:

  1. regression of the subject
  2. provision of an acceptable ending

The isolation of the subject imposed by handlers to prevent the subject from forming real relationships with outsiders needs to be maintained even after programming goals have been concluded. The bond/relationship between programmer/handler and subject needs to be maintained for purposes of upholding the programming as well.

This is actually one distinct advantage of the digital over the physical programming site. Of course , there is nothing to preclude both sites from being used on a particular subject depending on the plan / goals of programmers.

 

 

Advertisements