Evaluating High-Strangeness Cases: A Practical Scoring Framework (Without Losing the Science)

High-strangeness reports—events that blend unusual motion, odd lights, missing time, “impossible” technology, or deeply personal experiences—have a way of forcing a false choice: either you dismiss everything, or you accept everything. Neither approach helps if your goal is to find the science, not the fiction.

This guide gives you a practical scoring framework you can use to evaluate cases consistently. You’ll learn how to separate physical evidence from testimony, how to spot common failure modes (like over-weighting a single dramatic detail), and how to produce a clear “evidence profile” that stays useful even when you don’t know what happened. The point is not to “debunk” or to “prove”—it’s to rank what’s most worth investigating next.

What counts as “high strangeness” (and what doesn’t)

Working definition (for this framework): “High strangeness” is not a synonym for “untrue.” Here it’s a label for cases where at least one key element is hard to reconcile with ordinary expectations: extreme acceleration, silent hovering close to observers, apparent transmedium motion, inconsistent timelines, poltergeist-like effects, telepathic impressions, or “absurd” coincidences.

That said, a high-strangeness feel can also come from ordinary causes—especially when observation conditions are weak. Bright planets near the horizon, aircraft landing lights, drones, bolides, satellites, camera artifacts, and the normal limits of human memory and perception can all produce compelling experiences. A disciplined framework keeps you from collapsing “weird” into “alien,” or collapsing “mundane explanation exists” into “case solved.”

The core idea: score evidence channels, then score strangeness separately

Most arguments happen because people mix two different questions:

• How strange is the claim? (Does it imply something extraordinary about physics, technology, or consciousness?)
• How strong is the support? (Do we have independent, high-quality evidence that the claimed event occurred as described?)

This framework keeps them separate. You’ll produce two numbers:

• Evidence Strength Score (ESS): how well-supported the event is, regardless of interpretation.
• Strangeness/Impact Score (SIS): how far the best-supported facts depart from ordinary expectations.

A case can score high on strangeness and low on evidence (compelling story, weak support), or moderate on strangeness and high on evidence (boring but well-documented), or—rarely—high on both (the cases most worth careful work).

Step 1: Build a “case file” in one page

Before scoring, write a short, structured case file. In this framework, if you can’t do this, the case is not ready to evaluate.

One-page case file checklist

• Time window: start/end times, time zone, and how those times were established (memory, phone logs, dispatch records).
• Location: coordinates or nearest intersection; viewing direction(s); estimated distances if claimed.
• Witness list: how many, where each stood, whether they discussed the event during/after.
• Primary claims: list as bullet points (e.g., “object hovered,” “shot upward,” “engine stopped,” “triangle shape,” “skin burns”).
• Evidence inventory: photos/video, audio, radar, ADS-B history, weather data, medical records, physical traces, third-party reports, official reports.
• Chain of custody: who has the original files/objects, whether originals exist, and what has been edited.

Step 2: Score Evidence Strength (ESS) across six channels

Score each channel from 0 to 5, then sum for a total out of 30. Use half-points if you must, but try to keep it simple.

ESS Channel A: Documentation quality (0–5)

• 0: No contemporaneous documentation; only later retellings.
• 1: Basic notes later; no timestamps or originals.
• 3: Contemporaneous notes/messages; original media exists; metadata partly intact.
• 5: Originals preserved; clear timeline; corroborating logs; minimal gaps.

What to look for: original photo/video files (not screenshots), raw audio, call logs, dispatch IDs, and whether files moved through apps/platforms that can reduce auditability (for example, through re-encoding or stripping metadata during sharing).

ESS Channel B: Independent witnesses (0–5)

• 0: Single witness with no independent confirmation.
• 2: Multiple witnesses but closely connected and co-located; heavy cross-contamination.
• 4: Independent witnesses separated by distance or role (e.g., motorists + security guard).
• 5: Independent witnesses plus at least one trained observer (pilot, ATC, astronomer) with good notes.

Pitfall: “Many people saw it” is not the same as “many people independently documented it.” Crowd dynamics can synchronize interpretations quickly.

ESS Channel C: Instrumentation (0–5)

• 0: No instrumented data.
• 2: Consumer video only, low light, no reference points.
• 3: Multiple videos from different angles; some calibration possible (stars, buildings, timestamps).
• 5: Independent sensors (radar/IR/optical) with known specs and retrievable raw data.

Important: Sensor data can be wrong for ordinary reasons (clutter, interference, processing artifacts, miscalibration), and the score here is about auditability: whether you can examine how the data was produced and processed.

ESS Channel D: Physical traces (0–5)

• 0: No trace claims.
• 2: Trace claims without documentation or sampling (e.g., “burned grass” photographed days later).
• 4: Time-linked traces with good documentation and controls (soil, vegetation, EM effects).
• 5: Trace + lab analysis + chain of custody + plausible mechanism analysis.

