Method & terms

alien-contact.me is a personal, noncommercial source archive maintained by one operator under the name Node-1. It combines a selective public record, a field guide, and a reference index.

This site is not a government authority, not an emergency service, and not a professional investigation organization. It does not operate communities, groups, events, trainings, or "contact sessions" under this or any other name.

It does not claim institutional authority or case-verification capability. The public value is the traceable source record and the stated method, not the operator's identity or credentials.

I want this to stay useful whether you lean believer, skeptic, or somewhere in between. The goal is a calm record, not a side.

Labels describe source role (Official / Testimony / Public context), not proof of origin. This site can be wrong: sources get updated, context changes, and interpretation drifts.

Ground rules: I don't claim proof, there are no ads or trackers, and I don't share private messages without asking first. Privacy details (retention, deletion, and infrastructure logs) are on Transparency.

Official UAP reports are usually written to document scope, process, and what can be stated in public. They rarely read like one big theory, because the goal is traceability: definitions, sources, assumptions, and limitations.

Start with the frame: identify who published the document, the date/version, and the intended audience (policy oversight, aviation safety, scientific recommendations, historical review).

If you want a quick way to skim these reports, try this approach:

1. Executive summary: what is actually being stated, and what is explicitly not stated.
2. Scope: what time period, what domains, and what kinds of cases/data are included.
3. Assumptions: what the analysis assumes about sensors, observers, reporting, and reliability.
4. Definitions: what "UAP" means in this document, and how key terms are used.
5. Data sources: what types of data exist in this pipeline (and what is missing).
6. Limitations: redactions, missing metadata, sensor artifacts, collection bias, and why cases remain unresolved.
7. Findings vs. interpretation: separate what is supported by cited facts from what is commentary or inference.

Keep two columns: (1) what the document directly supports (data, citations, defined terms), (2) what people add on top (interpretation, speculation, narrative).

UAP vs. NHI: "UAP" is an identification status (unresolved after analysis), not a synonym for "non-human". When origin is discussed in official writing, it is usually cautious and bounded by what can be supported.

Quick shortcut: search the PDF for "scope", "assumptions", "definitions", "limitations", "data", "appendix/annex".

Many UAP stories return in cycles: a clip gets reposted, a quote gets reframed, or a case is revived with a new headline. The fastest way to stay accurate is to anchor on primary documents and original files.

A quick way to check:

1. Locate the primary: original PDF/transcript/official release, or the earliest known source file.
2. Check what is actually new: new primary material, or only a new edit/narration/repost.
3. Confirm definitions: terms and labeling can shift across time and institutions.
4. Look for stated limits: missing metadata, sensor constraints, redactions, and out-of-scope boundaries.
5. Test the headline claim: find the exact sentence/table/appendix that allegedly supports it.
6. Watch for circular reporting: repeated references that never reach a primary source.

If you cannot trace a statement to a primary source, label it as "claim" rather than "finding".

Testimony is a real category of evidence, but it is not automatically "proof" of a claim. In practice, testimony can be challenged, rebutted, and weighed for credibility.

What "under oath" changes:
"Under oath" increases legal stakes and signals that the statement is being taken in a formal setting. It can reduce casual lying, but it does not guarantee accuracy or completeness.

What it does not change:
People can be mistaken, misremember details, interpret limited information, or describe events outside direct observation. An oath does not automatically provide corroboration.

How to log testimony professionally (UAP / NHI context):

• Separate observation from interpretation: what the person directly saw/did versus what they believe it means.
• Identify proximity: first-hand involvement, second-hand report, or "I heard / I was told".
• Look for corroboration: primary documents, logs, sensor data, and original media with intact metadata.
• Track limits: what the witness explicitly says they do not know, cannot say, or did not verify.

In this archive, "Testimony" is treated as meaningful context that can guide where to look next, but it is not treated as confirmation by itself.

You don't have to "trust" any single institution or community to handle a UAP claim well. This node treats official statements, testimony, and public media as different source types, and keeps uncertainty explicit when evidence is incomplete.

Practical approach: treat every claim (official or not) as one input, then triangulate across independent sources and check what is directly supported versus what is interpretation.

• Separate observation vs. interpretation: log what you directly saw first; add "what I think it was" second.
• Preserve originals: keep one untouched original file (metadata intact) before any sharing or edits.
• Use independent checks: aircraft/satellite/balloon/planet tools can resolve many cases without anyone's "authority".
• Prefer primary material: original files, original documents, original transcripts — avoid circular reporting.

