Research profilesZenodoYouTubeORCID
Reflective Time ModelRTM Research Platform
RTM FINDINGS · DOCUMENTED CASES & CONTROL TESTS

RTM Findings — Selected Case Studies from the Research

This page brings together selected case studies from the RTM research. Each case begins with a documented source record — a message, timestamp, date, image, text, or external datum — and proceeds to the anchors, closures, and relationships found around that record.

The presentation is designed to keep separate what was fixed or documented beforehand, what was derived by calculation, and what was tested with controls. Some cases also include null models, simulations, and search-aware stress tests.

Documented sourceEvent, image, message, timestamp, or external datum
Closure architectureAnchors, representations, and numerical routes
Methodological controlsNull models, simulations, and sensitivity tests where applicable
Reading key: Fixed defined before calculation · Derived generated from the data · Target check known fact used to verify the return.
What is shown on this page?This is an entry point into the wider RTM research corpus. Each card presents a selected case — not the entire dossier — and links to a page where the source record, chronological context, anchors, calculations, and relevant controls can be inspected. Cross-case structural patterns are presented only after the individual cases.
SELECTED CASE STUDIES

Selected case studies

Each card is a gateway to a documented case: source, chronology, architecture, and controls where available.

Visual source · 7 documented examples

Real-Time Records

Seven cases in which the source record was preserved before calculation. Each case presents source, chronology, anchors and closures, with Null controls where applicable.

7documented casesSource firstrecord before calculationAuditcase-specific controls
Open Real-Time Records →
Documented event · 6/6 · Exact Null · 17 Dec 2021

Wedding finding — ketubah, identity and date

Six dependency-compressed core structures link the event questions, identities, 17.12, the year 2021 and the ketubah. Two central convergence nodes are each supported by three separate routes — 2337 and 810 — and are evaluated together in the Exact Null.

6/6core structures3 + 3routes to 2337 and 810Exact Nullp ≈ 1.06×10⁻¹⁶
Open the full wedding network →
Location event · 16 Sep 2026

Albania — Plaza Tirana

Amir Harpaz and Ayala Cohen Shapira stayed in room 1602 on floor 16. The date and two identities converge on 4083, the location-description value, and the node returns to both identities.

1209 + 1609 + 543 + 722 = 4083
Open the Albania case →
Physical object · 2000 → 2025

The Living Subscriber

Two identifiers printed on a 2000 membership card connect to complete-week counts derived from two 2025 measurements. The first route reaches 1312 and returns to 4262; the corrected measurement also returns 4819. The core uses no gematria.

2000: 4819 · 4262 ↔ 2025: 1312 · 1316
Open the case →
Timestamped sequence · 14 → 15 July

14–15 July 2026

2378 is present in the archived 14 July network; on the next day it becomes the exact value of the full date phrase. The declared gates are then scanned across the full date range.

14 Jul: 2378 → 15 Jul: date phrase = 2378
Open the July sequence →
Cross-case series · Titanic · 9/11 · Ford Capri

Historical Events

Titanic, 9/11 and Ford Capri are presented from simple to complex. Titanic now opens with two short foundation closures — 659 → 956 → 1912 and 846 + 62 + 116 = 1024 — before moving to the deeper Millvina Dean network: 2 February 1912 → 972, the 1912 ↔ 1718 loop, and the 11100 → 1509 convergence.

659 → 956 → 1912 · 846 + 62 + 116 = 1024 · 972 · 1912 ↔ 1718 · 1509
Open Historical Events →
Patterns across cases

The same structural families recur across different cases

The same structural families recur across several RTM case files. Comparison comes only after each case states its source, fixed inputs and calculation.

Multiple paths → same targetMulti-path convergence

Different source routes terminate on the same target or internal node.

Albania · Living Subscriber · Ford Capri

Question → answerQUERY RECONSTRUCTION

The numerical form of a question participates in reconstructing its answer, time or identity.

Titanic · 9/11 · Ford Capri

Identity / role reconstructionIdentity / Role

The network returns the person, name or role that belongs to the event.

Albania · 9/11 · Ford Capri

Cross-representation closureNUMBER ↔ WORDS ↔ DATE

The same information moves between numeric form, number words, date or gematria and meets again.

Living Subscriber · Titanic · 9/11

Loops and chronologyLOOPS & RECURRENCE

An output returns to an earlier node, or later information reconstructs an earlier state.

Living Subscriber · 14–15 July
Validation remains a separate layer.

Observer replacement, role sensitivity, exhaustive enumeration, Monte Carlo, Null models and dependency compression are pressure tests — not case categories.

How to read each case

EventWhat happened
SourceWhat was fixed or documented
DerivedWhat was deterministically computed
NetworkWhat closes and where it returns

This order keeps chronology and researcher degrees of freedom visible. Only then do we compare cases and move to pressure tests.