Where Daniel supplies the structure, the creation clock supplies the consummation. The model rests on a 6,000-year master clockmaster clockThe overarching biblical time mechanism that divides salvation history into fixed periods.: 6,000 years of human history, followed by the seventh-day Sabbath of the millennium — the ancient typology of the six days of creation and the seventh rest, read through the key "one day is with the Lord as 1,000 years" (2 Pet 3:8).
The clock is built on a symmetrical architecture: 2,520 + 480 + 480 + 2,520 = 6,000. The 2,520 is seven prophetic times (7 × 360); the 480 echoes the Exodus-to-temple span of 1 Kings 6:1; and the two pairs are mirrored about a centre. Anchored on the Masoretic chronology from creation, the clock ends in autumn 2034 — and thereby, counting back across the seven-year week, the seventieth weekseventieth weekThe final seven years of the 490-year contract: the week of the coming prince, wholly future (weighed). The juridical week of 27 to 34 is its type, not a first fulfillment. begins in 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 2027.
Here belongs the first, and weightiest, honest test of this part. Of all the anchors the master clock bears the most — it fixes the consummation, and with it the whole week — and it has at the same time the most play. The degrees of freedom are real: the Masoretic creation epoch over against the roughly 1,500-years-longer Septuagint genealogies; the exact AM dating; the anchoring across the era boundary. The full derivation lies in God's Algorithm and is not repeated here. But it must be said here: the existential stake of the model — the year 2034 — rests above all on this one anchor, and this one anchor has, of them all, the largest margin. Whoever wishes to test the model, tests here. That is no weakening of the position; it is the place where the position itself invites the test.
The two midpoint anchors: Purim and Passover 2031
The midpoint of the week is fixed by two anchors that lie about 30 days apart — and it is precisely that distance which carries the coherence of the Danielic numbers.
The first anchor is the abomination at Purim 2031 (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. 14-15, around March 2031): the setting up of the abomination of desolation, the starting point of the 1,290 days (Dan 12:11) and the 1,335 days (Dan 12:12). The second is Passover 2031 (15 NisanNisanFirst month of the Hebrew religious calendar (early spring). Pesach falls on 14 Nisan; the Crucifixion fell on 14 Nisan in AD 31 (weighed)., April 8, 2031): the starting point of the 1,260 days of the nourishing of the woman in the wilderness, to which she fled at the signal of the abomination (Rev 12:6, 14; Rev 11:3). The 42 months of the beast (Rev 13:5) are the wider measure: they already begin between Purim and Passover.
The keystone is of a remarkable simplicity: the difference 1,290 − 1,260 = 30 days is exactly the window from Purim to the first day of Passover (14 Adar → 15 Nisan). The two counts, from two feasts, close on one autumn 2034. And the typology seals what the numbers reckon: Purim — the feast of Haman's thwarted genocide — becomes the trigger date of the adversary's final genocide attempt; Passover — the feast of the exodus — becomes the beginning of the preservation of the remnant in the wilderness. The abomination comes on the day of the thwarted extermination; the deliverance on the day of the exodus. This is no chance coincidence but text-internal architecture: the kind of coherence a model cannot force but can only discover. The same form already stands in Genesis 15: two numbers for one exodus, 400 and 430, with 30 years between them. Paul counts the 430 from the covenant (Gal 3:17); the 400 run from the persecution of the seed (Gen 15:13; Gal 4:29). There too two counts with a difference of 30 close on one endpoint; and the verb of Galatians 4:29, "persecute," runs through Pharaoh's pursuit (Exod 14) to the dragon that persecutes the woman (Rev 12:13). (Formal likeness, weighed; no day-year key.)
The three counts run from these anchors to the return. The 1,260 days from Passover 2031 carry the preservation of the woman and the two witnesses; the 42 months of the beast are wider and already begin between Purim and Passover. The 1,290 days from Purim 2031 reach 30 days further (the Purim-Passover window). The 1,335 days reach 45 days further still than the 1,290 — "blessed is he who waits and reaches to the 1,335 days" (Dan 12:12) —: to the last possible day of the return, the day before the Sabbath on which the kingdom begins. The numbers close, with their familiar differences of 30 and 45 days, around autumn 2034 — consistent with the master clock.
Honestly: the landing on the exact day depends on the Hebrew calendar intercalations between 2031 and 2034; the precise calculation lies in God's Algorithm. Here the structure of the counts closes at the level of the architecture, to be refined at the level of the day.
Two tracks, thirty days apart — the 1,260, 1,290 and 1,335 days of Daniel 12 from Purim and Passover 2031, assuming one Adar II in the spring of 2034.
The built-in leap year. That refinement at the level of the day has since been carried out, and it yielded a finding that must be briefly named here; the full computation stands in God's Algorithm (chapter 12). On the rabbinic conventional calendar the counts land 30 days past the feasts: Purim 2031 (March 9) plus 1,335 is November 3, 2034 — 21 Cheshvan, one lunar month beyond Hoshana Rabbah. The model therefore presupposes one observational Adar II in the spring of 2034 that the fixed cycle does not have there — an explicit, testable presupposition. Now: apply the standard leap positions of the cycle to the corrected year-count of the master clock — the year the fixed calendar calls 5794 is, on the clock, 5999 (the clock counts from year 0, as in God's Algorithm: in autumn 2034 the 6,000 years are complete and the 6001st year begins, clock year 6000) — and 5999 (position 14 of the cycle) is arithmetically of necessity a leap year, independently of which Gregorian year one identifies as AM 6000: the dial carries its own closing month, and Daniel's 1,335 — the number that for a century and a half looked 45 days too long — is exactly the length that built-in Adar II fills. With molad and postponement rules fully reckoned, the celebrated Purim of March 9, 2031 then counts exactly 1,335 days to the true Hoshana Rabbah of clock year 6000 (November 3, 2034), the first year after the full 6,000. That the count begins on the celebrated calendar and ends on the true one is itself a presupposition: on the clock, Purim 5996 lies on April 6, 2031, and from that Purim to Hoshana Rabbah 6000 it is 1,307 days; rabbinic, consistently, 1,305. And the same arithmetic, run backward 2,000 years, lays 14 Nisan of the true year 3996 on Wednesday, April 25, AD 31 (Julian) — the independently, astronomically argued crucifixion date, to the day and to the weekday: at both hinges of the clock the conventional count is one month early, and the true position supplies the missing month. Honestly stated, in full: five of the 19 possible epoch stances reproduce this pattern, and the grid assignment of the two endpoints adds a further lever of one reading in four — counted honestly, the composite figure carries roughly one in 15 (no one-in-a-thousand); the weekday hit is postponement-rule dependent (±1 day); and the finding presupposes the 6,000 terminus, so that it supports the model from within and does not prove it from without. But the +205-year shift was derived from the genealogical registers and the land-sabbath count, with no calendar input, and it nevertheless landed in the successful set — to the day. Its status, then: interpreted, without weight in the weighing (God's Algorithm, appendix D). Counted over the years, moreover, the mixed construction hits often: begin on the rabbinic calendar and end on the clock calendar, and the 1,335 lands on Hoshana Rabbah in roughly two years out of five. Testable consequence, stated in decision form rather than field form: the observational communities will declare a thirteenth month in the spring of 2034, so that their Passover falls around early May and their autumn feasts in early November — as the clock equally makes the spring of 2031 a leap position, with a Passover around May 6, 2031, a full month after the rabbinic date.
The master clock: 6,000 years to autumn 2034
Where Daniel supplies the structure, the creation clock supplies the consummation. The model rests on a 6,000-year master clockmaster clockThe overarching biblical time mechanism that divides salvation history into fixed periods.: 6,000 years of human history, followed by the seventh-day Sabbath of the millennium — the ancient typology of the six days of creation and the seventh rest, read through the key "one day is with the Lord as 1,000 years" (2 Pet 3:8).
The clock is built on a symmetrical architecture: 2,520 + 480 + 480 + 2,520 = 6,000. The 2,520 is seven prophetic times (7 × 360); the 480 echoes the Exodus-to-temple span of 1 Kings 6:1; and the two pairs are mirrored about a centre. Anchored on the Masoretic chronology from creation, the clock ends in autumn 2034 — and thereby, counting back across the seven-year week, the seventieth weekseventieth weekThe final seven years of the 490-year contract: the week of the coming prince, wholly future (weighed). The juridical week of 27 to 34 is its type, not a first fulfillment. begins in 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 2027.
Here belongs the first, and weightiest, honest test of this part. Of all the anchors the master clock bears the most — it fixes the consummation, and with it the whole week — and it has at the same time the most play. The degrees of freedom are real: the Masoretic creation epoch over against the roughly 1,500-years-longer Septuagint genealogies; the exact AM dating; the anchoring across the era boundary. The full derivation lies in God's Algorithm and is not repeated here. But it must be said here: the existential stake of the model — the year 2034 — rests above all on this one anchor, and this one anchor has, of them all, the largest margin. Whoever wishes to test the model, tests here. That is no weakening of the position; it is the place where the position itself invites the test.
The two midpoint anchors: Purim and Passover 2031
The midpoint of the week is fixed by two anchors that lie about 30 days apart — and it is precisely that distance which carries the coherence of the Danielic numbers.
The first anchor is the abomination at Purim 2031 (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. 14-15, around March 2031): the setting up of the abomination of desolation, the starting point of the 1,290 days (Dan 12:11) and the 1,335 days (Dan 12:12). The second is Passover 2031 (15 NisanNisanFirst month of the Hebrew religious calendar (early spring). Pesach falls on 14 Nisan; the Crucifixion fell on 14 Nisan in AD 31 (weighed)., April 8, 2031): the starting point of the 1,260 days of the nourishing of the woman in the wilderness, to which she fled at the signal of the abomination (Rev 12:6, 14; Rev 11:3). The 42 months of the beast (Rev 13:5) are the wider measure: they already begin between Purim and Passover.
The keystone is of a remarkable simplicity: the difference 1,290 − 1,260 = 30 days is exactly the window from Purim to the first day of Passover (14 Adar → 15 Nisan). The two counts, from two feasts, close on one autumn 2034. And the typology seals what the numbers reckon: Purim — the feast of Haman's thwarted genocide — becomes the trigger date of the adversary's final genocide attempt; Passover — the feast of the exodus — becomes the beginning of the preservation of the remnant in the wilderness. The abomination comes on the day of the thwarted extermination; the deliverance on the day of the exodus. This is no chance coincidence but text-internal architecture: the kind of coherence a model cannot force but can only discover. The same form already stands in Genesis 15: two numbers for one exodus, 400 and 430, with 30 years between them. Paul counts the 430 from the covenant (Gal 3:17); the 400 run from the persecution of the seed (Gen 15:13; Gal 4:29). There too two counts with a difference of 30 close on one endpoint; and the verb of Galatians 4:29, "persecute," runs through Pharaoh's pursuit (Exod 14) to the dragon that persecutes the woman (Rev 12:13). (Formal likeness, weighed; no day-year key.)
The three counts run from these anchors to the return. The 1,260 days from Passover 2031 carry the preservation of the woman and the two witnesses; the 42 months of the beast are wider and already begin between Purim and Passover. The 1,290 days from Purim 2031 reach 30 days further (the Purim-Passover window). The 1,335 days reach 45 days further still than the 1,290 — "blessed is he who waits and reaches to the 1,335 days" (Dan 12:12) —: to the last possible day of the return, the day before the Sabbath on which the kingdom begins. The numbers close, with their familiar differences of 30 and 45 days, around autumn 2034 — consistent with the master clock.
Honestly: the landing on the exact day depends on the Hebrew calendar intercalations between 2031 and 2034; the precise calculation lies in God's Algorithm. Here the structure of the counts closes at the level of the architecture, to be refined at the level of the day.
The built-in leap year. That refinement at the level of the day has since been carried out, and it yielded a finding that must be briefly named here; the full computation stands in God's Algorithm (chapter 12). On the rabbinic conventional calendar the counts land 30 days past the feasts: Purim 2031 (March 9) plus 1,335 is November 3, 2034 — 21 Cheshvan, one lunar month beyond Hoshana Rabbah. The model therefore presupposes one observational Adar II in the spring of 2034 that the fixed cycle does not have there — an explicit, testable presupposition. Now: apply the standard leap positions of the cycle to the corrected year-count of the master clock — the year the fixed calendar calls 5794 is, on the clock, 5999 (the clock counts from year 0, as in God's Algorithm: in autumn 2034 the 6,000 years are complete and the 6001st year begins, clock year 6000) — and 5999 (position 14 of the cycle) is arithmetically of necessity a leap year, independently of which Gregorian year one identifies as AM 6000: the dial carries its own closing month, and Daniel's 1,335 — the number that for a century and a half looked 45 days too long — is exactly the length that built-in Adar II fills. With molad and postponement rules fully reckoned, the celebrated Purim of March 9, 2031 then counts exactly 1,335 days to the true Hoshana Rabbah of clock year 6000 (November 3, 2034), the first year after the full 6,000. That the count begins on the celebrated calendar and ends on the true one is itself a presupposition: on the clock, Purim 5996 lies on April 6, 2031, and from that Purim to Hoshana Rabbah 6000 it is 1,307 days; rabbinic, consistently, 1,305. And the same arithmetic, run backward 2,000 years, lays 14 Nisan of the true year 3996 on Wednesday, April 25, AD 31 (Julian) — the independently, astronomically argued crucifixion date, to the day and to the weekday: at both hinges of the clock the conventional count is one month early, and the true position supplies the missing month. Honestly stated, in full: five of the 19 possible epoch stances reproduce this pattern, and the grid assignment of the two endpoints adds a further lever of one reading in four — counted honestly, the composite figure carries roughly one in 15 (no one-in-a-thousand); the weekday hit is postponement-rule dependent (±1 day); and the finding presupposes the 6,000 terminus, so that it supports the model from within and does not prove it from without. But the +205-year shift was derived from the genealogical registers and the land-sabbath count, with no calendar input, and it nevertheless landed in the successful set — to the day. Its status, then: interpreted, without weight in the weighing (God's Algorithm, appendix D). Counted over the years, moreover, the mixed construction hits often: begin on the rabbinic calendar and end on the clock calendar, and the 1,335 lands on Hoshana Rabbah in roughly two years out of five. Testable consequence, stated in decision form rather than field form: the observational communities will declare a thirteenth month in the spring of 2034, so that their Passover falls around early May and their autumn feasts in early November — as the clock equally makes the spring of 2031 a leap position, with a Passover around May 6, 2031, a full month after the rabbinic date.