If you want independent, public-document-oriented research, there are long-running FOIA-based archives (example: The Black Vault's document archive). Example archive.

If you want independent case review/investigation outside government channels, some civilian groups do take submissions (example: The Black Vault's TBV Investigations). Example investigation intake. Always read their scope and rules first.

Headlines, podcasts, threads, and documentaries are often the fastest way to discover a story. They are also usually secondary layers: summary, interpretation, and narrative on top of a smaller set of underlying sources. A quick "source check" keeps you accurate without dismissing anyone's work.

Five quick checks (practical):

• Separate claim vs. source: What is being claimed, and what is the closest available primary source behind it (PDF, transcript, official release, original file)?
• Attention vs. validation: High reach means many people saw it; it does not, by itself, tell you whether the underlying evidence is strong.
• Testimony vs. corroboration: A witness statement can be meaningful; treat it as a data point and look for independent corroboration.
• Check definitions: Make sure "UAP" is used as "unidentified after analysis", not as a synonym for origin.
• Keep uncertainty explicit: If the best label is "unresolved", write it that way instead of forcing a conclusion.

When in doubt, use the archive labels as a navigation aid (source type), and try to trace the story back to the earliest and most direct material available.

Image quality and authenticity are separate questions. A high-resolution file may come from a capable camera, synthetic generation, upscaling, or aggressive device processing.

1. Generative fakes:
Photorealistic video can now be generated from prompts. If a striking clip appears with no exact date, no location, no known witness, and no original file, treat it as a claim rather than evidence. High resolution cannot compensate for missing provenance.

2. Smartphone processing vs. real optics:
Modern phones do more than record light. Noise reduction, sharpening, interpolation, and heavy digital zoom can reshape a small distant light into something that looks structured or metallic. This is why an ordinary-looking wide clip with context is often more useful than a dramatic close-up.

The practical filter:
A shaky video with an exact time, location, direction, and original file is usually more valuable than a cinematic clip with no backstory. Start with provenance first, image quality second.

A quick check

• Context: Who posted it first, when did it appear, and can you trace it to an original upload or source file?
• Consistency: Do lighting, motion, reflections, shadows, audio, and scene details behave in a physically coherent way?
• Integrity: Is there an original file, metadata, or any chain of custody, or only reposts, edits, and compressed copies?

Technical clue, not proof:
Content Credentials (C2PA) can sometimes help show where a file came from or whether participating tools recorded edits. They are useful when present, but absence does not prove a file is fake.

If you cannot establish source, date, location, or original file integrity, label the material as unverifiable and move on. The goal is not to dismiss unusual footage, but to keep attention on material that can actually be checked.

Pareidolia is the tendency to see faces, craft shapes, or symbols in random patterns clouds, lights, compression blocks, or sensor noise.

Treat these impressions as "hypotheses", not data points. If the pattern disappears when zoom, contrast, or angle change, it is likely an artifact of perception or processing.

When you expect to see UAPs, drones, or spacecraft, ambiguous lights are more likely to be interpreted that way.

A helpful habit is to write down exactly what you saw before adding what you think it might be.

Human memory is reconstructive, not a video recording. Details like distance, speed, and shape can drift with re‑telling or exposure to new narratives.

Preserve contemporaneous notes and original files. Later edits, captions, and discussions should be logged separately from the initial observation.

In groups, interpretations can converge quickly one confident statement can shape how others remember and describe the same event.

When logging a "multi‑witness" case, invite each person to write a separate description before comparing notes. Divergences are information, not failure.

Resolution rates depend on the reporting population, available sensor data, review method, and the threshold used for closing a case. A percentage from one program should not be applied to a different dataset without checking those conditions.

Many reviewed reports are attributed to aircraft, balloons, atmospheric effects, planets, satellites, or sensor artifacts. Others remain unresolved because the record is incomplete. The archive preserves the rate and wording used by each source rather than presenting one universal percentage.

"Unresolved" usually means that the available data are insufficient to choose between ordinary explanations, not that an extraordinary cause was confirmed.

Without reproducible measurements and primary data, science cannot assign a specific origin. Keeping "unresolved" separate from "extraordinary" protects both believers and skeptics from over‑claiming.

UAP: Unidentified anomalous phenomenon. On this site, the term describes the subject of a report or record; it does not imply that a formal analysis is complete or that the origin is extraordinary.

Unresolved: The available review did not establish a satisfactory identification. This is a data-status label, not an origin finding.

NHI: Non-human intelligence. This is a substantive origin hypothesis, not a synonym for UAP and not an evidentiary status.

Every entry in the Archive carries one of three labels. Labels describe source role and context, not a quality score or proof of origin.

Official: Primary documents, official releases, or institutional records (traceable baseline).

Testimony: Individual claims, whistleblower allegations, and witness statements (unverified by default; see "Testimony" above for how to interpret).

Public context: Selected research, media, or organizer material included when it helps trace a public claim, framing, or recurring discussion. Selection is intentionally limited.

AARO

All-domain Anomaly Resolution Office, a U.S. Department of Defense office.

ASRS

NASA Aviation Safety Reporting System for confidential civil-aviation safety reports.

ATC

Air traffic control.

Chain of custody

A documented history of who held a file or item and what was done to it.

DOPSR

Defense Office of Prepublication and Security Review. Clearance addresses protected information; it does not verify every claim in a text.

FAA

Federal Aviation Administration in the United States.

FOIA

Freedom of Information Act, the U.S. public-records access law.

Metadata

File information such as timestamps, device details, format, or location. It can support review but can also be absent or altered.

NARA

U.S. National Archives and Records Administration.

NHI

Non-human intelligence, an origin hypothesis rather than an evidentiary status.

Primary source

The closest available original record: for example a report, transcript, official release, or original media file.

Provenance

The traceable origin and handling history of a record or file.

UAP

Unidentified anomalous phenomenon. The term alone does not state why something is unidentified or what its origin is.

Unresolved

A review status indicating that available information did not support a satisfactory identification.