A date seems the least spiritual thing there is. A number on a calendar, something for archivists and almanacs. What difference does it make whether the cross stood in the year 30, or 31, or 33? The blood is the same blood; the resurrection the same victory. And yet this whole book turns on precisely that one number — not out of a love of arithmetic, but because of something that lies deeper than a date: the question whether God arrives on time.
The assumption beneath everything
There is one conviction that carries this book, and the whole body of work of which it is the cornerstone. It can be said in a single sentence, and its consequences are far-reaching: God keeps his appointments exactly on time. Not roughly. Not approximately. To the day. Whoever believes that cannot wave a date away as a side issue — for then a date is precisely the place where God's faithfulness becomes visible, or does not.
This assumption is the reason this investigation exists. It was not curiosity about chronology that drove it, but the expectation that the God who calls the stars by name also keeps his own clock — and that whoever looks carefully will find that precision again. The question was never merely "can we make a case for a year?", but, deeper: "is God as exact as I suspect?"
Why that is not a pious hunch
Such a conviction could be a wish — a devout longing for reality to work out neatly. But it is more than that, because God has made it testable himself. In his law he did not institute a vague "springtime", but exact dates: the Passover on the fourteenth day of the first month, the unleavened bread on the fifteenth, the wave sheaf in the days that followed, and precisely fifty days later the Feast of Weeks. Dates, not atmospheres.
And the New Testament tells redemption as the fulfilment of those dates — on the day. Christ died as the Passover; He rose as the Firstfruits, on the day of the wave sheaf if one counts it with the Sadducees; the Spirit was poured out when the day of Pentecost was "fully come". Three great acts of God, on three feasts He himself had dated centuries in advance, in the right order. Whoever sees this knows: nothing here is done approximately.
Groundworkthe feasts fulfilled on their day (verifiable)
The appointed times. Leviticus 23 dates the feasts to the day: Passover on 14 Nisan (v. 5), the unleavened bread from the 15th (v. 6), the wave sheaf "on the day after the sabbath" (v. 11), and the Feast of Weeks precisely fifty days later (vv. 15-16). Not a season, but a calendar.
The fulfilment, on those very days. "For our Passover also has been sacrificed: Christ" (1 Cor. 5:7). He was raised as "the Firstfruits of those who have fallen asleep" (1 Cor. 15:20), on the day of the wave sheaf only if one counts it with the Sadducees on the Sunday after the weekly sabbath, and not on 16 Nisan, as Three Days and Three Nights (Casus 31) works out in chapter 4. And the Spirit was given "when the day of Pentecost was fully come" (Acts 2:1) — fifty days counted, to the day.
To expect exactness is therefore not devotion but inference: God has demonstrably delivered on the day where He had set a date. This is the pivot of the whole work — not that typology is beautiful, but that God is precise with what He promises. [DOCUMENTED]
And that is why this work counts the nights instead of rounding them off. It is not hair-splitting; it is following a God who counts himself. If He set the Passover on the fourteenth and kept it, then one may expect that the cross too — and the clock that hangs from it — is right to the day, and not "approximately".
Two hands
But expectation is not proof, and conviction must not become a blinker. That is why this book keeps two hands at once: a firm hand on the structure, and a loose hand on the year. Firm, where the text compels — the sign, the weekday, the count that carries itself. Loose, where the data leave room — for a year that rests partly on assumptions is offered with an open hand, not imposed with a fist.
So the load-bearing word everywhere in this book is convergence, and nowhere the claim of a proof. Every calculation can be checked by the reader, and every source is given its location and its uncertainty. The year 31 itself comes from Casus 31, where the familiar year 33 too is given the floor at its strongest; this book weighs what rests on it, link by link. A cornerstone that defeats only straw men carries nothing. Whoever weighs his own case honestly need not overstate it.
The stone and the clock
Why then this stone in particular, and with such care? Because a clock hangs from it. The wider work reads salvation history as a precisely executed plan — a Master Clock, with its appointed times and its six thousand years — and the cross is the pivot on which that clock is hung. Daniel already saw it: after the sixty-nine weeks the Anointed One would be "cut off" (Daniel 9:26). That cross is the original image of which a later, dark mirror — the abomination that the wider work reads at Purim 2031, a month before Passover — is the counterpart. If the pivot sits on the wrong day, the whole clock hangs crooked.
Hence this book, and its structure. First the anchor: the year 31 as Casus 31 establishes it, with the window from Dating the Birth of Jesus (Chapter 1). Then the convergence, honestly counted: which lines stand free of that anchor, and how many there are (Chapter 2). Then the decree, where the seventy weeks begin (Chapter 3). Then the missing years, the gap between the rabbinic count and this clock (Chapter 4). Then the hundred and twentieth Jubilee: what the year 2034 really rests on (Chapter 5). An epilogue and an appendix with the chain in one image close the book. From the anchor along the chain to the terminus — and always back to that one question: does God arrive on time?
HeartHEART
Beneath all the arithmetic lies a simple comfort. A God who binds himself to a day is a God you can trust — for He puts something in your hands that you can check. He does not say: believe my good intentions. He says: see whether I keep my word, to the day. And whoever notices that He did so at the Passover and at Pentecost dares also to entrust to Him the times still to come.
The answer this book will give is not a proof. The Wednesday in the spring of 31, three nights in the dark and a resurrection to the measure He himself had named stand in Casus 31. This book weighs the chain that hangs from them: the decree of 458, counted from Tishri 457; the anointing in 27; the anchor in 31; the epoch in 3967 BC; the terminus in 2034. Every link receives its label, and the foundation does not hang on the prediction. Whoever believes that God arrives on time will find reason here to go on believing it; and whoever does not believe it may look on as the data fall, and weigh for himself. A cornerstone asks no more — and may offer no less.
A date seems the least spiritual thing there is. A number on a calendar, something for archivists and almanacs. What difference does it make whether the cross stood in the year 30, or 31, or 33? The blood is the same blood; the resurrection the same victory. And yet this whole book turns on precisely that one number — not out of a love of arithmetic, but because of something that lies deeper than a date: the question whether God arrives on time.
The assumption beneath everything
There is one conviction that carries this book, and the whole body of work of which it is the cornerstone. It can be said in a single sentence, and its consequences are far-reaching: God keeps his appointments exactly on time. Not roughly. Not approximately. To the day. Whoever believes that cannot wave a date away as a side issue — for then a date is precisely the place where God's faithfulness becomes visible, or does not.
This assumption is the reason this investigation exists. It was not curiosity about chronology that drove it, but the expectation that the God who calls the stars by name also keeps his own clock — and that whoever looks carefully will find that precision again. The question was never merely "can we make a case for a year?", but, deeper: "is God as exact as I suspect?"
Why that is not a pious hunch
Such a conviction could be a wish — a devout longing for reality to work out neatly. But it is more than that, because God has made it testable himself. In his law he did not institute a vague "springtime", but exact dates: the Passover on the fourteenth day of the first month, the unleavened bread on the fifteenth, the wave sheaf in the days that followed, and precisely fifty days later the Feast of Weeks. Dates, not atmospheres.
And the New Testament tells redemption as the fulfilment of those dates — on the day. Christ died as the Passover; He rose as the Firstfruits, on the day of the wave sheaf if one counts it with the Sadducees; the Spirit was poured out when the day of Pentecost was "fully come". Three great acts of God, on three feasts He himself had dated centuries in advance, in the right order. Whoever sees this knows: nothing here is done approximately.
Groundworkthe feasts fulfilled on their day (verifiable)
The appointed times. Leviticus 23 dates the feasts to the day: Passover on 14 Nisan (v. 5), the unleavened bread from the 15th (v. 6), the wave sheaf "on the day after the sabbath" (v. 11), and the Feast of Weeks precisely fifty days later (vv. 15-16). Not a season, but a calendar.
The fulfilment, on those very days. "For our Passover also has been sacrificed: Christ" (1 Cor. 5:7). He was raised as "the Firstfruits of those who have fallen asleep" (1 Cor. 15:20), on the day of the wave sheaf only if one counts it with the Sadducees on the Sunday after the weekly sabbath, and not on 16 Nisan, as Three Days and Three Nights (Casus 31) works out in chapter 4. And the Spirit was given "when the day of Pentecost was fully come" (Acts 2:1) — fifty days counted, to the day.
To expect exactness is therefore not devotion but inference: God has demonstrably delivered on the day where He had set a date. This is the pivot of the whole work — not that typology is beautiful, but that God is precise with what He promises. [DOCUMENTED]
And that is why this work counts the nights instead of rounding them off. It is not hair-splitting; it is following a God who counts himself. If He set the Passover on the fourteenth and kept it, then one may expect that the cross too — and the clock that hangs from it — is right to the day, and not "approximately".
Two hands
But expectation is not proof, and conviction must not become a blinker. That is why this book keeps two hands at once: a firm hand on the structure, and a loose hand on the year. Firm, where the text compels — the sign, the weekday, the count that carries itself. Loose, where the data leave room — for a year that rests partly on assumptions is offered with an open hand, not imposed with a fist.
So the load-bearing word everywhere in this book is convergence, and nowhere the claim of a proof. Every calculation can be checked by the reader, and every source is given its location and its uncertainty. The year 31 itself comes from Casus 31, where the familiar year 33 too is given the floor at its strongest; this book weighs what rests on it, link by link. A cornerstone that defeats only straw men carries nothing. Whoever weighs his own case honestly need not overstate it.
The stone and the clock
Why then this stone in particular, and with such care? Because a clock hangs from it. The wider work reads salvation history as a precisely executed plan — a Master Clock, with its appointed times and its six thousand years — and the cross is the pivot on which that clock is hung. Daniel already saw it: after the sixty-nine weeks the Anointed One would be "cut off" (Daniel 9:26). That cross is the original image of which a later, dark mirror — the abomination that the wider work reads at Purim 2031, a month before Passover — is the counterpart. If the pivot sits on the wrong day, the whole clock hangs crooked.
Hence this book, and its structure. First the anchor: the year 31 as Casus 31 establishes it, with the window from Dating the Birth of Jesus (Chapter 1). Then the convergence, honestly counted: which lines stand free of that anchor, and how many there are (Chapter 2). Then the decree, where the seventy weeks begin (Chapter 3). Then the missing years, the gap between the rabbinic count and this clock (Chapter 4). Then the hundred and twentieth Jubilee: what the year 2034 really rests on (Chapter 5). An epilogue and an appendix with the chain in one image close the book. From the anchor along the chain to the terminus — and always back to that one question: does God arrive on time?
HeartHEART
Beneath all the arithmetic lies a simple comfort. A God who binds himself to a day is a God you can trust — for He puts something in your hands that you can check. He does not say: believe my good intentions. He says: see whether I keep my word, to the day. And whoever notices that He did so at the Passover and at Pentecost dares also to entrust to Him the times still to come.
The answer this book will give is not a proof. The Wednesday in the spring of 31, three nights in the dark and a resurrection to the measure He himself had named stand in Casus 31. This book weighs the chain that hangs from them: the decree of 458, counted from Tishri 457; the anointing in 27; the anchor in 31; the epoch in 3967 BC; the terminus in 2034. Every link receives its label, and the foundation does not hang on the prediction. Whoever believes that God arrives on time will find reason here to go on believing it; and whoever does not believe it may look on as the data fall, and weigh for himself. A cornerstone asks no more — and may offer no less.