Your explanation as to why nouns are avoided?
"The brain has no context whatever on data for that level of decision; it would be up to the analyst to know the 'tasking context' to put description into."
[...] What does it mean for a brain to have no context on data for that level of decision?
It means if I show you this image:
You might be unable to tell me that this image is, OF COURSE, the stocking'd leg and uniform of a
circus performer with an elephant, and that in fact when your brain got that information it was mostly upside down and sideways and had a bizarre sense of 'breeze' and half a dozen micro-instant flashes of association that are from your memory bank concerning probably previous red lycra visuals, circus visuals, elephant rides, and god knows what else, many of those ALSO appearing in 'pieces' completely out of context, some almost as slightly-opaque overlays, but everything usually so subtle it can be just below the threshold of what can even be articulated. Sometimes it's a friggin miracle information makes it to the paper at all.
A viewer works on perceiving, on translating what they perceive, on articulating what they perceive via sketch or words. They look at hard feedback. They compare every word/phrase/line of data they wrote down with the target, with their remembered-experience of what made them write that down, and they hopefully learn something from that. Rinse, repeat 10,000 times.
Like any sensory process, active repeated use for input and neural mapping to 'meaning' of input is required. Unfortunately this is a VERY long term practice; probably one of the most frustrating arts on earth for that reason and others. Everybody is working on it. Even the most public 'expert' (McMoneagle) fails sometimes and he is learning still, and forever. Everybody else has varying levels of skill, some better than others, all subject to variance.
Some people, like Gulliver, are more courageous and "this is weird and fun" than others -- they have the guts to go out in public and try it just for the hell of it. They've seen it work enough times (and sometimes stunningly) to believe in it, but they know it varies and it might suck or be great or be so-so, and no matter what the case it might still get trashed by people. But they have enough interest in the viewing and lack of concern for public opinion to be willing to go for it. I really admire that in viewers.
Psi by nature is a personal and often kind of intimate experience and it is not easy to put out for people to stomp on, because psychologically it feels less like a work report than a love poem or something; more personal.
Why is it up to an analyst to know the "tasking context" to put description into?
Because the more successful approach in RV tends to be asking a specific question for which you can take a specific "descriptive" answer and apply that info, knowing what you know so-far. Remote viewing is not designed for things that radio satellites, intelligence agents and cameras can do. They are all vastly better at all of that stuff.
RV is best utilized (aside from the 'personal hobby' element of course) to address things that nobody knows or can even give an 'educated guess' about, or to reduce the larger probability-set when there are a zillion options and you have to start looking somewhere, etc.
A tasker would not be asking, "What is one given thing in the whole universe, describe it so I can guess what it is." Usually taskings are more like a PI/detective that has a good deal of info already but is looking for some important detail, or a lead to one of some choices, or description of one specific thing, etc.
Two important considerations are:
(1) RV data is not used alone but in concert with other forms of intell/info;
(2) RV data is often a 'process' to get. It's not like you just ask someone, they hand you something and it's over; in a perfect world yeah, not usually though. It often involves multiple viewers and/or tasks, re-tasking the viewer(s), compiling the info and evaluating which of it might apply to the specific question(s) and how, etc.
It's not a magic-8-ball; it requires both skill and something of an art in the people managing and utilizing it, as well.
Some have it, and are willing to make the effort because it can be amazing when it's all done well, and it can provide something nothing else can.
Some psychological profiles really need very simple things and clear facts and are not really intuitive or flexible enough to figure anything out (eg no amount of related, symbolic, analogy or allegorical, etc. in the data would do them any good because they're so "over-literal" in their information processing), and they'd be terrible as RV managers or evaluators. To each their own.
What is "tasking context?"
The known question and reason for doing the viewing.
If I'm a detective tasking a viewer to describe the current health-state of a missing woman, the target is the woman's health but the tasking 'context' is the larger reason for the viewing--that a woman is missing, that it's a police investigation, and more specifically, that we are looking for a woman of known description who's been missing for 7 days now.
If the viewer describes something biological, dead, in a forest-like area, sense of violence/drama, I don't need to be a rocket scientist to 'guess' what they are referring to, nor do I need to get that data and go "Hey! If they didn't say that was Jane Doe, HER, how do we know this isn't just coincidence?!"
The viewer had a task and they had NO idea what it was but some numbers. Unless they're describing nothing but an object or a zebra or something, it's considered that whatever data is provided--though it will vary in specificity, application, accuracy and detail--at least
might pertain to the specific question asked. This may be wrong but some baseline 'try it' points are in place here.
In most applications, tasks are specific and the context is specific. Only in science does remote viewing provide a judge with 5 deliberately-disparate options and have someone choose 'which it matches best'; only in media or the internet (or practice) does someone merely attempt to describe a target and then see 'how well it matches'. Only in really hardshell cases like the Japanese FBI with McMoneagle is a viewer asked to describe a bunch of stuff including multiple locations, 'path through' all those locations, and detail, in order to find someone missing sometimes for decades -- probably about 3 people on earth could do that and McMoneagle is one of them (and the others are private).
Eventually other people might be able to do that; he has over 30 years of more than full time experience -- most people are working adults with families and lives and even if they are really 'into' RV, the number of hours available to an employed adult with a life are at best 'hobby-level'. For most of us viewers to get the equivalent experience of someone like McMoneagle we will need to live to be about 400 years old. In the meantime, we do what we can where we are, we look at hard feedback, we evaluate what we did poorly on and what we would like to have gotten and didn't, and then we do it again and, like any other art or skill, hope to improve with practice. If the theorists are right and human beings simply have some kind of biological sensory functions which allows us to perceive nonlocal energy, the issue is learning to wake those senses up and use them, and get enough real-world hard-fact experience with them that the brain will learn how to 'map meaning'for them.
Who is the "analyst" and what defines his or her role?
The roles common in remote viewing are (off the cuff this is. I should write this up so it's more formal...):
Project Manager - outlines things; a scientist or detective may play this role. Defines the protocol, scope of the project, sometimes the specific data desired.
Tasker - is often the project manager as well, (a) looks at what info is needed, (b) thinks about how to best put that into formats that remote viewing can be expected to address (eg physicals vs. abstracts), (c) considers questions that "descriptive data" is going to be useful as response to (as no labels or abstracts are predictably obtainable), (d) considers the viewer(s) available and their known strengths or weaknesses in this art [eg some people are better with person targets, some better with technology], (e) assigns numbers to it or drops it in software that assigns it one and gives the number to the viewer. Often when the session comes back, they might after looking at the data, (f) re-task the same question if they didn't get what they thought answered the question [add it to the flow of overall tasks to that viewer, so they don't know it's a retask usually], or (b) might re-task a different question, or perhaps a question about something within the session.
Viewer - collects information 'intuitively' and attempts to translate when necessary and record it all legibly.
Interviewer or Monitor - this is an optional role. It is difficult to keep some degree of 'influence' out of the situation since a viewer is de-facto 'suggestible' because they are "being open" at that moment, so this should either be someone really good or nobody at all. In a traditional science sense, the role here is simply to 'facilitate' the viewing, help keep a person on track in logic (viewers may be altered-state), to ask questions that come to mind (as the viewer's unlikely to think of them on their own when in that state), etc. In a scientology sense [!...don't get me started...] this is a 'controller' role called monitor which makes sure the viewer is 'doing things right' and 'directs them'. In today's world most viewers don't have any kind of interviewer or monitor.
Analyst/Evaluator - these terms vary a little in usage but generally, an analyst is someone who analyzes the session based on the historical tracked accuracy of the viewer on each specific kind of data and a target/tasking genre in general. This usually assigns 'probability weights of accuracy %' to data points based both on that person's stats, and on a long list of 'tells' that people familiar with RV see and recognize as implying a viewer may have had more/less analytical or target influence at a given point. (This has nothing to do with the target, to which the analyst is at least initially blind; it is only regarding the session and viewer. Sometimes target context or detail is provided to the analyst afterward and some additional work is done based on that genre of target in the viewer's historical performance.)
An evaluator is someone who takes the data and attempts to figure out how those puzzle pieces fit into the 'tasking context' -- given the question asked (tasking context), and the known situation (the larger target context), how might that data answer the question? Separate from both of these descriptions, the word "analyst" is often used rather 'generically' to mean any or all of the above, and in general, 'the person who considers the data, the question, and decides what to do from there' -- so this is often another role the project manager plays as well.
In a science role, usually the above is instead a 'judge'.
There are other peripheral roles (a viewer profiler for instance, who tracks the accuracy of a viewer in detail and may also play the literal 'analyst' role mentioned above). This entire situation is fairly flexible as long as the viewer stays doubleblind to the target detail and preferably to its nature--this as much for the sake of data evaluation as anything else.
Sometimes the viewer WILL know a target's nature either unavoidably or because they get that in the first 10 minutes of session. Then they have to spend the rest of it fighting 10x as hard to keep their brain from putting every damn impression into a 'labeled specific' based on what they think they might already intellectually know about the target, filtering information that doesn't fit into that, mutating information so it better-fits, etc. (this is referred to 'AOL-Drive', aol being 'Analytical Overlay').
It only takes several sessions of letting this happen and being 'sure' before a viewer discovers what a mistake that is and learns to do what they were told all along and 'avoid labeling'. This is why most real viewers actually prefer the doubleblind because while on one hand it removes their context entirely, on the other hand it prevents assumptions. Some viewers work DB for an initial session(s) and then 'generically frontloaded' (eg 'the target is a person' or 'the target is an object') for a followup session, so their mind has some context for the information modeling. In a good session a viewer only gives labels if something very clearly came across exactly like that. Most (not all!) data is actually a memory-clip from the brain's database of experience, of something "like" the target. This is a whole subject of its own but yet another reason why psi is easier to do poorly than well, but has immense potential if only humans could get a handle on the details.
Some of us are working on it. Not omniscient yet.
RC