Session identity
A unique record, start time, end time, and total duration.
Invitation App / Deep dive 02
Full Session
Trail
A continuous record connecting the room baseline, every event, every quiet period, the surrounding conditions, the final notes, and the user’s submission choice.
Follow the trail ↓The evidence has a history
Not just what happened.
How we got there.
A full session trail is the chronological context needed to understand an individual result.
A screenshot, word, sound, or sensor change can look important when isolated. The trail keeps the lead-up, exact time, surrounding activity, rules in effect, and what happened afterward. It also preserves the parts where nothing happened.
The standard: A reviewer should be able to move backward from a conclusion to the event, then from the event to the original session conditions.
01 / BEFORE, DURING & AFTER
The life of a session record
- 01
BEFORE OUTPUT
Session identity begins
The app creates the session record, connects the selected room profile, and records the build and available operating context.
- 02
BEFORE OUTPUT
Baseline is established
Normal room behavior is observed before experimental output is permitted, giving later changes something real to compare against.
- 03
DURING SESSION
The invitation opens
The chosen mode, questions, user notes, and opening state become part of the same timeline.
- 04
DURING SESSION
Every event receives a time
Words, question windows, phonetic fragments, visual captures, sound events, and available sensor context are placed chronologically.
- 05
DURING SESSION
Silence remains visible
Gaps, no-response periods, and modes that remain inactive are not removed simply because they are less exciting.
- 06
AFTER SESSION
The invitation is closed
The end state, duration, available radio conditions, and participant notes complete the local record.
- 07
AFTER SESSION
Contamination is documented
Movement, voices, wind, water, notifications, nearby electronics, handling, and other ordinary influences can be marked for review.
- 08
USER CHOICE
The session may be submitted
Nothing is sent automatically. Only the session evidence the user permits is uploaded after the green database button is deliberately pressed.
02 / WHAT TRAVELS WITH THE EVENT
Context fields
The event never travels alone.
The trail joins observable results to the information needed for later review. Exact proprietary thresholds and internal calculations are not exposed.
Room & baseline
The selected room profile and the normal conditions established before testing.
App state
The app build, ruleset version, active mode, and major session-state changes.
Event timeline
Questions, words, fragments, captures, audio events, and no-response periods in order.
Movement context
Available indicators showing when handling or motion may have affected a result.
Sound context
Available microphone activity and preserved recordings relevant to the session.
Radio context
Available Airplane Mode, Wi-Fi, Bluetooth, cellular, and NFC state at key times.
Review context
Participant notes, possible contamination, negative outcomes, and submission state.
03 / REVIEW
Questions the trail can answer
Can someone else follow the evidence?
The purpose is not to make an event look impressive. It is to make the reasoning inspectable.
- Did the baseline finish before the event?
- Which mode and app version were active?
- What happened immediately before and after?
- Was the phone moving or being handled?
- Was nearby sound or radio activity present?
- Were there unanswered questions or silent periods?
- Was a likely ordinary explanation documented?
- Does another independent record align in time?
What the trail cannot answer by itself: the identity, intent, or nature of whatever caused an unresolved event. Better context narrows uncertainty; it does not authorize a leap beyond the evidence.
PRIVACY PROMISE
The session belongs on the device until the user chooses otherwise.
No precise GPS coordinates
No automatic database upload
No unrelated phone information
Green button = deliberate permission
The app does not search through contacts, messages, passwords, browsing history, or unrelated files. When the user deliberately presses the green Download to Paranormal Invites Database button, only the permitted session package is sent.
PUBLICLY REVIEWABLE
What occurred, when it occurred, which conditions were present, and how the conclusion was classified.
PROPRIETARY