Controls matter: A soil anomaly without comparison samples often can’t distinguish “event effect” from “normal variability.”

ESS Channel E: Official records (0–5)

• 0: None sought or none exist.
• 2: Records exist but are vague or secondhand summaries.
• 4: Dispatch/ATC/police/meteorological records align with the timeline.
• 5: Multiple official sources align and include primary data (not just narrative).

Steel-man both sides: A lack of official records doesn’t demonstrate a cover-up; it can also reflect non-recording, retention limits, or the event not being recognized as significant at the time. When official records do exist, they can sharply constrain timelines and directions.

ESS Channel F: Alternative explanations tested (0–5)

• 0: No alternatives considered; only one favored story.
• 2: Alternatives listed but not checked (e.g., no weather/astronomy/air traffic review).
• 4: Strong alternatives actively tested against the timeline (air traffic, satellites, planets, meteors, drones).
• 5: Alternatives tested and documented; remaining anomalies clearly stated.

Step 3: Score Strangeness/Impact (SIS) on what’s best-supported

Now score strangeness—but only using the subset of claims that are supported by your strongest evidence. Don’t score the most dramatic rumor if the evidence only supports a distant light.

Score each dimension 0–4, sum for a total out of 20.

SIS Dimension 1: Kinematics (0–4)

• 0: Motion consistent with known aircraft/satellites/astronomy.
• 2: Unusual but plausible (rapid turns at unknown distance; drone-like behavior).
• 4: Strongly constrained “impossible” motion given distance estimates and multiple angles (rare; requires good geometry).

Common trap: Without distance, “accelerated instantly” can be an illusion. Distance uncertainty can turn “physics-breaking” into “unknown.”

SIS Dimension 2: Physical interaction (0–4)

• 0: No interaction (pure observation).
• 2: Weak interaction (EM interference claimed but undocumented).
• 4: Documented, time-linked interaction (instrument failure logs, measurable traces).

SIS Dimension 3: Information content (0–4)

• 0: Generic lights; no structured signals or consistent patterns.
• 2: Repeating behaviors suggestive of intent but ambiguous.
• 4: Structured, testable information (e.g., verifiable prediction), documented independently.

This category is where you should be the most conservative. Humans are pattern-finding machines; “it responded to me” is easy to experience and hard to validate.

SIS Dimension 4: High-strangeness experiential claims (0–4)

• 0: None.
• 2: Missing time / intense fear / anomalous perceptions reported but not externally anchored.
• 4: Multiple experiencers report aligned anomalies with some independent anchors (timestamps, third-party observations).

SIS Dimension 5: Broader implications if true (0–4)

• 0: No new implications (misidentification likely; or mundane phenomenon).
• 2: Would imply unknown tech or rare atmospheric event.
• 4: Would imply a significant revision to current understanding (very high bar; extraordinary claim).

Step 4: Place the case on a 2D map (what to do next)

Once you have ESS (0–30) and SIS (0–20), categorize the case by what action makes sense.

Type I: Low ESS / Low SIS (routine noise)

In many collections of reports, you will encounter lots of ambiguous lights, weak documentation, and plausible conventional explanations. Archive them, but don’t spend investigative time unless they cluster with better-documented events.

Type II: Low ESS / High SIS (compelling story, weak support)

These are the cases people argue about endlessly. Your best move is to identify what specific missing evidence would raise ESS: original files, independent witnesses, time anchors, or official records. If you can’t get those, treat it as an experience report rather than an engineering datapoint.

Type III: High ESS / Low SIS (strong data, mild anomaly)

These can be surprisingly valuable. They help calibrate your process, expose recurring misidentifications, and improve your “alternative explanations tested” skill. Over time, they make you better at handling Type IV cases.

Type IV: High ESS / High SIS (priority anomalies)

These are rare and worth careful handling. Preserve originals, replicate checks, and write down the strongest mundane hypothesis and the strongest unconventional hypothesis side by side. Your goal is not to pick a camp; it’s to specify discriminating tests.

Steel-manning: how to fairly compare conventional vs unconventional explanations

A disciplined evaluation gives both sides their best version.

Conventional explanation, steel-manned

• Human perception is vulnerable to distance ambiguity, expectation, stress, and low-light effects.
• Some “impossible motion” impressions can change substantially once distance and geometry are constrained.
• Modern skies include many potential misidentification targets (drones, satellites, high-altitude aircraft), and practical access to tracking/archival data can be uneven by region, sensor type, and time window.
• Video is not “objective” unless it’s calibrated; sensors have artifacts and processing pipelines.

Unconventional explanation, steel-manned

• Some cases include multi-witness reports with time-anchored details, occasionally with instrumented components.
• Rare, genuine anomalies can exist even if many reports are misidentifications (a general logic point in many scientific domains).
• Institutional incentives can discourage careful documentation or public engagement without requiring a coordinated conspiracy.
• Even within established physics, there are open research questions about gravity, spacetime, and extreme environments—though that does not imply engineered “gravity control” has been demonstrated.

