13

Knowability and falsifiability

5 min read

At a glance

The fan [the structure] survives what the chain [the chronology] does not survive.
Falsifiability: what would refute the model

Knowable, testable, kept separate

  1. 1Mt 24:32-33, 36; 1 Th 5:4; Dan 12:4

    The season

    the season has been made knowable; the year rests on the chronology and bears its risk

    season is no specific year

  2. 2Dan 9:27a

    The breaking points

    fixed in advance in a deposited falsification protocol

    covenant gate Tishri 2027, midpoint condition Purim 2031, a subordinate calendar layer

  3. 3

    After 2034

    if autumn 2034 passes without the visible return, the chronological keystone falls, not the structure

    a shifted window is a new hypothesis, without credit from the old one

the frame

the structural foundation: defended with a firm hand

the window

the chronological foundation: held with an open hand; convergent support that the window is approximately right, but the precise year rests on the chain, above all on the Masoretic epoch

Firm about the form, modest about the date.

In-depth:

Knowability: frame over against window, and the two foundations

The model does not stand or fall as a whole; it has two foundations, and they must be kept separate.

The first is the structural foundation: the whole/peak distinction, the two cohortstwo cohortsTwo companies in opposite relation to the one tribulation: the Bride taken away from the whole before the peak (Rev 7; 12:5 — upward, the throne); the remnant kept through the peak (Matt 24 — downward, the wilderness; Rev 12:6; Jacob's trouble). Two cohorts, not a two-layer Bride., the thlipsis/orgē key, the sixth-seal position. This is strong and redundant (§22), and it is largely independent of the precise date. This is the frame — the form of the end times as the model reads it.

The second is the chronological foundation: the master clockmaster clockThe overarching biblical time mechanism that divides salvation history into fixed periods., the week 2027-2034, the midpoint 2031. This is chain-like and externally-dependent. This is the window — the placement of the frame in time.

The frame is defended with a firm hand; the window held with an open hand. There is convergent support for the window — several lines point to the same period (the 6,000 years, the generation since 1948, and, as confirmation not as foundation, the solar eclipses and the year-for-day line of the Dome of the Rock — the abomination on the Temple Mount, completed in 72 AH (691/692), plus 1,335 years to TishriTishriThe seventh month of the Jewish ecclesiastical calendar but the first month of the civil calendar, corresponding to September-October. Tishri 1 is the Feast of Trumpets (Rosh Hashanah); Tishri 10 is the Day of Atonement (Yom Kippur); Tishri 15-21 is the Feast of Tabernacles. The seventieth week opens on Tishri 1, 2027 in the chronology proposed in this book. Treated throughout, with technical deta 2025/26 or 2026/27, the threshold of the window, as type of the 1,335 days still to come, §20) — but that convergence must be honestly weighed: some lines are not fully independent, and the eclipse- and Dome-lines carry the least weight — the latter hangs on a pliable year-for-day reckoning (anchor, counting). The net picture: the window has convergent support that raises confidence that it is approximately right; the precise year (2034 over against a near year) rests on the chain, above all on the Masoretic epoch.

Here the model touches the paradox of Matthew 24:36. The solution is not to evade the text but to honour it on its own level: the season has been made knowable — Jesus Himself commands to read the fig tree (Mt 24:32-33), Paul says the day does not overtake the watchful as a thief (1 Th 5:4), Daniel is told that the words are unsealed in the time of the end (Dan 12:4). But season is no specific year. The season rests on the knowability that Scripture itself promises; the year rests on the chronology, and bears its risk. Whoever holds this distinction can present the model with a good conscience: firm about the form, modest about the date.

Falsifiability: what would refute the model

An honest position says what it would die of. The solar eclipse of 2027 is expressly disclaimed as non-founding and non-trigger — a marker that the model cannot fail, it also cannot confirm. But its earlier touchstones the model fixes in advance, in operational, deposited form, and after 2034 it becomes sharply falsifiable: if that autumn passes without the visible return, the chronological keystone falls. There the model sticks out its neck, and that speaks for its intellectual honesty.

The protocol, deposited. This model is testable and its breaking points are fixed beforehand in a separately deposited falsification protocol — Pre-Registered Falsification Protocol for the Pre-Abomination Model (Zenodo, deposited alongside this paper) — which is the binding text wherever any formulation elsewhere, including in this paper, is looser. Its architecture, in brief. The covenant gate: the covenant with the many (Dan 9:27a) is expected to come into force at Trumpets, 1 Tishri 5788, 2 October 2027 — Daniel's dated act is the making strong; preparation and signature may precede it, even by years. If no publicly identifiable covenant has come into force by the end of Tishri 5788 (31 October 2027), the primary configuration is dead, and the cascade is strict: the 1,335 days never begin, every downstream prediction is void with the thesis, and no calendar call will be scored over a fallen model. No event will be retroactively reinterpreted into covenant status; near-misses are misses. A publicly identifiable covenant is a treaty or declaration that meets all three requirements: it is publicly signed or declared in force between 1 and 30 Tishri 5788; Israel is a party, or is bound into it by a large majority of the surrounding states; and it regulates peace, security or worship in Jerusalem, or all three. A resumed daily sacrifice in the months before the covenant may count as a hit; the expectation remains that it is bound up with the covenant. The midpoint condition: if no abomination stands within the Hebrew day 14 Adar 5791 — sunset 8 March to sunset 9 March 2031, Jerusalem — the thesis has fallen, whatever any calendar authority declares in any year; the halting of the offerings is that day's necessary consequence, for the abomination and the loyalty offering cannot coexist on the Mount. If no sacrificial service is running on the Temple Mount at Purim 2031, the midpoint condition is not met. That day is the celebrated Purim of the conventional calendar; that the count begins there and not on the clock, where Purim falls on 6 April 2031, is an explicit presupposition of the model (chapter 3). The calendar layer, subordinate, within the week (the springs of 2028 through 2034): the clock intercalates in 2028, 2031 and 2034, not in 2029, 2030, 2032 and 2033; the conventional calendar intercalates in 2030 and 2033. The spring of 2026 fell before the week and does not count as a test; it is named here all the same: the clock intercalated, no observing group did (Karaite: first month from 20 March 2026). With this come referees named in advance in a hierarchy the model itself predicts (a reconstituted temple authority determining the months by observation; failing that, the Karaite determination; failing that, the in-land aviv reports), two kill-conditions (a declared intercalation for spring 2033 fells the model; a declared non-intercalation for spring 2034 fells the terminus dating; if 2028 and 2030 do not give what the clock expects, those are misses for the calendar layer, not a kill), a degradation rule and a fall rule stated in advance, and scoring rules that remain operative in the model's own expected world: kill-conditions fire only on rulings, corroborations are claimed only on rulings, and the model earns nothing from silence. And what no historical outcome can falsify: the arithmetic itself — the day-structure and its corridor property, verified on independently written engines and invariant across all 57 aviv-plausible intercalation patterns — with the shield running one way only: the surviving mechanism earns a fallen application no credit. (The operational form of this protocol — deposited in advance where the author cannot amend it, tolerances that will not be widened, the public record as referee — is owed to R. J. Allinson, whose falsification discipline is exemplary in this genre.)

GateWhat is expectedWhen the model falls
The covenant gatethe covenant with the manycovenant with the manyThe covenant that the coming prince (weighed) makes strong with overwhelming force for the many in Daniel 9:27, for one week; in the half of the week he makes sacrifice and offering cease. (Dan 9:27a) is to come into force at Trumpets, 1 Tishri 5788, 2 October 2027no publicly identifiable covenant in force by the end of Tishri 5788 (31 October 2027): the primary configuration is dead, and every downstream prediction is void. A publicly identifiable covenant is a treaty or declaration that meets all three requirements: it is publicly signed or declared in force between 1 and 30 Tishri 5788; Israel is a party, or is bound into it by a large majority of the surrounding states; and it regulates peace, security or worship in Jerusalem, or all three.
The midpoint conditionthe abomination within the Hebrew day 14 AdarAdarTwelfth month of the Hebrew religious calendar (late winter). In leap years, a thirteenth month — Adar II — is inserted by the rabbinic authorities to keep the lunar months aligned with the solar seasons. See Intercalary month, Aviv rule. 5791 (sunset 8 March to sunset 9 March 2031, Jerusalem): the celebrated Purim, not that of the clock (6 April 2031); a presupposition, see chapter 3no abomination on that day, or no sacrificial service running on the Temple Mount at Purim 2031: the thesis has fallen, whatever any calendar authority declares
The calendar layer, subordinatewithin the week (the springs of 2028 through 2034): the clock intercalates in 2028, 2031 and 2034, not in 2029, 2030, 2032 and 2033; the conventional calendar in 2030 and 2033; the spring of 2026 (before the week) is named, not scoreda declared intercalation for spring 2033 fells the model; a declared non-intercalation for spring 2034 fells the terminus dating; if 2028 and 2030 do not give what the clock expects, those are misses for the calendar layer, not a kill
The arithmeticthe day-structure and its corridor property, invariant across all 57 aviv-plausible intercalation patternsfalsifiable by no historical outcome; the surviving mechanism earns a fallen application no credit

But — and this is the architectural core — if the chronological keystone falls, the structure does not fall. The whole/peak distinction, the two cohorts, the thlipsis/orgē distinction, the address of 3:10: these stand independent of the year. A failed 2034 would prove that the dating failed, not that the Bride shares the wrath or that the great tribulation is one whole with its peak. The fan survives what the chain does not survive. That is precisely why the two foundations must remain separate: it is possible that the frame is true and the window shifted, though a shifted window is a new hypothesis, without credit from the old one (the protocol above). In that case most of what this paper defends remains standing, while only the placement in time is revised.