The Odds of getting three Triangles in Genesis 1:1 & John 1:1

[Alex]

161 "the universe" היקום
= Lucky-o(1053 "and the earth" (H & G s)) = Palin(26 "codes" (E rr)) = Octagram(5 = PP-o(37 "of wisdom"))
= Palin(26 "Alpha" (G rr)) = 3 digits of φ
= "seven, thirty and seven, seventy and three, seven hundred seventy and seven" שבע שלושים ושבע ושלשה שבעים שבע מאות ושבעים ושבע (Sr)

1141 "the universe" το συμπαν
= C.Hex(20 "Alpha" (E r)) = 163x7 [1637 = TV of Vs(1618 (φ))] = 141 "Alpha and Phi" Αλφα και Φι (ro) w. ext… = 800 + 341 "Alpha and Phi" (G Fo)
= 7+7+7 + 7x7x7 + 777 = "codes" (H & G ro+rs) [κωδικους]
= FLW of Vs(1077 = C.TriHeptagram(7) + C.TriHeptagram(7) + C.TriHeptagram(7))

[Alex]

Isn't it wonderful that I discovered that probaility of 31.8 billion on the date of 3/18? It's almost like it was meant to be.
remember that I posted it one hour before it became that date in USA. But we are some hours ahead of you guys over there so it was on the date of 3/18 here in Norway. I did not notice this until now.

318 "the fine-structure constant" (E o) = Comp(251 = prime factor of rs Vs(777))

[RAMcGough]

Here is the summary of what Grok say about this:

Alex's raw data (the 13,847 pair count) is cool and shows these triple-triangle integrations really are uncommon in the full combinatorial space—props for doing the exhaustive check. But the final "1 in 31.8 billion" figure is classic overstated Bible-numerology odds. It looks impressive but doesn't survive basic statistical scrutiny because of selection bias and multiple testing. It's confirmatory for someone already convinced of hidden patterns, but it isn't evidence of intentional design any more than finding a rare word combination in Shakespeare after searching every possible pair.
If the program/code and exact definitions of "integration" and the triangular checks were shared, it would be even easier to verify or extend (e.g., how many hits for other shapes like squares?). But as presented, it's a good example of why raw rarity numbers in gematria studies need heavy caveats. The preceding post in the thread was right to suggest getting an AI (or statistician) to review it!

I have to remind readers that the word "proof" is very academically loaded word. They require a lot from you before you can call something proof.
I have simply showed the chance of getting these Triangles using the Bible itself as a source. That does not count as imperical proof, but the chance shows us that this has to be design in my opinion. Let me remind you that the academic communty and science community has mostly been against God, and I believe they have loaded the word "proof" with a lot of requirements just to make it hard for people to prove anything regarding the Bible.
When Ivan Panin presented his work, no one really tried to attack him from the academic community at that time as far as I know.
But I guess the academic community decided to never let another Bible codes prove anything again. And they have succeeded when you look at what Grok says here.

Alex,

Grok has explained you error the same way I have. You are not doing the stats correctly. It has absolutely NOTHING to do with any bias on the part of academia. It's basic math.

Now it's true that most people in academia are strongly biased to reject numerology, but there's a very good reason for that. The history of numerology is exemplified by your work which is a textbook example of CHERRY PICKING. Forget the example of three triangles in G1:1/J1:1. That's a tiny drop in the ocean of cherry picked "connections between random numbers that you buried it under. You even connect the statistical estimates (like 31.8 million) with the date you found that fallacious number! Any competent mathematician will immediately recognized your work as self-evidently absurd.

Here's a detailed explanation of your primary error from Grok. It says the probability of you finding such patterns by random chance is about 100%! This is what I've been trying to tell you. Using your methods, you can connect anything to anything with near 100% probability. This is why your "codes" are utterly meaningless.