Common pitfalls (and how this framework prevents them)

Pitfall 1: “One weird detail” dominates everything

A single dramatic claim (telepathy, missing time, instant acceleration) can overshadow the rest. The split-score system forces you to ask: is this detail actually supported by the strongest evidence channel, or only by later narrative?

Pitfall 2: Treating testimony and physical evidence as interchangeable

Testimony matters—often it’s all you have—but it behaves differently than physical traces or instrumented data. ESS explicitly keeps these channels distinct so you can say, for example, “strong witness independence, weak instrumentation.”

Pitfall 3: Overconfidence from “debunking” a piece of the case

Finding a mundane explanation for one component (say, a bright planet) does not automatically explain the entire timeline. Conversely, failing to find a mundane explanation quickly does not make the event exotic. ESS Channel F rewards documented alternative testing, not rhetorical victory.

Pitfall 4: Time drift and narrative inflation

Stories evolve. Details accrete. The case file’s emphasis on contemporaneous documentation and chain of custody is your defense against “memory archaeology.”

A simple worked example (template you can reuse)

Imagine a report of a silent triangle with three lights hovering over a neighborhood for 90 seconds.

• Case file: time estimated by memory; no exact timestamp; location known; 4 witnesses in same yard; one phone video uploaded to social media; no official reports requested.
• ESS: A=2 (video exists but not original), B=2 (group witnesses together), C=2 (single low-light video), D=0 (no traces), E=0 (no records), F=1 (no serious alt checks) → ESS=7/30.
• SIS: Kinematics=1 (hovering unclear without distance), Interaction=0, Info=0, Experiential=0, Implications=2 (if real structured craft) → SIS=3/20.

Outcome: not a priority anomaly. Best next step isn’t “argue about triangles”—it’s to request originals, establish timeline anchors, and check air traffic and known bright objects for that date/time range.

What to preserve and what to ask for (practical checklist)

• Original media files: not re-encoded, not edited, ideally copied directly from the device.
• Context frames: record the horizon, landmarks, and audio; pan to include stars/buildings for calibration.
• Independent timelines: texts sent during the event, phone call logs, doorbell cams, security footage.
• Environmental context: weather at the time, wind, cloud base, visibility; any power outages.
• Witness separation: independent written statements before extended group discussion, if possible.

If you’re exploring historical or recurring claims around “anti-gravity” and exotic propulsion, use archives as pointers—not as proof. For example, a curated archive can help you find themes and recurring narratives, but it doesn’t replace primary documentation. The Taming Gravity news archive can be useful in that limited way: as a starting place to browse what Taming Gravity has archived and when, before you track down primary sources.

Conclusion: a case can be meaningful without being solved

High-strangeness cases sit at the intersection of perception, culture, and (sometimes) physical anomalies. A scoring framework won’t tell you “what it was.” What it can do is keep your reasoning clean: separate evidence from interpretation, reward testable steps, and prevent the common slide from curiosity into certainty.

If you apply this framework consistently, it can help you aim for two practical improvements over time: fewer hours spent on poorly documented noise, and clearer writeups of whatever remains (what is known, what is claimed, what is ambiguous, and what would change your assessment). That’s the goal—make progress while staying loyal to the principle that matters here: find the science, not the fiction.

Q&A

Why split the evaluation into “evidence strength” and “strangeness”?

Because people often confuse “this sounds extraordinary” with “this is well supported.” Splitting the scores lets you say, for example, “the claim is very strange, but the documentation is weak,” or “the evidence is strong, but the anomaly is mild.” That keeps you from rewarding drama instead of data.

What’s the single fastest way to improve a case score?

Preserve originals and time anchors. Original media files (not screenshots or re-uploads) plus independent time markers (texts, call logs, security footage, dispatch records) often raise the Evidence Strength Score more than any amount of later narration.

Do official records outrank witness testimony?

Not automatically. Official records can be incomplete, mistaken, or absent. But when they exist and are time-linked (dispatch logs, ATC notes, weather records), they can constrain the timeline and location in ways memory can’t. The framework treats them as a separate channel so you can weigh each type of support honestly.

How do you avoid being unfair to experiencers when scoring?

By scoring evidence channels, not character. A low score is not a moral judgment; it just means the event is hard to validate. You can acknowledge an experience as sincere and impactful while still labeling the external evidence as limited.

What does a “high ESS / high SIS” case require to be credible?

It requires multiple independent lines of auditable support: strong documentation, independent witnesses, and ideally multi-sensor or physical trace components with chain of custody. High-strangeness claims that imply extreme physics need proportionately strong constraints on distance, time, and geometry—otherwise they remain ambiguous.