Remote Viewing Archives and Their Keepers

A documentary site handles remote viewing archives by separating three kinds of material that are usually mixed together: raw session notes and sketches, declassified government files, and the informal memory of the people who did the work. The first kind is evidence of a procedure, the second is evidence of an institution, and the third is evidence of a community. Treating them as one pile produces bad history. Treating them as three separate records, each with its own rules of proof, is what a site like Ten Thousand Roads sets out to do.

What counts as a remote viewing archive?

An archive in this field is not a single collection. It is at least four.

Session records come first. These are the working papers of a viewer and a monitor: handwritten notes taken in real time, sketches of a target site, sometimes a transcript, sometimes an audio tape. They are messy by design. A session is run under conditions that make neat documentation difficult, and the notes are often the only trace that a session happened at all. Their value is procedural. They show what a viewer wrote before feedback arrived, which is the only moment that matters for evaluating a claim.

Institutional files come second. The United States government ran remote viewing research and operations for roughly two decades, first under the Army at Fort Meade, later under the Defense Intelligence Agency, with the program commonly known as STARGATE. When the program was declassified in the mid 1990s, the released material included memoranda, contracts, evaluations and operational tasking. The Central Intelligence Agency's reading room and the DIA's FOIA releases are the public entry points, and the CIA commissioned an external evaluation of the program in 1995 that remains the most cited document in the field.

Community memory comes third. Before STARGATE there was a vocabulary, a set of habits, and a small network of researchers who corresponded by mail and later by early web pages. Much of that material was never filed anywhere. It survives in newsletters, personal sites, and the recollections of participants.

A fourth category, the popular literature, sits outside the archive proper. It is useful for dating claims and useless as evidence.

How are raw session notes read?

Raw notes are read for structure, not for hits. A trained reader looks at four things in order.

First, the tasking. What was the viewer asked to describe, and when was the question fixed? A session that begins before the target is selected is a different object from one that begins after.

Second, the sequence. Remote viewing protocols in the controlled form developed by Ingo Swann and others at SRI International separate a first, immediate impression from later analytical overlay. The notes usually show this separation physically: a page of short phrases, then a page of interpretation. Where the line falls is the most informative thing on the paper.

Third, the sketches. Drawings are harder to retrofit than words. A viewer who later describes a bridge can be accused of vagueness; a viewer who drew a bridge before being told there was a bridge is making a narrower claim.

Fourth, the feedback record. Was feedback given, when, and by whom? A session with no feedback is not worthless, but it cannot be scored the same way.

Sites that publish this material tend to publish the scans alongside any transcription, because a transcription is already an interpretation. The rule is simple: the reader should be able to disagree with the editor.

What do the declassified files actually show?

The declassified record shows an institution testing a claim and never resolving it to general satisfaction.

The 1995 evaluation, conducted for the CIA by a statistician outside the program, reviewed the experimental literature and the operational record and concluded that the effect, if any, had not been demonstrated at a level that justified continued funding. The program was terminated. That conclusion is often quoted as the end of the story, and it is not the whole document. The same evaluation noted that some individual results were difficult to explain and recommended that the underlying phenomena, whatever they were, deserved attention from a different kind of research program.

What the files also show is bureaucratic normalcy. Tasking requests, security classifications, personnel reviews, budget lines. A reader who expects either a conspiracy or a breakthrough will be disappointed by both. The archive reads like what it is: a small intelligence program with an unusual subject, run by people who filed their paperwork.

Three cautions apply to anyone working with these files. Declassification is not completeness; whole folders were destroyed or withheld. Redaction is not always meaningful; names are removed for privacy as often as for secrecy. And provenance matters; a document circulating as a scan without a release number is a rumor with a typeface.

Why does community memory need its own method?

Because it is the only record of how the work was actually done day to day, and because it is the least reliable record in the archive.

Participants in the early remote viewing community were not writing for historians. They were writing newsletters, teaching workshops, and arguing with each other. Their accounts are shaped by loyalty, by disputes over credit, and by the ordinary decay of memory over decades. None of that makes the material useless. It makes it testimony.

The method for testimony is different from the method for documents. A document can be dated and authenticated. A recollection can only be compared against other recollections and against the paper trail. Where a memory and a document conflict, the document usually wins, but the memory often explains why the document says what it says.

There is also an ethical dimension that documentary sites increasingly acknowledge. People who participated in this research were, in some cases, still living when their work was posted online. Preserving their accounts means preserving context: what they claimed, what they later revised, and what they never claimed at all. Quoting a participant's early enthusiasm without their later doubts is a form of distortion, even when every word is accurate.

How should a reader weigh anomalous results?

Slowly, and with attention to the design that produced them.

An anomalous result is a result that does not fit the model being tested. In this field, anomalies appear in three places: individual sessions that match a target with unusual precision, statistical effects in aggregate scoring that fall short of conventional significance but do not vanish, and operational cases where a viewer's report was used and, by the account of those involved, proved useful.

Each requires a different question. For a single session, the question is whether the match was judged blind and by whom. For an aggregate effect, the question is whether the experiment was replicated by an independent laboratory with the same protocol. For an operational case, the question is whether the outcome can be verified outside the memory of the people who ran it.

Most published treatments of this subject answer one of those questions and imply the other two. A documentary approach answers them separately and states which one is being answered. That is less satisfying than a verdict and more useful than one.

What does preservation require?

Preservation requires decisions about what to keep, and those decisions are arguments.

A site that publishes everything makes no argument but creates an unusable pile. A site that publishes selections makes an argument and risks burying what does not fit. The workable middle is to publish the primary material with enough apparatus that a reader can navigate it: dates, provenance, release numbers where they exist, and a clear statement of what is missing.

That last item is the one most often skipped. A collection of session notes with no indication of how many sessions were run, or how many were discarded, tells the reader nothing about base rates. A file release with no note about withheld folders implies a completeness it does not have.

For readers in the San Juans and elsewhere who come to this material from an interest in intelligence history rather than in the phenomenon itself, the archive is still worth the time. It is a well documented case of how a government evaluates an unusual claim, how a research community forms around a contested method, and how both leave paper behind. The paper is the part that lasts.

Sources: www.cia.gov.