What the STARGATE records actually preserve
A guide to the former program collection, its document types and the limits of a declassified file.
The STARGATE record is a useful place to begin because it contains several kinds of evidence in one public collection. It can show that agencies commissioned work, preserved reports and later released documents. It cannot turn every report into a verified event. This page therefore follows the file trail: who created a record, what purpose it served, how it was released and where a later summary begins. That sequence matters when an administrative memo, a session sheet and an evaluation are discussed as though they were interchangeable. The archive treats the collection as historical evidence about an intelligence-community program and as a source of questions about method, reliability and use.
Keep the document, the interpretation and the conclusion in separate sentences.
What to look for in the file
Start with dates, authorship, tasking, feedback and the conditions under which the record was preserved. Then compare the source with the page that describes it. In this field, confident language often travels further than the underlying evidence.
That does not make every account worthless. It means that accounts need labels. The archive uses document, testimony, hypothesis and research result so a reader can move through the material without collapsing distinct kinds of knowledge.
Why this page is here
This file belongs to the History & Archives route. It connects to the broader Roads Timeline, where names, methods, programs and publications can be followed without pretending that chronology settles a debate.
A file is not the program
The STARGATE collection is best read as a mixed administrative and operational archive, not as one continuous experiment. It can include memoranda, training material, task records, correspondence and later reviews. A document proves that an office created or retained a record; it does not prove the proposition described inside it. Start by identifying the issuing office, date, classification history and intended audience. Then ask whether the page is reporting an event, describing a proposed method or summarizing a later judgment. Those are different evidentiary tasks, even when they share a folder.
How to make a cautious reading
Choose one document and transcribe only what can be seen: names or initials, tasking language, feedback, routing notes, attachments and redactions. Separate the document date from the date it was released to the public. Compare the item with the CIA collection context and with the 1995 historical account, but do not treat a later summary as a substitute for the original page. A useful research note has three columns: record, immediate interpretation and unresolved question. That format prevents a striking phrase from becoming a conclusion by repetition.
What the archive cannot settle
A declassified file cannot by itself establish that remote viewing worked, that a session was operationally useful or that every participant shared the same method. It can show institutional interest, the vocabulary used by a program and the kinds of material preserved. Testimony may add texture, but memory and retrospective framing have their own limits. The strongest claim available here is documentary: STARGATE left a public trail that can be inspected, compared and read against the program’s eventual evaluation.
Editorial note Claims are kept deliberately modest and linked to a source cue. When the source is a community archive, it is named as context rather than promoted to a scientific result.
