Active Android field testing

The Invitation
App

A multi-mode paranormal research environment built to preserve what happened before anyone decides what it means. It records activity, silence, context, and uncertainty in the same evidence trail.

Built for transparent review while protecting the private technology that powers this invitation.

01 / PURPOSE

Research, not entertainment

One environment.
A complete record.

The Invitation App brings several experimental methods into one session so their timing and surrounding conditions can be compared instead of remembered separately.

It does not promise spirit communication, manufacture activity, or turn every unusual reading into a paranormal claim. Its job is to make the session reviewable: establish the room, record the conditions, preserve each result, and keep unanswered questions visible.

WHAT IT IS
  • A controlled multi-mode testing environment
  • A timestamped session and evidence recorder
  • A way to compare events with baselines and sensor context
  • A growing field-research tool under active testing
WHAT IT IS NOT
  • A device that proves the source of an event
  • A guaranteed spirit-conversation system
  • An entertainment app designed to produce constant activity
  • A replacement for human review and competing explanations
02 / RESEARCH MODES

Five ways to observe

Different signals.
One timeline.

Each mode records a different kind of event. None is treated as a conclusion by itself. Their value comes from timestamps, baselines, context, and possible correlation.

02
QA

Ask a Question

Creates a defined question window so the spoken prompt, waiting period, recorded response event, and environmental activity can be reviewed together.

  • User-initiated questions
  • Defined observation window
  • Question and result stay linked
03
PH

Phonetic

Preserves app-generated phonetic fragments and timing for longer trials. These outputs are not captured speech or EVP recordings. If no sound is produced, that does not mean the sensors were necessarily inactive: below-threshold activity can still remain in the record for comparison. Review happens after the session so ambiguous sounds are not forced into words in real time.

  • Generated fragments retained
  • No-response sensor context retained
  • Interpretation stays separate
04
SLS

SLS Vision

Maps human-like geometry in the camera view and can preserve still captures or recordings when a possible figure appears, while keeping the original scene visible.

  • Original visual context retained
  • Detection captures can be reviewed
  • False mapping remains a live explanation
05
EV

Session Evidence

Connects the session’s events with baselines, motion, microphone activity, radio state, app version, notes, and submission status for later review—including sensor changes that did not reach an output threshold.

  • Room-specific baseline
  • Contamination context
  • Outputs and below-threshold activity preserved
03 / SESSION FLOW

From room to record

How a session
moves through the app.

  1. 01

    Choose the room

    Use an existing room profile or establish a new baseline for the current environment.

  2. 02

    Record the baseline

    The app observes normal room conditions before experimental output is allowed.

  3. 03

    Open the invitation

    The user begins respectfully, selects a mode, and records questions or observations.

  4. 04

    Preserve events and context

    Outputs, timestamps, motion, sound conditions, and available radio states remain attached.

  5. 05

    Close the session

    The invitation is formally closed and the full session—including no-response time and available below-threshold sensor activity—is saved.

  6. 06

    Review and submit once

    The record can be examined and submitted to the research collection without duplicate submission.

04 / THE RECORD

What travels with the event

A result without context
is only a result.

The app is being built so a reviewer can trace an event backward—from the final interpretation to the original capture and the conditions present when it occurred.

01

Time

Event and session timestamps

02

Baseline

Normal room profile and state

03

Movement

Phone and session motion context

04

Sound

Microphone levels and audio events

05

Radio state

Available Wi-Fi, Bluetooth, cellular, Airplane Mode, and NFC state

06

Version

App build and decision-rule version

07

Outcome

Words, questions, phonetics, captures, no-response periods, and below-threshold sensor activity

08

Review notes

Contamination and alternate explanations

PUBLICLY EXPLAINED

What the app observes, which context it preserves, how sessions are classified, and why a result remains unresolved.

PROTECTED BY DESIGN

Source code, exact thresholds, internal weighting, selection logic, dictionary structure, security credentials, precise location, and private tester data.

Location privacy: The research design avoids precise public GPS. Coarse regional information is optional and used only when appropriate for broader pattern analysis.

05 / OPERATING OBSERVATIONS

Examples from testing

Interesting records.
Careful conclusions.

These are examples of what has appeared while the app has been operating. They are not presented as proof of spirits. Each remains subject to source review, contamination checks, repetition, and independent analysis.

Example 02 / Question windows

A strong response pattern

An investigator-reported operating example describes outputs following 10 of 11 question windows. The underlying session is not supplied in this public example. That timing pattern is worth preserving and repeating, but frequency alone does not establish who—or what—caused the outputs.

STATUS: REPORTED TIMING PATTERN
Example 03 / Negative evidence

A quiet outdoor run

A field test at a public park produced little or no meaningful activity. The session was kept rather than discarded, giving future comparisons an honest null result.

STATUS: PRESERVED NULL SESSION
Example 04 / Contamination

A poolside session

Activity recorded around water, movement, nearby voices, and changing conditions was treated as contamination likely. The data remains useful for learning how the system behaves in a noisy environment, but not as strong evidence.

STATUS: CONTAMINATION LIKELY
06 / WHAT TESTING HAS TAUGHT US

The app improves by being questioned

The strongest result
is the one we can audit.

01

Baselines must come first

Normal room conditions need to be established before any output can carry meaningful context.

02

Movement changes interpretation

A phone being handled, repositioned, or bumped can alter sensor and visual readings.

03

Radio state belongs in the record

Online and controlled-offline sessions should be distinguishable, with actual connectivity conditions preserved.

04

No response is still data

No qualifying word or phonetic sound does not prove the sensors were inactive. Preserved below-threshold readings help establish ordinary behavior and show how sensor patterns compare with sessions that did produce an output.

05

Software behavior must be explainable

Unexpected app behavior is investigated, corrected at its cause, and prevented from quietly influencing future results.

07 / CURRENT STATUS

Controlled tester program

Built in the field.
Reviewed after every run.

The Invitation App is currently in controlled Android field testing. Work is focused on stable capture, reliable evidence history, one-time research submission, SLS and audio consistency, and clear review states. An Apple/iPad version is planned but is not part of the current public tester build.

Android Active field testing

Apple / iPad Planned

Public release Not yet open

NEW / VERIFIED SNAPSHOT

See current intake totals and reviewed session examples.

Open live anonymous counts, the dated October 4 snapshot, and reviews of submitted sessions.

Open the database record →
08 / STRAIGHT ANSWERS

No inflated promises

What people should
understand clearly.

Does the app prove spirit communication?

No. It records events and context. The cause of an unexplained event remains unresolved unless the evidence can support something more specific.

Does it guarantee activity?

No. The app is not designed to produce scheduled entertainment or guarantee responses. Quiet sessions are expected and preserved.

Why protect the internal logic?

Protecting intellectual property and preventing test-gaming does not require hiding the evidence. Reviewers can still examine what happened, when it happened, and which conditions were present.

Can anyone download it now?

Not yet. Current builds are distributed through a controlled Android tester program while reliability and research safeguards continue to be evaluated.

Paranormal Invites™

We don’t chase.
We invite—and we preserve.

Return to technology →