Typed input
Numbers, Hebrew text, dates, times, identities, roles and sources.
RTM Lab takes records, text, identities, dates and times; reconstructs Evidence, finds structures in Discovery, builds a dependency-aware network, and runs null-model tests to compare the observed network with alternative worlds under the same search freedom.
The engine separates finding relations, building topology and testing extremeness. You can see not only what was found, but where it came from, what it depends on, and what happens when null worlds receive the same search contract.
Numbers, Hebrew text, dates, times, identities, roles and sources.
Legal paths are checked against frozen targets with an audit trail per closure.
New structural relations are searched under the same locked search rules.
Closures become a network of nodes, families, bridges, convergence and dependency.
Manifest and validation tools separate source, representation, computation and interpretation.
Alternative worlds run through the same search contract and are compared structurally.
Inputs, network, provenance and test settings can be retained for reproducibility.
A network-level result asks how many independent evidence units remain after deduplication, how many distinct families connect, how many anchors are covered, and how the largest connected component is organized.
Algebraically or semantically dependent paths are not automatically counted as independent evidence.
Sender, recipient, date, time, text and core anchors can receive different event-model rules.
The structural statistic considers component size, family diversity, anchor coverage, arity and convergence.
Null worlds are not handed the observed equation. They receive the same rules and search from scratch.
Fixed variables, resampled variables, transformations, seed, world count and observed signature are preserved.
A separate tool searches verses, words and contiguous phrases without automatically turning the result into Evidence.
RTM Lab keeps Standard, Strict and Super-Core profiles separate, including at the statistical stage.
Full search under the active search contract.
A fixed profile with reduced search freedom.
The hardest core of the locked search rules.
The event-level structural test.
R44 freezes the rules of the game, not the observed equation. The engine declares what is fixed and what may vary, generates an alternative event world, runs the same discovery process, and compares that world's best network against the observed signature.
When many values, representations and operations are available, chance can produce attractive relations. RTM Lab attempts to price that search freedom inside the null model.
RTM Lab keeps raw inputs, computation, topology and statistical inference conceptually separate, making it easier to reconstruct what actually contributed to a result.
Each anchor can be fixed, variable, dependent or derived, with an explicit role.
Seed, ranges, null model, world count, search contract and observed signature are recorded.
Exports support reconstruction outside the session in which the result was discovered.
Once Find and statistics have completed, RTM Lab can pass RTM AI a frozen Audit package containing the inputs, anchors, closures, network structure, provenance and Null results. The AI layer does not replace the deterministic engine; it analyzes the already-computed finding and returns a structured research report.
No. Gematria is one representation type. The central object is an information network made of anchors, roles, paths, dependencies, topology and null-model tests.
This overview is public. The full compute environment and its API are access-controlled, separating public methodology from private research compute.
No. It provides infrastructure for reconstruction, audit and extremeness testing under declared models. Moving from statistical anomaly to a theoretical claim requires additional evidence, confirmatory prediction and external replication.
Profile Score summarizes search characteristics under a profile. Full Network evaluates the structural signature after dependency deduplication. They answer different questions and are reported separately.
The public page explains the methodology; the full engine remains a private, authenticated research environment.