A quick reference for casting NATORI-ON-PSYFR: the workflow, the vocabulary, a cookbook of copy-ready operations, and answers to the questions that come up first. Tap any formula to copy it, then paste into the engine's Custom operation field.
In The Oracle, add two or more anchor dates — type them in, or scroll to The Ledger and hit seed ⚓ on any documented event. Two anchors is the minimum; more anchors = more interval pairs to project from.
The 19-Operation Pack loads by default. Swap it for a themed pack (138, 19 Metonic, Phoenix Lattice, Golden) with the violet buttons, or paste your own from the cookbook below.
Press ⟳ Cast the Oracle. Every anchor-pair interval is run through every operation, and each projected date is scored against the chronology. Switch the scoring lens (V8 / V7) to re-rank live.
Scroll to The Convergence — where several independent operations land on the same date. That agreement is the real signal. Click any result to read it on The Wheels.
After a cast, hit ✦ NOVEL ONLY to hide the ECHO rows (projections that just land back on an input). What remains are the dates the chronology didn't already hand you — that's where the discoveries live.
An anchor — a known date you feed the engine. Every cast needs at least two.
The number of axial rotations (days) between a pair of X-Dates. Counting turns of the Earth, not years — the Archaix way.
An equation that transforms Y into a day-offset. Always begins X1+ or X2+.
A projected date — the output. Offset applied to X1 or X2, then read across every calendar.
A Z-Date that lands back on an input anchor (±1 day). A confirmation, not a discovery — dimmed and tagged.
When several different operations agree on one date. The strongest signal in the whole instrument.
The resonance number-set (138, 831, 19 …). A projection whose interval or offset matches one scores extra.
Tap any formula to copy it, then paste into the engine's Custom operation box and press + Operation. Every one below is validated against the grammar — none will throw an error. Y is the interval in days.
X2+oph_round(Y)X1+YX2+oph_flip(oph_round(Y))X1+oph_flip(oph_round(Y))X1+oph_flip(oph_round(Y/OPH_PHI))X2+oph_flip(Y)+19X2+oph_round(Y/138)*138X2+Y+138X2+Y*138/100X1+oph_round(Y/414)*414X1+oph_round(Y/19)*19X2+Y+19X1+Y*19/10X2+oph_round(Y/6940)*6940X2+Y/OPH_PHIX1+Y*OPH_PHIX1+(Y/2)*OPH_PIX2+Y/OPH_CRVX2+oph_round(Y/OPH_PHI/OPH_PHI)X2+oph_round(Y/792)*792X1+oph_round(Y/600)*600X2+Y*360/365.2422Three rules: it must start with X1+ or X2+; it may use only Y, numbers, the constants, the oph_ functions, and arithmetic + − * / ( ); and it must evaluate to a number. Anything else is rejected.
| Token | Meaning |
|---|---|
| X1 / X2 | The earlier / later anchor of the pair. Your equation begins with one of them, plus an offset. |
| Y | The interval between the two anchors, in days (axial rotations). |
| OPH_PHI | Golden ratio — 1.61803398875 |
| OPH_PI | Archaix π — 3.14 |
| OPH_CRV | The curvature constant — 5.08 |
| oph_flip(n) | Reverse the digits — 138 → 831, 19 → 91. The palindrome maker. |
| oph_round(n) | Nearest whole day. Use it to keep offsets clean. |
| oph_floor / oph_ceil | Round down / up to a whole day. |
| oph_abs / oph_sqrt | Absolute value / square root (of the absolute value). |
Tip: a bare x between terms is read as multiply, the same as *. So X2+YxOPH_PI and X2+Y*OPH_PI are identical.
Real results from the default engine — follow along and you'll see the same numbers.
A strength-4 convergence on 2040 — four independent operations, from two different anchor pairs, all land on the Phoenix year. That agreement is the signal.
And the eclipse filter lights up two projections sitting on the documented cataclysm: 15 May 2040 on a total lunar eclipse (score 11) and 10 May 2040 on a partial solar (score 12). The engine found that the Phoenix date carries a real eclipse.
The operation X2+Y*138/100 projects onto 1902 CE (score 11) — a Phoenix node that is also a documented event (Charles Fort's "other Dark Age"). The two oldest cataclysms, scaled by 1.38, point straight at a recorded modern Phoenix year.
You'll also notice the engine re-deriving the Flood itself nearby — a confirmation the chronology is internally consistent.
Under V8, the top novel projection is 10 May 2040 (score 12) — a Phoenix node, documented, on a solar eclipse. History wins.
Flip to V7 and the ranking inverts to 1 June 2026 (score 6) — a date that wears 138 and aligns Metonically. The numbers win. Same cast, two different questions.
Because one of your anchors is reproducible by the operations. If you seed 2040 and an operation projects right back onto 2040, that's an echo — true, but circular. It's the engine confirming its own input.
Hit ✦ NOVEL ONLY to hide echoes, or remove the anchor that's being re-derived and re-cast to hunt for genuinely new convergences.
V8 · Chronology-first (default) rewards landing on the real timeline — Phoenix nodes and documented events score highest. Use it to ask "which projections resonate with history?"
V7 · Numbers-first lets the sacred numbers lead — 138 in the digits, palindromes, and MSRF outrank a documented cataclysm. Use it to ask "which projections resonate with the signatures?" The same cast can rank completely differently under each.
Strength is the number of distinct operations that independently landed in the same window. Strength 4 means four different equations agree — far stronger than any single high-scoring projection.
Start at ± 30 days. Tighten to exact day for the rarest coincidences; widen to Same year to see which years the whole pack points at. Wider windows find more (and looser) agreement.
The precomputed eclipse tables cover roughly 1–3000 CE. Projections outside that range simply carry no eclipse tag — the engine degrades gracefully rather than guessing. Most future-facing casts (2040, 2046 …) are well inside coverage.
Yes — the date engine was verified against every known Archaix anchor before release: today reads AM 5920 / LC 5138, the Great Flood lands on AM 1656, Petrie's survey year on AM 5776, and all 24 Phoenix events sit exactly on the 138-lattice (mod 138 = 108). The šar is reckoned as a turning of the stars — a day — per Breshears.
Yes. ⤓ Save .json writes your whole cast — anchors, operations, scoring lens, and convergence window — to a file. ⤒ Load reads one back. It's the same portable model as the original Ophis .oph files, so you can keep a 138-pack, a 19-pack, and a Phoenix-pack as named configurations and share them.
Click any row in the results or convergence table, or any ledger entry. The date is sent to The Wheels, where all seven reckonings re-read that moment — Phoenix, Nemesis, NER, Annus Mundi, Mayan Long-Count, Anunna turnings, and the Metonic moon. You can also drag the dial directly.
No. This is a worldbuilding and study instrument that renders Jason Breshears' Archaix thesis as living predictive calendrics. The chronology, the šar-as-day reckoning, and the cycle lattice are presented as that thesis — not as established archaeology. Deep-past conversions are cycle-true rather than historically observed.
You need at least two active anchors (the ✓ box lit) and at least one active operation. If the results are empty after a cast, the filter may be too tight — click ALL, or widen the convergence window. The engine also skips intervals over ~3,000,000 days and projections outside roughly 5400 BC – 4000 CE.
Tab moves between every control; Space or Enter toggles the ✓ checkboxes and buttons. The ☾/☀ switch flips light/dark (it follows your system on first visit), and A− / A / A+ scales everything — both remembered between sessions. Reduced-motion settings are honoured.