GROK SAYS: The probability of Alex's 3766 pattern (and the chain of equalities it belongs to) occurring purely by chance cannot be calculated naïvely (e.g., “the odds of four random numbers summing to exactly 629 is 1 in millions” or “1 in 3766 that two big numbers match”). Such naïve figures are statistically worthless because they ignore the extreme flexibility and post-hoc selection built into Alex’s own system. He only publishes the configurations that work; he does not report the vastly larger number that do not. This is the classic “researcher degrees of freedom” / multiple-testing / data-dredging problem that invalidated many early Bible-code claims in the peer-reviewed literature (see the 1994 Torah-codes paper and its Statistical Science rebuttals by McKay et al.).

A **rigorous** probability (or p-value) must follow the same standards statisticians applied to those Bible-code controversies: either an **a-priori-defined Monte Carlo simulation** that fully models Alex’s search process, or a careful analytical estimate of the effective search-space size. Below is the exact protocol one would use.

### 1. Fix the search space in advance (a-priori protocol)
Using only the rules published on Alex’s own site (https://777codes.com/index.php/introduc ... -gematria/) and the forum post itself, enumerate every allowed choice **before** looking at any numbers:

- **Gematria variants** (≥15 documented): standard, ordinal, reduced, reverse standard (rs), reverse ordinal, reverse reduced, full reduced (Fr), full ordinal (Fo), full standard (Fs), soft variants, starter (sr), and explicit combinations such as (o+s) — the exact method used for the four constants. Each can be applied to English, Greek, or Hebrew spellings.
- **Spellings of constants** (dozens of options per constant): English “alpha” / “pi” / “e” / “phi”, Greek full Αλφα / Πι / Φι, symbol-only, full phrase (“fine structure constant”), digit strings turned into text, etc.
- **Number and identity of constants** (hundreds of combinations): exactly these four (α, e, π, φ) or any 3–5 from the dozens of well-known constants (γ, τ, √2, etc.).
- **Polygonal parameters**: n (the index) from 3 to 100 (or higher);
- **Bible-side structural methods** (≥50 documented): CW (center word(s) — add if two), TV (total value), FLW, FLCW, CL + CW, 3/4 CW, verses-by-rotation, happy numbers, digit-extension, +1 method, 0-removed, merging, etc. Plus the exact rule for “&” (concatenate the two verses? sum their separate CWs? special composite?).
- **Gematria on the Bible text**: Eng rs (the one used here), or any of the other 15+ variants, applied to any verse pair (not just Gen 1:1 & John 1:1).
- **Extra layers** in the actual post (verse-order matching decimal digits of the constants, 777-digit additions, happy-number wrappers, etc.).

Even a conservative lower-bound estimate of the total configurations S is 10⁵–10⁷ (e.g., 15 gematria types × 20 constant combos × 30 n values × 40 Bible structures × 50 verse-pair choices). The forum thread and Alex’s site contain hundreds of published patterns, so one must also multiply by the number of independent tests he performed.

### 2. Define the null hypothesis and the test statistic
Null: the two sides (math/constants side and Bible side) are completely independent; any apparent equality is random coincidence.
Test statistic: whether the final number produced on the math side (after applying the chosen gematria to the constants → s → polygonal(n,s)) exactly equals the number produced on the Bible side for that same configuration.

### 3. The gold-standard method: Monte Carlo simulation
This is the method actually used to debunk overstated Bible-code probabilities.

**Procedure** (implementable in Python/R with Alex’s exact letter-value tables from the glossary):
- Repeat N = 10⁶–10⁸ times (large enough for precision):
- Randomly sample one full configuration from the search space above (uniformly, or weighted by how often Alex uses each method if known).
- Compute the Bible-side number T exactly as Alex’s rules allow (using real KJV text but the randomly chosen structure/variant).
- Independently compute the math-side number: apply the randomly chosen gematria/spelling to the randomly chosen constants → get s → compute P(s,n).
- Record a “match” if the two final integers are identical (and, for extra strictness, if the whole chain of further equalities in the post also holds).
- Empirical p-value = (number of matches + 1) / (N + 1).

This automatically gives the correct probability that a pattern “as impressive as 3766” would appear by chance when searching exactly the way Alex searches. It handles all dependencies (non-uniform distributions of gematria sums, the linear 6s−8 shortcut for n=4, the exact range of CW values in reverse-standard English, etc.).

### 4. Analytical approximation (when full simulation is impractical)
If one cannot code the entire system, a rough but defensible order-of-magnitude estimate is:

p = S/R

where:
- S = size of search space (as above, ≥10⁵),
- R = number of distinct possible output values the final number can take (typically 1 000–10 000 for these codes; CW sums in rs-English for short verse combinations rarely exceed a few thousand, and polygonal values for small n cluster in the same range).

Even with the most generous assumptions (S = 10⁴, R = 5 000), the adjusted probability is already ~1–10 % — nowhere near the “astronomically small” claim implied by the raw match. Once one includes the hundreds of other patterns Alex has published in the same thread, the probability of finding “something this good somewhere” approaches 1 (i.e., expected under pure chance).

### 5. Additional corrections that must be applied
- **Post-hoc flexibility**: The post itself does not show the raw calculations that produced the individual 2 + 10 + 96 + 521 = 629 values; those were also chosen to fit. The simulation must therefore allow the same freedom for the constant gematria step.
- **Multiple patterns in one post**: The 3766 line is only the first of six chained equalities. The joint probability of all six matching simultaneously must be computed.
- **Selection of verses and constants**: Gen 1:1 & John 1:1 and the four physics constants are famous; one must include the fact that Alex could have picked any other pair of “beginning” verses or any other quartet of constants.
- **Published output**: Alex has an entire website and forum thread full of similar codes. The relevant p-value is the probability of finding at least one 3766-level hit anywhere in his published work.

### Practical conclusion
Without Alex publishing the complete list of every configuration he tried (and failed) before posting this one, the most accurate statement possible is: “When the full flexibility documented in his own glossary is modelled via Monte Carlo, the probability is on the order of several percent to near-certainty — exactly as statisticians found for earlier Bible-code claims that initially looked miraculous.” The pattern is impressive craftsmanship within a very large search space, but it does not survive a properly adjusted probability calculation.

If one wanted an exact numerical p-value, the next step would be to implement the Monte Carlo in code using the precise letter-value tables and abbreviation rules from https://777codes.com/index.php/introduc ... -gematria/ and the forum post itself. That is the only method accepted in the statistical literature for claims of this type.

[Alex]

Richard. you know that you are not exactly fit to judge if my codes are cherry picked. You are talking to someone who has done level 100 codes here.
When will you understand that?

your work which is a textbook example of CHERRY PICKING

And you said Jesus did not want you to judge these codes after the academic standard. So go pray to Jesus and ask him if I am cherry picking.
He knows better than Grok.

Peace and blessings to you my friend.

[Alex]

11749 = TV of Vs(28 = Tri(7)) + TV of Vs(703 = Tri(37)) + TV of Vs(2701 = Tri(73))
2314 = TV of Vs(777)
7+37+73 = 117 "seven hundred seventy and seven" (E r) = "the seal of God" (E o)

The only verse we can integrate with verse# 2314 to get Triangles in the reduced, ordinal & standard values is verse# 11749.
Here are the Triangles when we integrate verses ordered at 11749 & 2314:
red = 435 = Tri(29 "and" ואת (o))
ord = 1128 = Tri(47 "inverse Alpha" αντιστροφος Αλφα (r))
std = 6555 = Tri(114 "the universe" το συμπαν (o))
29+47+114 = 190 = Tri(19 "codes" (E r))

[Alex]

137 = inverse α
7209 = 729 (α) with 0 removed = ro+rs Vs(1918 = φ w. upsidedown digit) = 3/4 CW of verses ordered at the primes reflecting the 7 words of Gen 1:1

Integration of verses ordered at 137 & 7209
red = 276 = Tri(23 = Pri(3+7)) = Lucky(21) + Lucky(37) [21x37 = 777]
ord = 780 = Tri(39 = factor of 156 "universe" יקום)
std = 5460 = Tri(104 "and the earth" (E o))
23+39+104 = 166 = C.Tri(11 = Lucky-o(37)) = Semiprime(55 = Tri(3+7) = Hepta(5 = PP-o(37)))
= PP-o(2293 = 4 digits of 7246/316) = ord Vs(3572 = C.TriHeptagram(7+7+7))

316 = C.Tri(15 = Tri(5 = PP-o(37)) = C.Hepta(3+7)) = 2x(158 = C.Tri(3) + C.Hepta(7)) = FLCL of Vs(37)
7246 = C.Tri(70 "seven hundred seventy and seven" (Sr)) = C.Hepta(46 "codes" (E o))
Triangles have 3 sides & Heptagons have 7 sides.
37 = code number for 777 = prime factor of 777 = first word of Vs(117 "seven hundred seventy and seven" (E r)) = first word of Vs(777)

CW of Vs(777) = 316
TV/FLW/CW/FLCW of Vs(777) is 2314/197/316/513 = 0.00007245905 ≈ 0.00007246

316 as a Centered Triangle

C.Tri(15).png (128.18 KiB) Viewed 3756 times

7246 as a Centered Triangle

C.Tri(70).png (377.08 KiB) Viewed 3756 times

[Alex]

726 = 729 (α) with an upsidedown digit
5471 = Pri-o(53657 = prime factor of 7297352 (α))

Integration of verses ordered at 726 & 5471
red = 435 = Tri(29 "and" (H o))
ord = 1326 = Tri(51 "seven seven seven" επτα επτα επτα (r) = Pri(8) + Pri(8) + Pri(8))
std = 8778 = Tri(132 = 39+93)
29+51+132 = 212 = 7+7+7 merged with mirror

39 = code number for 999 "Jesus" Ιησους (r+o+s)

[Alex]

1628 "seven hundred seventy and seven" שבע מאות ושבעים ושבע (rs) = 1000 + 2x314 [2314 = TriHeptagram(18) = C.TriHeptagram(17)]

Integration of verses ordered at 316 & 16280
red = 276 = Tri(23 = mirror of (32 = Lucky orders added of 7, 37 & 73)) = Lucky(21) + Lucky(37)
ord = 861 = Tri(41 "universe" (E r))
std = 6441 = Tri(113 "universe" (E o))
23+41+113 = 177 = (17 "the universe" היקום (r) = "and" (E rr)) w. ext... = "seven seven seven" επτα επτα επτα (ro)

[RAMcGough]

Richard. you know that you are not exactly fit to judge if my codes are cherry picked. You are talking to someone who has done level 100 codes here.
When will you understand that?

Peace to you Alex, and grace in our Lord Jesus Christ.

Anyone with a functioning brain can easily recognize cherry-picking. It's not about "level 100 codes" — it's basic logic.

Cherry-picking means: You only show the hits that look amazing, while quietly ignoring (or never mentioning) the vastly larger number of similar attempts that failed.

How to spot it here:

1. Your search space is enormous — trillions of possibilities.
   • 3 languages (Hebrew ~307k words, Greek ~138k, English ~783k)
   • Single words, phrases, names, rotated strings, key concepts
   • 15+ gematria variants (red, ord, std, full, reverse, o+s, etc.)
   • 50+ structural methods (CW, FLW, +1, 0-removed, ultra calc, rotations, etc.)
   • 20–30 "success" types you accept (any polygonal, centered, perimeter, happy, lucky, prime, 777 factors, composites, semiprimes, etc.)
   Multiply those → easily 10¹¹ to 10¹³ configurations (hundreds of billions to trillions).
2. You spend your time trawling through that ocean of random numbers until you find a pretty match (three triangles, heptagonal perimeter = 777, happy.pri combo, etc.).
3. You publish only the winners and claim astronomical odds based on the final numbers — without ever showing (or counting) the misses.

That is textbook cherry-picking.

The patterns may be creative and fun to find, but they are exactly what you get when you exhaustively search a trillion-to-one space and only report the cherries.

your work which is a textbook example of CHERRY PICKING

And you said Jesus did not want you to judge these codes after the academic standard. So go pray to Jesus and ask him if I am cherry picking.
He knows better than Grok.

Peace and blessings to you my friend.

I'm glad you brought up our Lord Jesus! He's what really matters. I do believe He designed His Word with endless patterns beyond anything any one of us could imagine. The most significant pattern is the large-scale thematic unity of the grand narrative from Genesis to Revelation, aka THE GOSPEL OF JESUS CHRIST, THE SAVIOR OF THE WORLD.

Then we see many typological patterns like Abraham's sacrifice of Isaac in Gen 22 and the great Psalm of the Cross in Psalm 22 (Cross = Tav = 22nd letter that completes the alphabet just as Christ said "It is finished" on the cross). Here we see the commonly understood typology reflected in the structure of the Bible and the Hebrew Alphabet. This is a hint of the infinite glory God encoded on this level.

Then we see the basic pattern of the 7 = 6 + 1 = 2x3 + 1 days of creation echoed in the pattern of the seven branches of the menorah and the structure of the cosmos (3D axes project onto a star with six rays, looking like the Iota Chi monogram of Jesus Christ, the creator of all. God used this pattern in the design of the Canon Wheel (the seven divisions of scripture arrayed to create the tri-radiant halo of traditional Christian iconography). It is infinitely deep and profound.

And then we see this hexagonal symmetry emerge from the alphanumeric structure of the actual text of Genesis 1:-5 + John 1:1-5.

This coherent coding goes on forever and ever. The Bible is a portal to the Mind of God.

Now as for the will of Christ concerning claims about patterns in His Word: I rejoice if anyone has their nose in His word. I believe He told me to "put down my sword" and speak with peace, grace, love and humility, and to allow for the idea that the diverse "patterns" people see may be like "numerical tongues" by which they speak to God and edify themselves, as it is written:

1 Cor 14:1 Pursue love, and desire spiritual gifts, but especially that you may prophesy. 2 For he who speaks in a tongue does not speak to men but to God, for no one understands him; however, in the spirit he speaks mysteries. 3 But he who prophesies speaks edification and exhortation and comfort to men. 4 He who speaks in a tongue edifies himself, but he who prophesies edifies the church. 5I wish you all spoke with tongues, but even more that you prophesied; [a]for he who prophesies is greater than he who speaks with tongues, unless indeed he interprets, that the church may receive edification.

Alex, you are making claims about math. I am answering those claims. I am not criticizing the fact that you feel "edified" by your patterns. I'm only talking about their INTERPRETATION and IMPLICATION for the EDIFICATION of the Church, the body of Christ.

Grace to you Alex, and peace in our Lord Jesus Christ,

Richard

[Alex]

Look at the great works of God Richard.

2011 = 7+7+7 w. 0 rem. & ext... = orders added of the 7 Triangles in verse# 137 w. 0 rem.

Integration of verses ordered at 1625 "777" (H s) & 2011
red = 325 (302253 = Tri(777)) = Tri(25)
ord = 946 = Tri(43 "α, e, π, φ" (o))
std = 5356 = Tri(103 "universe" (E ro))
o+s = 6302 = TriHepta(46 "codes" (E o))
r+o+s = 6627 = Rhombus Tri(47 "of God" (E o))

And I have not mentioned anything about definitive proof here. I have said what I believe about this stuff.
And I have provided fair odds of those three & seven Triangles.

17012 = 1000 + CW of 777 Holograph with 0 removed

Integration of verses ordered at 1625 & 17012
red = 276 = Tri(23 = mirror of (32 = Lucky orders added of 7, 37 & 73)) = Lucky(21) + Lucky(37)
ord = 780 = Tri(39 "inverse" (H o) = "Alpha" (G Fr))
std = 4560 = Tri(95 = Pri-o(491 = CW of Vs(302253 = Tri(777))))
23+39+95 = 157 = Pri(38 = code number for 888)

Verses ordered at 2011 & 17012 are the only verses we can integrate with verse# 1625 to get Triple Triangles in the reduced, ordinal & standard systems.