<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									Zodiac Cipher Mailings &amp; Discussion - Zodiac Discussion Forum				            </title>
            <link>https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/</link>
            <description>Zodiac Killer Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Sun, 22 Nov 2026 14:23:53 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>Z13: A Repeat-Distance Construction Yielding</title>
                        <link>https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/z13-a-repeat-distance-construction-yielding/</link>
                        <pubDate>Mon, 05 Oct 2026 21:52:03 +0000</pubDate>
                        <description><![CDATA[A repeat-distance construction in Z13 that yields HELLO
I want to present a structural observation in Z13 that produces HELLO.
I am not claiming that this proves a unique solution to Z13. ...]]></description>
                        <content:encoded><![CDATA[<h2>A repeat-distance construction in Z13 that yields HELLO</h2>
<p>I want to present a structural observation in Z13 that produces <strong>HELLO</strong>.</p>
<p>I am <strong>not</strong> claiming that this proves a unique solution to Z13. Z13 is too short for that kind of claim. What I am claiming is narrower: there is a simple and reproducible construction based on the repeated symbols and their positions which, under a small set of explicit assumptions, yields HELLO.</p>
<p>The construction has also been tested against alternative rule choices and randomized Z13-like layouts. Those tests do not prove intent, but they indicate that HELLO is not simply an inevitable product of a highly flexible procedure.</p>
<p>The method does not require a proposed name, an anagram, a dictionary search, Grandpré, Gromark, Poe, Marsh, or any other proposed plaintext.</p>
<h3>1. Start only with the symbol pattern</h3>
<p>The 13 positions of Z13 can be represented as:</p>
<p>A – E – N –  –  – K –  – M –  –  – N – A – M</p>
<p>To study the repetition without assigning plaintext values, label each new symbol in order of first appearance:</p>
<p><code>1 2 3 4 5 6 5 7 5 8 3 1 7</code></p>
<p>These class numbers are only labels. They have no numerical role in the calculation.</p>
<p>There are eight distinct symbol classes in total.</p>
<p>Four repeat:</p>
<ul>
<li>class 1 at positions 1 and 12</li>
<li>class 3 at positions 3 and 11</li>
<li>class 5 at positions 5, 7 and 9</li>
<li>class 7 at positions 8 and 13</li>
</ul>
<p>The remaining four classes — 2, 4, 6 and 8 — occur only once.</p>
<h3>2. Measure the repeat distances</h3>
<p>Reading from left to right, the repeat intervals are:</p>
<p><code>1 → 12 = +11</code></p>
<p><code>3 → 11 = +8</code></p>
<p><code>5 → 7 = +2</code></p>
<p><code>7 → 9 = +2</code></p>
<p><code>8 → 13 = +5</code></p>
<p>Before assigning any plaintext, the distinct distances show a simple relationship:</p>
<p><code>11 + 2 = 13</code></p>
<p><code>8 + 5 = 13</code></p>
<p>So the four distinct repeat distances occur as complementary pairs around the total length of the cipher:</p>
<p><code>11 &#x2194; 2</code></p>
<p><code>8 &#x2194; 5</code></p>
<p>This suggested testing the positions cyclically modulo 13.</p>
<p>Representing each movement by its shortest signed residue modulo 13 gives:</p>
<p><code>+11 ≡ -2 mod 13</code></p>
<p><code>+8 ≡ -5 mod 13</code></p>
<p>while:</p>
<p><code>+2 = +2</code></p>
<p><code>+5 = +5</code></p>
<p>Preserving the ordinary left-to-right order of the repeat events by their starting positions — 1, 3, 5, 7 and 8 — gives:</p>
<p><code>-2, -5, +2, +2, +5</code></p>
<p>No sorting is performed afterward to create that sequence.</p>
<p>The second <code>+2</code> exists because the symbol at positions 5, 7 and 9 occurs three times and therefore produces two consecutive repeat intervals:</p>
<p><code>5 → 7 = +2</code></p>
<p><code>7 → 9 = +2</code></p>
<p>This becomes important later.</p>
<h3>3. Use one external anchor: N → E</h3>
<p>The literal <code>N</code> symbol occurs at Z13 positions 3 and 11, so it is class 3 in the notation above.</p>
<p>The same cipher glyph <code>N</code> maps to plaintext <strong>E</strong> in both solved Zodiac ciphers Z408 and Z340.</p>
<p>I therefore test the explicit assumption that this mapping was retained in Z13:</p>
<p><code>N → E</code></p>
<p>Class 3 is the repeat class associated with:</p>
<p><code>-5</code></p>
<p>So the <code>-5</code> member of the displacement sequence is anchored to plaintext <strong>E</strong>.</p>
<p>This anchor is not chosen because E produces a useful word. It is motivated independently by the two solved Zodiac ciphers.</p>
<h3>4. Apply the same integer displacements to the alphabet</h3>
<p>This is the central interpretive step.</p>
<p>The values:</p>
<p><code>-2, -5, +2, +2, +5</code></p>
<p>were obtained in the 13-position cipher space.</p>
<p>I am <strong>not</strong> claiming that arithmetic modulo 13 is mathematically identical to arithmetic modulo 26.</p>
<p>The proposed operation is instead:</p>
<ol>
<li>use modulo 13 to obtain the shortest signed integer representing each positional movement;</li>
<li>take those resulting integers — <code>-2, -5, +2, +2, +5</code> — and test them as alphabetic shifts from one common base letter.</li>
</ol>
<p>Let the unknown common starting letter be called <strong>base</strong>.</p>
<p>Because the <code>-5</code> displacement belongs to the N class, and N is being anchored to plaintext E:</p>
<p><code>base - 5 = E</code></p>
<p>Using alphabet arithmetic modulo 26 with A=0 and E=4:</p>
<p><code>base - 5 ≡ 4 (mod 26)</code></p>
<p>therefore:</p>
<p><code>base ≡ 9</code></p>
<p>Alphabet value 9 is <strong>J</strong>.</p>
<p>So once the N→E anchor and the common-shift rule are accepted, the base is not freely selected. It is forced to be J.</p>
<p>Applying the five Z13-derived displacements:</p>
<p><code>J - 2 = H</code></p>
<p><code>J - 5 = E</code></p>
<p><code>J + 2 = L</code></p>
<p><code>J + 2 = L</code></p>
<p><code>J + 5 = O</code></p>
<p>gives:</p>
<p><strong>HELLO</strong></p>
<h3>5. Why the double L matters</h3>
<p>The second L is not inserted afterward to turn the result into an English word.</p>
<p>It comes directly from the only symbol class occurring three times.</p>
<p>The repeated symbol at positions 5, 7 and 9 produces:</p>
<p><code>+2, +2</code></p>
<p>and therefore:</p>
<p><code>L, L</code></p>
<p>under the proposed alphabetic interpretation.</p>
<p>Without the third occurrence at position 9, the mechanism would produce:</p>
<p><code>HELO</code></p>
<p>The extra occurrence creates the extra L.</p>
<p>So the doubled consonant in HELLO has a direct structural counterpart in Z13.</p>
<h3>6. Anchor sensitivity</h3>
<p>A useful test is to hold the entire procedure fixed and vary only the assumed plaintext value of the N symbol.</p>
<p>If the <code>-5</code> member is assigned plaintext letter <code>P</code>, then the five-letter output is forced to have the relative form:</p>
<p><code>P+3, P, P+7, P+7, P+10</code></p>
<p>The letters cannot be adjusted independently.</p>
<p>For example:</p>
<p><code>N → A</code> gives <code>DAHHK</code></p>
<p><code>N → E</code> gives <code>HELLO</code></p>
<p><code>N → I</code> gives <code>LIPPS</code></p>
<p><code>N → R</code> gives <code>URYYB</code></p>
<p><code>N → T</code> gives <code>WTAAD</code></p>
<p>Testing all 26 possible anchor values simply produces Caesar shifts of the same fixed relative pattern.</p>
<p>The important point is that E was not selected because it yielded HELLO. The reason for testing E comes from outside this construction: N→E is the mapping shared by the solved Z408 and Z340 keys.</p>
<p>This does not prove that Zodiac retained N→E in Z13, but it removes one obvious source of plaintext fitting.</p>
<h3>7. Testing alternative rule choices</h3>
<p>One legitimate objection to this type of analysis is the problem of <strong>forking paths</strong>: perhaps HELLO appears only because several reasonable-looking methodological choices were made after examining Z13.</p>
<p>To test that objection, a separate variant family was defined before inspecting its outputs.</p>
<p>The N class remained fixed as the anchor and N→E remained fixed.</p>
<p>Four methodological dimensions were varied:</p>
<p><strong>Direction</strong></p>
<ul>
<li>forward gap</li>
<li>reverse gap</li>
</ul>
<p><strong>Treatment</strong></p>
<ul>
<li>linear/raw displacement</li>
<li>shortest signed residue modulo 13</li>
<li>unsigned residue modulo 13</li>
</ul>
<p><strong>Event order</strong></p>
<ul>
<li>start position ascending</li>
<li>end position ascending</li>
<li>start position descending</li>
<li>end position descending</li>
</ul>
<p><strong>Mapping</strong></p>
<ul>
<li>alphabetic shift <code>+(v - vN)</code></li>
<li>alphabetic shift <code>-(v - vN)</code></li>
</ul>
<p>This produces:</p>
<p><code>2 × 3 × 4 × 2 = 48</code></p>
<p>predefined rule variants.</p>
<p>On the actual Z13 layout, those 48 variants collapse to 16 distinct outputs because several variants are mathematically equivalent.</p>
<p>The distinct outputs were:</p>
<p><code>HELLO</code></p>
<p><code>HEYYB</code></p>
<p><code>BEKKH</code></p>
<p><code>YYEHB</code></p>
<p><code>KKEBH</code></p>
<p><code>BYYEH</code></p>
<p><code>HKKEB</code></p>
<p><code>BHEYY</code></p>
<p><code>HBEKK</code></p>
<p><code>BEXXU</code></p>
<p><code>LLEHO</code></p>
<p><code>XXEBU</code></p>
<p><code>OLLEH</code></p>
<p><code>UXXEB</code></p>
<p><code>OHELL</code></p>
<p><code>UBEXX</code></p>
<p>Across this family, <strong>HELLO is the only ordinary English word produced by the actual Z13 layout</strong>.</p>
<p>HELLO occurs in two of the 48 variants:</p>
<ul>
<li>forward / shortest signed / start ascending / positive mapping</li>
<li>reverse / shortest signed / start ascending / negative mapping</li>
</ul>
<p>These two are mathematically equivalent descriptions of the same underlying operation, since reversing the direction and reversing the sign cancel each other.</p>
<p>So there is effectively one HELLO-producing mechanism within this family, not two independent ones.</p>
<p>It is also worth noting that descending event order gives:</p>
<p><code>OLLEH</code></p>
<p>which is HELLO reversed.</p>
<p>That is consistent with the idea that left-to-right event ordering carries the plaintext order.</p>
<h3>8. Randomized-layout null test</h3>
<p>The same full 48-variant family was then tested on <strong>200,000 randomized layouts</strong> preserving Z13's symbol multiplicities:</p>
<p><code>3,2,2,2,1,1,1,1</code></p>
<p>The symbol positions were randomized, but the rules were not optimized separately for each sample.</p>
<p>Using a strict English word list:</p>
<ul>
<li>at least one of the 48 variants produced a five-letter word in approximately <strong>0.78%</strong> of randomized layouts.</li>
</ul>
<p>Using a somewhat more permissive word list:</p>
<ul>
<li>at least one variant produced a word in approximately <strong>1.11%</strong> of layouts.</li>
</ul>
<p>So approximately <strong>99% of randomized layouts produced no English word at all</strong>, even when all 48 predefined rule variants were available.</p>
<p>The average individual variant produced a word in about:</p>
<p><code>0.085%</code></p>
<p>of random layouts.</p>
<p>Two or more distinct words appeared in only about:</p>
<p><code>0.04%</code></p>
<p>of layouts.</p>
<p>These dictionary-based figures depend on the precise word list used and should be treated as approximate calibration rather than exact probabilities.</p>
<p>This is not a formal probability that Zodiac intended HELLO. The rule family itself was designed by an analyst, and the analysis remains post-hoc with respect to the original discovery.</p>
<p>But the test does address a narrower objection:</p>
<blockquote>
<p>HELLO is not simply an inevitable consequence of allowing a modest family of alternative gap, direction, ordering and sign conventions.</p>
</blockquote>
<p>Within this particular predefined family, the real Z13 layout produces one English word:</p>
<p><strong>HELLO</strong></p>
<p>whereas a random Z13-like layout produces any English word only around 1% of the time.</p>
<h3>9. Exact HELLO null test under the frozen original procedure</h3>
<p>A separate exhaustive test was performed using only the original frozen procedure rather than the 48-variant family.</p>
<p>The relevant geometry is determined by the placements of the four repeated symbol classes, whose multiplicities are:</p>
<p><code>3,2,2,2</code></p>
<p>across 13 positions.</p>
<p>There are exactly:</p>
<p><strong>5,405,400</strong></p>
<p>distinct placements of those four repeated classes.</p>
<p>Under the frozen procedure, exactly:</p>
<p><strong>100</strong></p>
<p>of those repeat-class placements produce HELLO with N→E fixed.</p>
<p>The four distinct singleton labels occupy the remaining four positions. Their identities do not affect the repeat geometry, so they can be permuted among those four positions in:</p>
<p><code>4! = 24</code></p>
<p>ways.</p>
<p>This multiplies both numerator and denominator by the same factor:</p>
<p><code>5,405,400 × 24 = 129,729,600</code></p>
<p>fully labelled arrangements,</p>
<p>and:</p>
<p><code>100 × 24 = 2,400</code></p>
<p>HELLO-producing fully labelled arrangements.</p>
<p>Therefore the exact rate is the same either way:</p>
<p><code>100 / 5,405,400</code></p>
<p>or:</p>
<p><code>2,400 / 129,729,600</code></p>
<p>which equals approximately:</p>
<p><code>0.00185%</code></p>
<p>or:</p>
<p><strong>1 in 54,054</strong></p>
<p>randomized layouts.</p>
<p>Again, this should <strong>not</strong> be interpreted as a p-value for Zodiac's intention, because the procedure itself was discovered through prior exploration.</p>
<p>Its narrower meaning is simply that, once the procedure is frozen, the exact HELLO-producing repeat geometry is uncommon among layouts with the same repeat multiplicities.</p>
<h3>10. How the 13 positions contribute</h3>
<p>All 13 positions define the positional geometry, but the decoding statistic is generated only by transitions between successive occurrences of the four repeated classes.</p>
<p>The four singleton classes — 2, 4, 6 and 8 — do not individually generate plaintext letters, and their individual identities are not used by this construction.</p>
<p>What matters is which positions are occupied by singleton classes rather than by repeated classes, because those occupied positions help determine the distances between successive occurrences of the repeated classes.</p>
<p>Permuting the four singleton labels among the same four singleton positions leaves the repeat geometry and the resulting output unchanged.</p>
<p>Changing which positions are occupied by singleton classes, however, changes the placement of the repeated classes and can therefore change the transition distances from which the decoding statistic is derived.</p>
<p>The proposal is therefore better described as:</p>
<p><strong>13-position geometry → 5 transitions between repeated-class occurrences → 5 plaintext letters</strong></p>
<p>rather than:</p>
<p><strong>13 ciphertext symbols → 13 plaintext letters</strong></p>
<h3>11. What is observation, and what is assumption?</h3>
<p>This distinction is essential.</p>
<h4>Directly observable in Z13</h4>
<ul>
<li>
<p>there are 13 positions;</p>
</li>
<li>
<p>there are eight distinct symbol classes;</p>
</li>
<li>
<p>the normalized pattern is:</p>
<p><code>1 2 3 4 5 6 5 7 5 8 3 1 7</code></p>
</li>
<li>
<p>four classes repeat: 1, 3, 5 and 7;</p>
</li>
<li>
<p>four classes are singletons: 2, 4, 6 and 8;</p>
</li>
<li>
<p>the repeat positions are 1/12, 3/11, 5/7/9 and 8/13;</p>
</li>
<li>
<p>the forward repeat gaps are:</p>
<p><code>11, 8, 2, 2, 5</code></p>
</li>
<li>
<p>the distinct gap sizes contain the complementary pairs:</p>
<p><code>11 + 2 = 13</code></p>
<p><code>8 + 5 = 13</code></p>
</li>
<li>
<p>under shortest signed residues modulo 13, the repeat sequence in left-to-right event order is:</p>
<p><code>-2, -5, +2, +2, +5</code></p>
</li>
<li>
<p>the duplicated <code>+2</code> comes from the only three-occurrence class.</p>
</li>
</ul>
<h4>The construction makes three explicit assumptions</h4>
<p><strong>Assumption 1</strong></p>
<p>The 13 cipher positions may legitimately be treated cyclically, and the shortest signed residues modulo 13 are meaningful representations of the repeat movements.</p>
<p><strong>Assumption 2</strong></p>
<p>The N→E mapping shared by Z408 and Z340 was retained for the N symbol in Z13.</p>
<p><strong>Assumption 3</strong></p>
<p>The signed integer values obtained from the positional movements are also intended to function as signed alphabetic shifts from one common base letter.</p>
<p>Once those assumptions are accepted, HELLO is no longer freely selectable.</p>
<p>The <code>-5</code> member being fixed to E forces the base to J, and then:</p>
<p><code>-2 → H</code></p>
<p><code>-5 → E</code></p>
<p><code>+2 → L</code></p>
<p><code>+2 → L</code></p>
<p><code>+5 → O</code></p>
<p>giving:</p>
<p><strong>HELLO</strong></p>
<h3>12. What I am not claiming</h3>
<p>I am not claiming that HELLO has been proven to be the unique solution of Z13.</p>
<p>A cipher this short is inherently underdetermined, and many possible systems can be proposed.</p>
<p>I am also not claiming to know Zodiac's intention.</p>
<p>The narrower claim is:</p>
<blockquote>
<p><strong>Z13 contains a repeat-distance construction which, when represented by shortest signed movements modulo 13, anchored by the independently motivated N→E mapping, and reused as alphabetic offsets from a common base, produces HELLO.</strong></p>
</blockquote>
<p>The construction is reproducible.</p>
<p>It has also survived two attempts to test whether the output is merely an artifact of flexible rules:</p>
<ol>
<li>under the frozen original procedure, HELLO occurs in exactly 100 of 5,405,400 repeat-class layouts — equivalent to 2,400 of 129,729,600 fully labelled arrangements — or about 1 in 54,054;</li>
<li>across one predefined family of 48 plausible methodological variants, HELLO is the only English word produced by the actual Z13 layout, while randomized layouts produce any English word in only about 0.8–1.1% of cases under the tested dictionaries.</li>
</ol>
<p>Neither result proves intention.</p>
<p>They do, however, make the weaker explanation — that HELLO appears trivially because almost any reasonable manipulation of the Z13 repeat structure produces a word — less convincing.</p>
<p>Finally, the result appears immediately after Zodiac's introduction:</p>
<p><strong>“MY NAME IS —”</strong></p>
<p>which gives the possible reading:</p>
<p><strong>“MY NAME IS — HELLO”</strong></p>
<p>That contextual fit is interesting, but it should remain supporting context rather than evidence used to construct the result.</p>
<p>The remaining question is therefore quite specific:</p>
<blockquote>
<p><strong>Did Zodiac intend the signed repeat movements in the 13-position cipher to be reused as alphabetic shifts?</strong></p>
</blockquote>
<p>That is the principal unresolved interpretive step in determining whether this construction reflects Zodiac's intended mechanism rather than a reproducible structural coincidence.</p>
<h3>Reproducibility note</h3>
<p>The variant and null tests described above were implemented independently from the proposed plaintext and can be reproduced from the stated rules.</p>
<p>For transparency, the test code and word-list definitions can be provided on request.</p>
<p>The dictionary-based rates depend on the particular English word list used. The exact HELLO enumeration:</p>
<p><code>100 / 5,405,400</code></p>
<p>equivalently:</p>
<p><code>2,400 / 129,729,600</code></p>
<p>does <strong>not</strong> depend on a dictionary.</p>]]></content:encoded>
						                            <category domain="https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/">Zodiac Cipher Mailings &amp; Discussion</category>                        <dc:creator>Northkey</dc:creator>
                        <guid isPermaLink="true">https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/z13-a-repeat-distance-construction-yielding/</guid>
                    </item>
				                    <item>
                        <title>Proposal for a Z13 Symmetric Autokey: The Role of the Symmetrically Placed N Symbol on Both Ends and the K-Axis</title>
                        <link>https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/proposal-for-a-z13-symmetric-autokey-the-role-of-the-symmetrically-placed-n-symbol-on-both-ends-and-the-k-axis/</link>
                        <pubDate>Mon, 07 Sep 2026 21:10:28 +0000</pubDate>
                        <description><![CDATA[Hey everyone! Analyzing the structural patterns of the Z13, I wanted to propose a new line of reasoning focused on graphic symmetry to solve the problem of orphan symbols (those not found in...]]></description>
                        <content:encoded><![CDATA[<p data-path-to-node="1">Hey everyone! Analyzing the structural patterns of the Z13, I wanted to propose a new line of reasoning focused on graphic symmetry to solve the problem of orphan symbols (those not found in the traditional Z340 or Z408 tables).</p>
<p data-path-to-node="2">Observing the layout of the cipher, we have a striking detail: <b data-path-to-node="2" data-index-in-node="63">the symbol N is positioned completely symmetrically on both ends of the code (on both the left and the right sides)</b>.</p>
<h3 data-path-to-node="3">The K-Axis Dynamics and the Self-Generated Sequence</h3>
<p data-path-to-node="4">If we treat the <b data-path-to-node="4" data-index-in-node="16">K symbol</b> as our central axis, the symmetric expansion of the reading behaves as follows:</p>
<ul data-path-to-node="5">
<li>
<p data-path-to-node="5,0,0">Moving left from K, we pass through L and reach N.</p>
</li>
<li>
<p data-path-to-node="5,1,0">Moving right from K, we pass through L, M, and N, ending at O.</p>
</li>
</ul>
<p data-path-to-node="6">This symmetric distribution maps out precisely the four unknowns that usually generate discrepancies in Z13 decoding attempts (resulting in the letters <b data-path-to-node="6" data-index-in-node="152">L, L, N, O</b> highlighted in blue in the projection). Instead of trying to fit letters arbitrarily or forcefully, treating these remaining symbols as a sequence self-generated by a spiral or palindromic rotation key (<i data-path-to-node="6" data-index-in-node="366">N-M-L-K-L-M-N-O</i>) brings an impressive mathematical cohesion to the arrangement.</p>
<p data-path-to-node="7">This would solve the mystery of the Z13 "orphan" symbols by utilizing the internal symmetry of the Zodiac's own graphical chaining. What do you think of this approach? Has anyone else tested whether this symmetric logic fits with the alphabetical inversion pattern or generates other coherent readings across the rest of the line?</p>
<p data-path-to-node="7"><img src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg-m7dg91fSg-UPomNs3oLRR2qi9rnOuUNSjbc7rlQWH1lU6SyL2AzucS_EZ65fpW4gzW8_AjvT_NkB6UZAYB1RD9lvRCV8akiGwyuqNoTCz-mixifVTD6PZ4ijuYiV0oCodbZAu_Zt2Iy_sBCo7Z2Rb7cAOJ7n9Ar67rmkybFVD9G0MONif7UfxgGcuNY/s600/klmno.jpg" /></p>
<p data-path-to-node="7">Before anyone gets too carried away trying to force anagrams like "ALLEN" or "LEANDRO" out of these letters: let's be real, forcing anagrams is a massive stretch. My name is Marcelo Leandro, and for the record, I am definitely not the Zodiac Killer. If mathematical ciphers start spelling out my grocery list or personal info next, I'll be sure to send my billing address to the police.</p>]]></content:encoded>
						                            <category domain="https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/">Zodiac Cipher Mailings &amp; Discussion</category>                        <dc:creator>Marclean</dc:creator>
                        <guid isPermaLink="true">https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/proposal-for-a-z13-symmetric-autokey-the-role-of-the-symmetrically-placed-n-symbol-on-both-ends-and-the-k-axis/</guid>
                    </item>
				                    <item>
                        <title>Validating the Z13 Solution: How a Palindromic Key Reinforces Dr. Ryan Garlick’s Hypothesis</title>
                        <link>https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/validating-the-z13-solution-how-a-palindromic-key-reinforces-dr-ryan-garlicks-hypothesis/</link>
                        <pubDate>Sun, 06 Sep 2026 06:13:36 +0000</pubDate>
                        <description><![CDATA[alidating the Z13 Solution: How a Palindromic Key Reinforces Dr. Ryan Garlick’s Hypothesis
Hey everyone,
I wanted to share a structural analysis I’ve been working on that provides mechanic...]]></description>
                        <content:encoded><![CDATA[<p data-path-to-node="4"><b data-path-to-node="4" data-index-in-node="0">alidating the Z13 Solution: How a Palindromic Key Reinforces Dr. Ryan Garlick’s Hypothesis</b></p>
<p data-path-to-node="6">Hey everyone,</p>
<p data-path-to-node="7">I wanted to share a structural analysis I’ve been working on that provides mechanical backing for <b data-path-to-node="7" data-index-in-node="98">Dr. Ryan Garlick’s proposed solution</b> to the Z13 cipher <a href="https://www.youtube.com/watch?v=tqwVEU5hapk" target="_blank" rel="noopener">( on Dave Oranchak’s channel)</a>.</p>
<p data-path-to-node="8">While Dr. Garlick derived the historical context from 1960s newspaper publications and assigned the letters <b data-path-to-node="8" data-index-in-node="108">P-R-T</b> to fill the short cipher's missing slots, my goal here is to demonstrate the <b data-path-to-node="8" data-index-in-node="191">geometric shift mechanism</b> that validates this exact substitution.</p>
<h3 data-path-to-node="10">1. Historical Context: Taunting the 1960s Academic</h3>
<p data-path-to-node="11">Around the time the Z13 was mailed (prefaced by <i data-path-to-node="11" data-index-in-node="48">"My name is..."</i>), a 1960s academic and cryptography expert publicly challenged the Zodiac in local newspapers to provide a cipher containing his actual name.</p>
<p data-path-to-node="12">As analyzed by Dr. Garlick, the Zodiac’s response wasn't his real identity, but a dark taunt directed at that scholar:</p>
<ul data-path-to-node="13">
<li>
<p data-path-to-node="13,0,0"><b data-path-to-node="13,0,0" data-index-in-node="0">The Railway "Torpedo":</b> In 1960s railroad parlance, a "torpedo" was a small explosive cap strapped to train tracks that detonated with a loud bang when rolled over by a train wheel to warn the engineer.</p>
</li>
<li>
<p data-path-to-node="13,1,0"><b data-path-to-node="13,1,0" data-index-in-node="0">The Response:</b> By combining characters solved via the Z340 and assigning <b data-path-to-node="13,1,0" data-index-in-node="72">P-R-T</b> to the unmapped symbols of the short Z13 code, the plaintext resolves into <b data-path-to-node="13,1,0" data-index-in-node="153">DREATATORPEDO</b> (<i data-path-to-node="13,1,0" data-index-in-node="168">"Dr Eat a torpedo"</i>) — a sarcastic <i data-path-to-node="13,1,0" data-index-in-node="199">"eat an explosive"</i> response to the scholar who dared him.</p>
</li>
</ul>
<h3 data-path-to-node="15">2. Structural Validation: The Palindromic Rotation Matrix</h3>
<p data-path-to-node="16">To show that the assignment of <b data-path-to-node="16" data-index-in-node="31">P-R-T</b> holds mechanical backing and isn't arbitrary, I applied the mirrored shift vector <code data-path-to-node="16" data-index-in-node="119">ZYXWVUTSRQPONMNOPQRSTUVWXYZ</code> across two parallel tracks anchored around the central pivot <b data-path-to-node="16" data-index-in-node="208">M</b>:</p>
<table data-path-to-node="17">
<thead>
<tr>
<td><strong>Layer / Track</strong></td>
<td><strong>Sequence &amp; Structure</strong></td>
<td><strong>Function in Code</strong></td>
</tr>
</thead>
<tbody>
<tr>
<td><span data-path-to-node="17,1,0,0"><b data-path-to-node="17,1,0,0" data-index-in-node="0">1. Z13 Ciphertext (Symbols)</b></span></td>
<td><span data-path-to-node="17,1,1,0"><code data-path-to-node="17,1,1,0" data-index-in-node="0">A E N ⊕ ⊗ K ⊗ M ⊗ ⅋ N A</code> <b data-path-to-node="17,1,1,0" data-index-in-node="24"><code data-path-to-node="17,1,1,0" data-index-in-node="24">M</code></b></span></td>
<td><span data-path-to-node="17,1,2,0">Ciphertext anchored at central pivot <b data-path-to-node="17,1,2,0" data-index-in-node="37">M</b></span></td>
</tr>
<tr>
<td><span data-path-to-node="17,2,0,0"><b data-path-to-node="17,2,0,0" data-index-in-node="0">2. Revealed Plaintext</b></span></td>
<td><span data-path-to-node="17,2,1,0"><b data-path-to-node="17,2,1,0" data-index-in-node="0"><code data-path-to-node="17,2,1,0" data-index-in-node="0">D R E A T A T O R P E D O</code></b></span></td>
<td><span data-path-to-node="17,2,2,0">Decoded plaintext (<i data-path-to-node="17,2,2,0" data-index-in-node="19">"Eat a torpedo"</i>)</span></td>
</tr>
<tr>
<td><span data-path-to-node="17,3,0,0"><b data-path-to-node="17,3,0,0" data-index-in-node="0">3. Upper Key Track</b></span></td>
<td><span data-path-to-node="17,3,1,0"><code data-path-to-node="17,3,1,0" data-index-in-node="0">Y X W V U T S R Q</code> <b data-path-to-node="17,3,1,0" data-index-in-node="18"><code data-path-to-node="17,3,1,0" data-index-in-node="18">P</code></b> <code data-path-to-node="17,3,1,0" data-index-in-node="20">O N</code> <b data-path-to-node="17,3,1,0" data-index-in-node="24"><code data-path-to-node="17,3,1,0" data-index-in-node="24">M</code></b></span></td>
<td><span data-path-to-node="17,3,2,0">Regressive shift sweep towards center <b data-path-to-node="17,3,2,0" data-index-in-node="38">M</b></span></td>
</tr>
<tr>
<td><span data-path-to-node="17,4,0,0"><b data-path-to-node="17,4,0,0" data-index-in-node="0">4. Lower Key Track</b></span></td>
<td><span data-path-to-node="17,4,1,0"><code data-path-to-node="17,4,1,0" data-index-in-node="0">Z Y X W V U</code> <b data-path-to-node="17,4,1,0" data-index-in-node="12"><code data-path-to-node="17,4,1,0" data-index-in-node="12">T</code></b> <code data-path-to-node="17,4,1,0" data-index-in-node="14">S</code> <b data-path-to-node="17,4,1,0" data-index-in-node="16"><code data-path-to-node="17,4,1,0" data-index-in-node="16">R</code></b> <code data-path-to-node="17,4,1,0" data-index-in-node="18">Q P O N</code></span></td>
<td><span data-path-to-node="17,4,2,0">Phase offset validating missing <b data-path-to-node="17,4,2,0" data-index-in-node="32">P-R-T</b> values</span></td>
</tr>
</tbody>
</table>
<p data-path-to-node="18">Sliding the key leftward creates a symmetrical rotational shift that naturally maps the Z13's unknown symbols directly into <b data-path-to-node="18" data-index-in-node="124">P</b>, <b data-path-to-node="18" data-index-in-node="127">R</b>, and <b data-path-to-node="18" data-index-in-node="134">T</b>.</p>
<p data-path-to-node="18"> </p>
<p data-path-to-node="18"><img src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhYZQZZQQyPcBttatR0hjehnNnSxiZ_PqbtOslbC3GGHXgv3OKJU0yYXBcR6lxxG0BzcIS4uOcHddXMtH4RAAWSbOxrv7b9pB96e4a_PSyJbUk90fULuux1xDtqn2_NbTN0LGUOdTcnfH5sfccScOFAWlaCTto6GpMI196l3k4-4qB3P5cASs4Z2ljyWyo/s600/Z13PALINDROMO.jpg" /></p>
<p data-path-to-node="18">Marcelo </p>
<p data-path-to-node="18"> </p>]]></content:encoded>
						                            <category domain="https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/">Zodiac Cipher Mailings &amp; Discussion</category>                        <dc:creator>Marclean</dc:creator>
                        <guid isPermaLink="true">https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/validating-the-z13-solution-how-a-palindromic-key-reinforces-dr-ryan-garlicks-hypothesis/</guid>
                    </item>
				                    <item>
                        <title>My z32 candidate</title>
                        <link>https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/my-z32-candidate/</link>
                        <pubDate>Tue, 01 Sep 2026 14:58:56 +0000</pubDate>
                        <description><![CDATA[My Z32 candidate: AT SIX SIX INCHES FROM MOUNT DIABLO PIT








&nbsp;
I want to present this as a working hypothesis, not as a proven unique decryption of Z32.
&nbsp;
My candi...]]></description>
                        <content:encoded><![CDATA[<div>
<div class="docs-ml-promotion docs-ml-promotion-off-screen" role="alertdialog" aria-labelledby="docs-ml-promotion-aria-label" aria-hidden="true">
<div class="docs-ml-promotion-content">
<div class="docs-ml-promotion-header">
<div class="docs-ml-promotion-text-heading" style="text-align: left">My Z32 candidate: AT SIX SIX INCHES FROM MOUNT DIABLO PIT</div>
</div>
</div>
</div>
</div>
<div class="app-container">
<div class="doc-container">
<div class="doc">
<div class="doc-content">
<p>&nbsp;</p>
<p><span>I want to present this as a working hypothesis, not as a proven unique decryption of Z32.</span></p>
<p>&nbsp;</p>
<p><span>My candidate is:</span></p>
<p>&nbsp;</p>
<p><span>AT SIX SIX INCHES FROM MOUNT DIABLO PIT</span></p>
<p>&nbsp;</p>
<p><span>Without spaces:</span></p>
<p>&nbsp;</p>
<p><span>ATSIXSIXINCHESFROMMOUNTDIABLOPIT</span></p>
<p>&nbsp;</p>
<p><span>It is exactly 32 letters.</span></p>
<p>&nbsp;</p>
<p><span>Z32 contains only three repeated-symbol identities:</span></p>
<p>&nbsp;</p>
<p><span>1 = 26</span></p>
<p><span>2 = 32</span></p>
<p><span>6 = 14</span></p>
<p>&nbsp;</p>
<p><span>The candidate gives:</span></p>
<p>&nbsp;</p>
<p><span>1/26 = A/A</span></p>
<p><span>2/32 = T/T</span></p>
<p><span>6/14 = S/S</span></p>
<p>&nbsp;</p>
<p><span>All three fit.</span></p>
<p>&nbsp;</p>
<p><span>What is interesting, however, is what happens if we do not insert PIT beforehand.</span></p>
<p>&nbsp;</p>
<p><span>I tested a deliberately restricted map grammar based on what Zodiac actually gave us: Mount Diablo as the origin, the dial positions 0 / 3 / 6 / 9, distances written ONE through TWELVE, and the form:</span></p>
<p>&nbsp;</p>
<p><span>AT   INCHES FROM MOUNT DIABLO </span></p>
<p>&nbsp;</p>
<p><span>The destination word was left unknown.</span></p>
<p>&nbsp;</p>
<p><span>Within this defined model, SIX / SIX is the only direction/distance combination that can fill a 32-letter text while satisfying the Z32 constraints 1=26 and 6=14.</span></p>
<p>&nbsp;</p>
<p><span>The result before the destination is determined is:</span></p>
<p>&nbsp;</p>
<p><span>AT SIX SIX INCHES FROM MOUNT DIABLO ???</span></p>
<p>&nbsp;</p>
<p><span>The known part occupies 29 positions. The Z32 constraint 2=32 then requires the final letter to be the same as position 2, namely T:</span></p>
<p>&nbsp;</p>
<p><span>AT SIX SIX INCHES FROM MOUNT DIABLO ??T</span></p>
<p>&nbsp;</p>
<p><span>This is an important distinction. We did not start with a gravel pit and then construct a 32-letter phrase that hit it. Within this map grammar, SIX / SIX / MOUNT DIABLO / ??T comes first. P and I in PIT are not cryptographically forced; if correct, they must come from the geography.</span></p>
<p>&nbsp;</p>
<p><span>This is also not a claim of global uniqueness. Z32 is too short and contains too little repetition to force a single plaintext without external information.</span></p>
<p>&nbsp;</p>
<p><span>The map operation</span></p>
<p>&nbsp;</p>
<p><span>Zodiac wrote on the Mount Diablo map:</span></p>
<p>&nbsp;</p>
<p><span>“0 is to be set to Mag. N.”</span></p>
<p><span><img title="" src="https://docs.google.com/docs-images-rt/ALKuztZEcBKLoPd778S_7rLe296Uh9qMCZhooBpbNkzLl2XVEdgDATFP7hBbNUrxOWAvOA87fUYQXzmYNK67u8MeQ7zwQid3EefZlRmWc8JhjW5TUhDjMcuJHceq8vEq0dNJKy_aoujWbNYrJICRyEnp4UhfD4eSOegy_mHjzB8-zA=s320" alt="" /></span></p>
<p>&nbsp;</p>
<p><span>In the Little List letter about a month later, he wrote:</span></p>
<p>&nbsp;</p>
<p><span>“P.S. The Mt. Diablo Code concerns Radians &amp; # inches along the radians.”</span></p>
<p>&nbsp;</p>
<p><span>This gives a natural angle-plus-distance operation.</span></p>
<p>&nbsp;</p>
<p><span>Set 0 to magnetic north.</span></p>
<p>&nbsp;</p>
<p><span>The first SIX is read as position 6 on the oriented dial. Six lies directly opposite zero:</span></p>
<p>&nbsp;</p>
<p><span>6 o’clock = 180° from 0 = π radians</span></p>
<p>&nbsp;</p>
<p><span>This does not mean six radians. 6 radians ≈343.8°, which is a completely different direction.</span></p>
<p>&nbsp;</p>
<p><span>The second SIX belongs to:</span></p>
<p>&nbsp;</p>
<p><span>SIX INCHES</span></p>
<p>&nbsp;</p>
<p><span>and specifies the linear map distance along the ray defined by position 6.</span></p>
<p>&nbsp;</p>
<p><span>The Phillips 66 inset used by Zodiac has the printed scale:</span></p>
<p>&nbsp;</p>
<p><span>“ONE INCH EQUALS APPROX. 6.4 MILES”</span></p>
<p>&nbsp;</p>
<p><span>The nominal 1970 operation is therefore:</span></p>
<p>&nbsp;</p>
<p><span>6 inches × 6.4 miles/inch = 38.4 miles</span></p>
<p>&nbsp;</p>
<p><span>I am therefore not using the Phillips 66 branding as the source of the words SIX/SIX. It is not necessary for the mechanism. The operative elements are the Z32 construction, the 0–3–6–9 dial, and the map’s printed scale.</span></p>
<p>&nbsp;</p>
<p><span><img title="" src="https://docs.google.com/docs-images-rt/ALKuztbDYMJqc3QyPVrN2oDF4S8fnigFRXsRfm4F6pPxzxkmIjcWKBbaJh20Q5Q9yFZXQZqjrReRCZI07v_fFHjgapFhkbv7ibVRNw42335RezsE1c1_m1_McfZyLNZiP3KE9bU3lwyhITnUm6gGlBuJZa4KtkqrtHmx_76M0XJhOA=s320" alt="" /></span></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p><span>Source check:</span></p>
<p>&nbsp;</p>
<p><span>Search: "9-QQ-1219-S" Zodiac</span></p>
<p><span>Search: "Original Untouched '69 Phillips 66 Map"</span></p>
<p>&nbsp;</p>
<p><span>The large original scan shows both the map code 9-QQ-1219-S and the printed 6.4-mile scale.</span></p>
<p>&nbsp;</p>
<p><span>As a modern cross-check — not as the 1970 method — we can compare Mount Diablo with the published locality reference for Near/Neary Quarry.</span></p>
<p>&nbsp;</p>
<p><span>The reference points give approximately:</span></p>
<p>&nbsp;</p>
<p><span>Distance: 38.380 miles</span></p>
<p><span>Printed-scale equivalent: 5.997 inches</span></p>
<p><span>Initial true bearing: 197.236°</span></p>
<p>&nbsp;</p>
<p><span>If dial position 6 is magnetic south, that bearing would correspond to a declination of approximately 17.236° E.</span></p>
<p>&nbsp;</p>
<p><span>That value must not be confused with the historical value. A historical calculation for Mount Diablo on June 26, 1970 gives approximately 16°53′ E = 16.9° E. The difference is only a few tenths of a degree.</span></p>
<p>&nbsp;</p>
<p><span>The quarry coordinate is also a locality reference with a stated accuracy of about 100 metres, not a survey-grade target point. I therefore do not use 38.380 versus 38.400 as a “32-metre precision” argument. The point is only that the nominal SIX-INCHES distance and direction are highly consistent with the historical quarry area.</span></p>
<p>&nbsp;</p>
<p><span>Source check for the coordinate/bearing/declination control:</span></p>
<p><span>Mount Diablo summit reference (USGS topo source via TopoQuest): 37.881702 N, -121.914268 W</span></p>
<p><span>https://topoquest.com/place/california/summit/mount-diablo/222343</span></p>
<p><span>Near Quarry (Neary Rock Quarry), Mindat locality 92281: 37.35000 N, -122.12083 W; stated MRDS location accuracy 100 m</span></p>
<p><span>https://www.mindat.org/loc-92281.html</span></p>
<p><span>NOAA/NCEI Historic Magnetic Declination Calculator</span></p>
<p><span>https://www.ngdc.noaa.gov/geomag/calculators/ushistoricForm.shtml</span></p>
<p><span>On the 32-Character Zodiac Cipher — Table 2 gives Mount Diablo, June 26, 1970 as 16°53′ E</span></p>
<p><span>https://iacr.steepath.eu/2023/982-Onthe32CharacterZodiacCipher.pdf</span></p>
<p>&nbsp;</p>
<p><span>What is at the endpoint?</span></p>
<p>&nbsp;</p>
<p><span>When this operation is followed from Mount Diablo, we arrive in the Los Altos Hills area.</span></p>
<p>&nbsp;</p>
<p><span>A contemporary topographic map then gives us an independent geographic check.</span></p>
<p>&nbsp;</p>
<p><span>The USGS Cupertino, California 7.5-minute quadrangle, original 1961, version/photorevision 1968 and print 1969, existed before Z32 was mailed in June 1970.</span></p>
<p>&nbsp;</p>
<p><span>On the map, the area is explicitly labeled:</span></p>
<p>&nbsp;</p>
<p><span>Gravel Pit</span></p>
<p>&nbsp;</p>
<p><span><img title="" src="https://docs.google.com/docs-images-rt/ALKuztb2bWIHi4COXEVKqcdpLfCQLW7YPrN2MX69PUq-UmV-LX7kM4y2MiPOwGUswkTPav36HKxvN2MnBcn38F8XTrYIT3oWE3yzb6J_WMD7kcQ50qMYgaUGNtmSVHC2nN0kyoAKYFD4_kG25dIoVgqnT51qU4189hW9q5vMzyw=s320" alt="" /></span></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p><span>The USGS catalog itself confirms:</span></p>
<p>&nbsp;</p>
<p><span>Product 307728</span></p>
<p><span>Scale 1:24,000</span></p>
<p><span>Version date 1968</span></p>
<p><span>Print date 1969</span></p>
<p><span>1961 historical map</span></p>
<p>&nbsp;</p>
<p><span>Source check:</span></p>
<p>&nbsp;</p>
<p><span>Search: USGS Cupertino 307728</span></p>
<p>&nbsp;</p>
<p><span>This is why I propose completing the already constrained destination slot as:</span></p>
<p>&nbsp;</p>
<p><span>??T → PIT</span></p>
<p>&nbsp;</p>
<p><span>The USGS map does not decrypt the letters P and I. No part of the Z32 repetition pattern does that. The argument is instead:</span></p>
<p>&nbsp;</p>
<p><span>Z32 + the map grammar gives a three-letter destination ending in T.</span></p>
<p>&nbsp;</p>
<p><span>The map operation leads to an area that a map available before Z32 literally labels Gravel Pit.</span></p>
<p>&nbsp;</p>
<p><span>PIT is therefore a geographic and semantic completion of ??T.</span></p>
<p>&nbsp;</p>
<p><span>Section 6 – found after the endpoint</span></p>
<p>&nbsp;</p>
<p><span>The next finding came after the quarry/pit endpoint had already been identified.</span></p>
<p>&nbsp;</p>
<p><span>In California Journal of Mines and Geology, Volume 50, No. 2, April 1954, there is:</span></p>
<p>&nbsp;</p>
<p><span>Table 6. Rock (crushed) operations in Santa Clara County</span></p>
<p>&nbsp;</p>
<p><span>Row 44 reads:</span></p>
<p>&nbsp;</p>
<p><span>Sondgrath Bros. (Neary)</span></p>
<p><span>T. 7 S.</span></p>
<p><span>R. 2 W.*</span></p>
<p><span>Sec. 6</span></p>
<p><span>West of Los Altos</span></p>
<p>&nbsp;</p>
<p><span>The footnote to the asterisk says:</span></p>
<p>&nbsp;</p>
<p><span>“Mt. Diablo Base &amp; Meridian projected.”</span></p>
<p>&nbsp;</p>
<p><span><img title="" src="https://docs.google.com/docs-images-rt/ALKuztZo6o4gkRSzw52UPd1VOzAS62pEdAYKVGWSZw4RHWiaQTtjP2csjz8VNoHb6mNmGB3W6C58IZfLSgXAP8p4MbHwFkRxdZQ_UQSmBDGgvI34whX6C3cqtYdG0z-SZC1gD17xpo7zFANvsPkQiQ4X3Jr-LYYbdts_SO1HQr6Ztg=s320" alt="" /></span></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p><span>We have now checked this directly against the original scan of Volume 50 at Internet Archive, not only against a modern web transcription. The Internet Archive copy was scanned from the University of California, Davis Libraries and is identified as volume 50 of California journal of mines and geology. The separate QuarriesAndBeyond reproduction, used with permission from the California Geological Survey, transcribes the same Sondgrath/Neary entry as Sec. 6, T.7S., R.2W., M.D.B.M. (projected), west of Los Altos.</span></p>
<p>&nbsp;</p>
<p><span>Source check:</span></p>
<p>&nbsp;</p>
<p><span>Search: "Sondgrath Bros. (Neary)" "Sec. 6"</span></p>
<p><span>Search: californiajourna50cali</span></p>
<p>&nbsp;</p>
<p><span>This is methodologically important:</span></p>
<p>&nbsp;</p>
<p><span>Section 6 was not used to find the quarry.</span></p>
<p>&nbsp;</p>
<p><span>We already had the SIX-o’clock direction, the SIX-INCHES distance, and the gravel-pit endpoint before the Section 6 entry was found.</span></p>
<p>&nbsp;</p>
<p><span>Only then did this possible secondary pattern appear:</span></p>
<p>&nbsp;</p>
<p><span>6 o’clock</span></p>
<p><span>6 inches</span></p>
<p><span>Section 6</span></p>
<p>&nbsp;</p>
<p><span>or:</span></p>
<p>&nbsp;</p>
<p><span>6 – 6 – 6</span></p>
<p>&nbsp;</p>
<p><span>with DIABLO as the origin name.</span></p>
<p>&nbsp;</p>
<p><span>I am not claiming that this proves a deliberate 666 construction. The components are not statistically independent enough for us to assign any meaningful probability, and the finding is post-hoc.</span></p>
<p>&nbsp;</p>
<p><span>But because Section 6 was not used as an input to select the endpoint, it is an interesting secondary historical control finding, not a parameter that was adjusted to create the match.</span></p>
<p>&nbsp;</p>
<p><span>What the hypothesis actually claims</span></p>
<p>&nbsp;</p>
<p><span>This is not a claim that we have found a proven, unique symbol-for-symbol key to Z32.</span></p>
<p>&nbsp;</p>
<p><span>What I find interesting is this sequence:</span></p>
<p>&nbsp;</p>
<p><span>Z32 repeated-symbol constraints + restricted map grammar</span></p>
<p><span>→ AT SIX SIX INCHES FROM MOUNT DIABLO ??T</span></p>
<p>&nbsp;</p>
<p><span>0 set to magnetic north</span></p>
<p><span>→ SIX = position 6 = 180° = π radians</span></p>
<p>&nbsp;</p>
<p><span>SIX INCHES + Phillips map scale</span></p>
<p><span>→ 38.4 nominal map miles</span></p>
<p>&nbsp;</p>
<p><span>Pre-Z32 USGS map at the endpoint</span></p>
<p><span>→ Gravel Pit</span></p>
<p>&nbsp;</p>
<p><span>??T + geography</span></p>
<p><span>→ PIT</span></p>
<p>&nbsp;</p>
<p><span>and only after this had been found:</span></p>
<p>&nbsp;</p>
<p><span>1954 mining record</span></p>
<p><span>→ Sondgrath Bros. (Neary), Section 6, T7S R2W, Mt. Diablo Base &amp; Meridian</span></p>
<p>&nbsp;</p>
<p><span>The candidate is therefore:</span></p>
<p>&nbsp;</p>
<p><span>AT SIX SIX INCHES FROM MOUNT DIABLO PIT</span></p>
<p>&nbsp;</p>
<p><span>For me, the interesting point is not one single coincidence, but that the Z32 structure, Zodiac’s radians/inches hint, the dial geometry, the printed map distance, the contemporary Gravel Pit map, and the later-discovered Section 6 entry can be assembled into one coherent operation.</span></p>
<p>&nbsp;</p>
<p><span>But the distinctions must be preserved:</span></p>
<p>&nbsp;</p>
<p><span>P and I in PIT are derived geographically/semantically, not cipher-forced.</span></p>
<p><span>Section 6 / 666 is secondary post-hoc support.</span></p>
<p><span>The Phillips 66 branding is not necessary for SIX/SIX.</span></p>
<p><span>The modern coordinate check is a control, not the solution method Zodiac or a solver would have had to use in 1970.</span></p>
<p>&nbsp;</p>
<p><span>That is why I present this as a Z32 solution candidate, not as a proven decryption.</span></p>
<p>Small note: I’m posting this from my phone while away on vacation, and the forum’s mobile attachment handling was a bit awkward. I’m not entirely sure all the images came through correctly, so if anything is missing or out of order, that’s the reason. The text and source order are unchanged</p>
</div>
</div>
</div>
</div>
<div id="wpfa-1713" class="wpforo-attached-file"><a class="wpforo-default-attachment" href="//forum.zodiackillerciphers.com/wp-content/uploads/wpforo/default_attachments/1788274736-01_P66_Zodiac_MagN_Dial.jpg" target="_blank" title="01_P66_Zodiac_MagN_Dial.jpg"><i class="fas fa-paperclip"></i>&nbsp;01_P66_Zodiac_MagN_Dial.jpg</a></div>]]></content:encoded>
						                            <category domain="https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/">Zodiac Cipher Mailings &amp; Discussion</category>                        <dc:creator>Northkey</dc:creator>
                        <guid isPermaLink="true">https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/my-z32-candidate/</guid>
                    </item>
				                    <item>
                        <title>Z408, the last 18: Testing the final-line &#039;pull-down&#039; hypothesis (ChatGPT)</title>
                        <link>https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/z408-the-last-18-testing-the-final-line-pull-down-hypothesis-chatgpt/</link>
                        <pubDate>Wed, 08 Jul 2026 18:04:04 +0000</pubDate>
                        <description><![CDATA[Statistical Assessment of the Z408 Final-Line “Pull-Down” Hypothesis
1. Research question
The final 18 cipher symbols of the Zodiac Z408 cipher famously do not decode into meaningful plain...]]></description>
                        <content:encoded><![CDATA[<h1 class="PDq2pG_selectionAnchorContainer" data-start="0" data-end="78">Statistical Assessment of the Z408 Final-Line “Pull-Down” Hypothesis<span class="PDq2pG_selectionAnchor" aria-hidden="true"></span></h1>
<h2 data-start="80" data-end="103">1. Research question</h2>
<p data-start="105" data-end="460">The final 18 cipher symbols of the Zodiac Z408 cipher famously do not decode into meaningful plaintext under the established homophonic substitution solution. One proposed explanation is that at least some of these symbols were not enciphered text at all, but were generated by copying (“pulling down”) fragments of ciphertext from rows immediately above.</p>
<p data-start="462" data-end="491">The question tested here was:</p>
<blockquote data-start="493" data-end="625">
<p data-start="495" data-end="625">Does the final line of the Z408 exhibit a degree of vertical copying from previous rows that would be unlikely to occur by chance?</p>
</blockquote>
<p data-start="627" data-end="747">The purpose of the test was not to prove intent, but to determine whether the observed pattern is statistically unusual.</p>]]></content:encoded>
						                            <category domain="https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/">Zodiac Cipher Mailings &amp; Discussion</category>                        <dc:creator>shaqmeister</dc:creator>
                        <guid isPermaLink="true">https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/z408-the-last-18-testing-the-final-line-pull-down-hypothesis-chatgpt/</guid>
                    </item>
				                    <item>
                        <title>Modified Micheal Cole Z13 solution</title>
                        <link>https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/modified-micheal-cole-z13-solution/</link>
                        <pubDate>Thu, 21 May 2026 03:30:37 +0000</pubDate>
                        <description><![CDATA[Modified Micheal Cole Z13 solution. Well actually, i am going to ripoff, ermm, i mean riff off, Michael Cole&#039;s solution from 10years ago Cole:Cole presents his full solution as:I AM [the Zod...]]></description>
                        <content:encoded><![CDATA[<p>Modified Micheal Cole Z13 solution. <br /><br />Well actually, i am going to ripoff, ermm, i mean riff off, Michael Cole's solution from 10years ago <br />Cole: https://zodiacrevisited.com/my-name-is-cipher-solution/<br /><br />Micheal Cole presents his full solution as:<br />I AM  . _ . X . _ M I X<br /><br />~~~ The modification ~~~ <br /><br />As per Cole, the 1st underscore and the 'X' are the initials (forename, surname) of a name <br />So i think we can change the 2nd underscore to an 'a' resulting in:<br /><br /><br />I AM  .  .  . aM I <br /><br />then it links nicely to "I am mildly cerous" on the next line. <br /><br />This solution responds to Dr. D.C.B.Marsh's challenge by giving Z's name initials yet also reveals nothing.<br /><br /> It keeps the glyph count 3 part symmetry of 4-5-4<br /> Has its own symmetry of "I am", "am I"<br /> Ties into "I am mildly cerous"<br /> Reveals nothing about Z, just like the 408+340 (though this is a + point for Z, not for us )<br /><br /> Does not tie into "My name is ---" ( Though that long dash is peculiar )<br /> No question mark after the proposed "am I"<br /><br />~~ An expanded full solution ~~ <br />split Z13 into 3 parts <br /><br />AEN@ .K.M. *NAM <br />iam@ .K.M. amiM<br /><br />Key = {A:i, E:a, N:m, K:K, M:M, *:a, },<br />@ = Zodiac glyph , <br />* = Inverted Aries glyph<br /><br />I am Zodiac  am I Surname ?<br /><br />--Zodiac , expanded form of Zodiac glyph<br />--? Should be in the cipher for grammar reasons, but is not <br />--K corresponds to letter initial probably a First name/ forename (culturally dependant) <br />--Surname corresponds to the 2nd initial, in this case 'M'<br /><br />~~ Notes ~~<br />"My name is ---" could be the title of the cryptogram, specifically directing Prof D.C.B. Marsh to this cipher.<br /><br />D.C.B. Marsh's name has 3 periods in it ... coincidence ?? I like to think its a reference to to D.C.B Marsh's name.<br /><br />M.Coles says the 8-ball glyph is a taurus symbol and its unused elsewhere on all Z's ciphers<br />therefore it has a special significance - that is, it is a letter/word separator, like a space, period, etc.<br />None of Z's ciphers so far as is known use a letter/word separator except maybe this one.<br /><br />Super speculative is the philosophical angle of "I am Zodiac ... am I Surname?"<br />Is Surname a character played by Zodiac ? Is Zodiac another personality of Surname ?<br />--In the "Death machine" letter dated November 9th 1969, Zodiac says;<br />"I look like the description passed out only when I do my thing, the rest of the time I look entirle different."<br />Is it only Zodiacs appearance that changes or does his persona change too? <br />Will the real Zodiac please stand up. &#x1f642;   <br /><br />The envelope has a repeat of the word 'Editor' rotated 180 degrees. <br />https://zodiackillerciphers.com/wiki/index.php?title=Unsolved_13-character_%22My_name_is%22_cipher<br />--Could be a clue to this z13 or a clue to the z408 or nothing. <br />--Some of Z's other envelopes have peculiarities, <br />not sure if those peculiarities have been studied, they probably have.<br /><br />To be clear i am not saying this is the solution, it's just another speculative attempt.<br /><br />I kinda like the way it gives possible Name initials whilst at the same time gives nothing.<br />Credit to Micheal Cole, i just added a little tweak and made a messy post.</p>]]></content:encoded>
						                            <category domain="https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/">Zodiac Cipher Mailings &amp; Discussion</category>                        <dc:creator>letega</dc:creator>
                        <guid isPermaLink="true">https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/modified-micheal-cole-z13-solution/</guid>
                    </item>
				                    <item>
                        <title>Plotting your Z32 Solution using Google Maps (if you must)</title>
                        <link>https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/plotting-your-z32-solution-using-google-maps-if-you-must/</link>
                        <pubDate>Tue, 12 May 2026 06:13:22 +0000</pubDate>
                        <description><![CDATA[In follow-up to a previous thread—Plotting your Z32 Solution easily using Microsoft Word—we&#039;ll take a look here at how we might go about working out what adjustments we need to make in the h...]]></description>
                        <content:encoded><![CDATA[<p>In follow-up to a previous thread—<a href="https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/plotting-your-z32-solution-easily-using-microsoft-word/" target="_blank" rel="noopener">Plotting your Z32 Solution easily using Microsoft Word</a>—we'll take a look here at how we might go about working out what adjustments we need to make in the hope of being able to readily translate our map coordinates into corresponding lat./long. coordinates for use with Google Maps.</p>
<p>It is common to encounter the error of supposing that we can simply begin with the raw bearing we have applied to the map, couple this with the stated scale of 6.4 miles to the inch and then just run the math. It is, however, not as simple as this.</p>
<p>The Phillips 66 Map used by The Zodiac is, as we shall find, actually <em>not</em> scaled at anything close to 6.4 miles to the inch, nor is the straight-up direction (Map North) properly aligned to True North. It is for these reasons that, through ignoring these combining deviations, we find ourselves regularly presented with proposed bomb locations that do not match the location that would have been obtained by simply following the instructions and laying off the coordinates on the map, as given.</p>
<p>The starting point, then, must be a detailed analysis aimed at identifying the precise degree of each of these primary deviations. And, to do that, we must start with the map itself.</p>]]></content:encoded>
						                            <category domain="https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/">Zodiac Cipher Mailings &amp; Discussion</category>                        <dc:creator>shaqmeister</dc:creator>
                        <guid isPermaLink="true">https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/plotting-your-z32-solution-using-google-maps-if-you-must/</guid>
                    </item>
				                    <item>
                        <title>My mild obsession with Twin Peaks for the Z32 bomb location</title>
                        <link>https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/my-mild-obsession-with-twin-peaks-for-the-z32-bomb-location/</link>
                        <pubDate>Mon, 11 May 2026 00:49:23 +0000</pubDate>
                        <description><![CDATA[OK, so it hasn&#039;t yet got to the Close Encounters degree where I&#039;m building dinner time replicas out of mashed potato, but there is definitely something about San Francisco&#039;s Twin Peaks that ...]]></description>
                        <content:encoded><![CDATA[<p>OK, so it hasn't yet got to the <em>Close Encounters</em> degree where I'm building dinner time replicas out of mashed potato, but there is definitely something about San Francisco's <em>Twin Peaks</em> that has me keep coming back to it as the absolute ideal location for the Zodiac's "Buss Bomb," according to his Mark II design.</p>
<div align="center"><img src="https://www.exp1.com/blog/wp-content/uploads/sites/7/2020/09/Twin-Peaks-at-Night-e1599744799244.jpg" /></div>
<p>Topographically we have the sloping hillside with adjacent road, surely frequented by school buses for both day outings as well as regular school runs, all combining to meet the logistics of the detailed mechanism we had drawn for us. Yet, more than just this, there is something oddly compelling about the existence of precisely these features at such an elevated and <em>visible</em> landmark—there for all the inhabitants of San Francisco to see and notice daily.</p>
<p>Were there to have actually been an explosion here, people would have been able to stand and point towards it from wherever they found themselves, with only the minimal of effort. With a telescope or an excellent pair of binoculars, it could even be scoped from the very peak of Mount Diablo itself. Even a search here for an ultimately absent device would have been enough to draw the daily attention of tens of thousands at a time.</p>
<p>The North-East face of the twin-peaked hill—precisely that face where the bomb would have to be placed to catch the early morning Summer sun—is just the very face which looms in the distance from many a vantage point along the majority of Market Street, heading west.</p>
<p>And maybe—just <em>maybe</em>—it is a schematic for these very Peaks that we have encoded in the otherwise mysterious symbol added to the Halloween card.</p>
<p>In any event, if there is any new potential solution I see offered to the Z32 cipher, my first thought is always to check whether it will reach from Mount Diablo along the "eighth radian" to somewhere around the middle of the San Francisco Peninsula, and I am all the less excited whenever it doesn't.</p>]]></content:encoded>
						                            <category domain="https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/">Zodiac Cipher Mailings &amp; Discussion</category>                        <dc:creator>shaqmeister</dc:creator>
                        <guid isPermaLink="true">https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/my-mild-obsession-with-twin-peaks-for-the-z32-bomb-location/</guid>
                    </item>
				                    <item>
                        <title>Z32 form - why these specific constraints?</title>
                        <link>https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/z32-form-why-these-specific-constraints/</link>
                        <pubDate>Mon, 04 May 2026 13:35:18 +0000</pubDate>
                        <description><![CDATA[Aside from the fact that the plaintext of the Z32 cipher is, as its name implies, 32 characters in length (assuming a simple homophonic substitution cipher), there are three further constrai...]]></description>
                        <content:encoded><![CDATA[<p>Aside from the fact that the plaintext of the Z32 cipher is, as its name implies, 32 characters in length (assuming a simple homophonic substitution cipher), there are three further constraints that we have to work with in any attempt at deciphering the text:</p>
<ol>
<li>the <em>first</em> and the <em>twenty-sixth</em> letter must be the same;</li>
<li>as, also, the <em>second</em> and the <em>final</em> (thirty-second) letter;</li>
<li>and, finally, the same for the <em>sixth</em> and the <em>fourteenth</em> letter.</li>
</ol>
<p>This is all that we have to work with.</p>
<p>Yet, it is perhaps worthwhile considering the question as to why it was these specific three constraints that the author chose to give to us at the outset, and not any of the alternatives that must have been equally possible.</p>
<div align="center"><img src="https://forum.zodiackillerciphers.com/wp-content/uploads/wpforo/default_attachments/1777901718-Z32_constraints.jpg" /></div>
<p>Why, in particular, does he seem especially keen to direct us to the relationship between the very beginning and end of the cipher?</p>
<p>&nbsp;</p>
<div id="wpfa-1557" class="wpforo-attached-file"><a class="wpforo-default-attachment" title="Z32_constraints.jpg" href="//forum.zodiackillerciphers.com/wp-content/uploads/wpforo/default_attachments/1777901718-Z32_constraints.jpg" target="_blank" rel="noopener"><i class="fas fa-paperclip"></i> Z32_constraints.jpg</a></div>]]></content:encoded>
						                            <category domain="https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/">Zodiac Cipher Mailings &amp; Discussion</category>                        <dc:creator>shaqmeister</dc:creator>
                        <guid isPermaLink="true">https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/z32-form-why-these-specific-constraints/</guid>
                    </item>
				                    <item>
                        <title>Plotting your Z32 Solution easily using Microsoft Word</title>
                        <link>https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/plotting-your-z32-solution-easily-using-microsoft-word/</link>
                        <pubDate>Wed, 15 Apr 2026 01:11:03 +0000</pubDate>
                        <description><![CDATA[So, you&#039;ll probably have your own easy way of doing this. But, for those that don&#039;t yet, here&#039;s one simple way to quickly plot your Z32 solution on the Phillips 66 map and discover where it ...]]></description>
                        <content:encoded><![CDATA[<p>So, you'll probably have your own easy way of doing this. But, for those that don't yet, here's one simple way to quickly plot your Z32 solution on the Phillips 66 map and discover where it actually lands you.</p>
<p>Here I'm going to be using only an old version of Microsoft Word and a copy of the Zodiac Phillips Map. The example I'm going to be working with is one chosen completely at random, but which nonetheless has a nice, natural 'read' to it.</p>
<p>We use, then:</p>
<pre contenteditable="false">AT FOUR AND A THIRD INCHES RADIAN EIGHT</pre>
<p>from:</p>
<div align="center"><img src="https://forum.zodiackillerciphers.com/wp-content/uploads/wpforo/default_attachments/1776215463-z32_plaintext_example.jpg" /></div>
<p>'RADIAN EIGHT', here, assumes the given division of the superimposed compass rose over Mount Diablo, which The Zodiac has suggested we divide into twelve equal sectors of 30° each. Radian eight, therefore, it that "radial line" extending from Mount Diablo at a bearing of (8 × 30°) + 17° = 257° from map north, the last term added to make the adjustment to Magnetic North, as indicated.</p>
<p>Let's get into it, then.</p>
<p></p>
<div id="wpfa-1488" class="wpforo-attached-file"><a class="wpforo-default-attachment" title="z32_plaintext_example.jpg" href="//forum.zodiackillerciphers.com/wp-content/uploads/wpforo/default_attachments/1776215463-z32_plaintext_example.jpg" target="_blank" rel="noopener"><i class="fas fa-paperclip"></i> z32_plaintext_example.jpg</a></div>]]></content:encoded>
						                            <category domain="https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/">Zodiac Cipher Mailings &amp; Discussion</category>                        <dc:creator>shaqmeister</dc:creator>
                        <guid isPermaLink="true">https://forum.zodiackillerciphers.com/community/zodiac-cipher-mailings-discussion/plotting-your-z32-solution-easily-using-microsoft-word/</guid>
                    </item>
							        </channel>
        </rss>
		