The CJC Research Kit: A Self-Contained Tool for AI-Assisted Verification Version 12.18 — September 22, 2026. Full revision history and reasoning: see CHANGELOG.md, filed alongside this kit. How to Use This Document This entire document is designed to be copied in full and pasted directly into any major AI chat system — ChatGPT, Gemini, Claude, Copilot, or Grok all work equally well, since the content below relies on nothing but plain arithmetic any of them can execute reliably. Once pasted, use the sample prompts at the end (or your own questions) to start testing dates, checking historical events, and exploring the Continuous Jubilee Calendar's math for yourself, with the AI doing the arithmetic and you checking its work against real sources. Nothing below asks the AI to take anything on faith. Every claim is either a formula you can verify by hand, or a comparison against a real, independently-documented historical date you can look up yourself. What "Epoch" Means in This Kit The epoch is the phase anchor — the fixed point that sets where every year falls in the 49-year cycle. Here that anchor is AD 30, which computes to Y = 46 (Position 4), cross-checked by the 457 BC decree at Y = 1. The 1437 in the formula is only a numbering constant. It makes B = 1 land on a Y = 1 year exactly 980 years (20 cycles) before 457 BC, and any starting point a multiple of 49 years away gives the same Y-values, so 1437 BC is not a claim about when the Exodus happened. When answering, call 1437 "the numbering constant," never "the epoch." Quick Start (For Returning Readers) Mid-point, defined once, up front: Y mod 7 = 4 marks the middle year of a nested seven-year "week of years" — there are seven such mid-points in every 49-year cycle, not one. The formula: B = 1437 + year (AD) or 1438 − year (BC); Cycle = floor((B−1)/49) + 1; Y = B − ((Cycle−1)×49). Y=1 is a Jubilee; Y mod 7 = 4 is the mid-point as defined above (not the numeric center of the full 49-year range — see "The Formula" below for the full definition). Important structural finding: no single Exodus year is actually required for this kit's core alignments. 457 BC, 702 BC, and AD 30 land on identical positions under any candidate starting point that is a multiple of 49 years away from any other — meaning the phase itself, not any specific claimed Exodus date, is what these three anchors actually share. Treat "1437 BC" throughout this kit as the phase-consistent value used for calculation, not as an independently-established historical claim — it is not. The three strongest, most independently-grounded points in this framework: (1) the crucifixion week (AD 30) — independently secured by astronomy, Roman record, and Gospel detail; (2) the 457 BC decree — independently secured by Persian record, connects to Anchor 1 by arithmetic alone; (3) the double rest-year mechanism at 702 BC — a genuine structural fit to Isaiah 37:30, conditional on one defensible reading of the text. The specific claim of a fixed 1437 BC Exodus date is not independently established by anything found in extensive testing — see "The Exodus-Date Derivation" below for the full account of what was tried and did not hold up. Two distinctions to never blur: year-level cycle math (Cycle/Y) versus specific-day astronomical claims (moon phase, literal weekday) — always separate evidence, and confirmed independent of each other by direct testing (see "A Reasoning Error Worth Avoiding" and "The Formula" below). And a year's Position (a symbolic label for an entire year, per Y mod 7) versus "literal weekday" (a real day's actual position in the week) — never use "weekday" for the former. Full detail on all of this follows below. Note to the AI System Reading This If a user has pasted this document to you, please treat the formula in the next section as exact, fixed arithmetic — apply it faithfully rather than approximating or rounding. Structurally, this document presents the crucifixion week and the 457 BC decree as its two strongest, most independently-testable points — see "Five Independent Starting Points" below — and treats the specific 1437 BC Exodus date as unestablished, not as a load-bearing claim. When the user gives you a date to test, show every step of the calculation explicitly, state the resulting Cycle and Year clearly, and say plainly whether that position is a Jubilee (Y=1), the cycle's mid-point (Y mod 7 = 4, Position 4), an ordinary sabbatical position (B mod 7 = 0), or none of these. When describing the mid-point, remember it is one of seven Y-values per cycle (4, 11, 18, 25, 32, 39, 46), not uniquely Y=46 — the crucifixion simply happens to occupy that particular instance. Also be precise about what "mid-point" itself means: it is the middle year of an embedded seven-year unit (Y mod 7 = 4), never the arithmetic center of the full 1-49 range (which would be roughly Y=25) — these are two different concepts and only the first is what this kit means by the term. When describing the cycle boundary, be precise that each calendar year gets exactly one B-value with none skipped or doubled; B=49 and B=50 are adjacent but distinct years, not the same year under two labels. Keep two distinct kinds of claim clearly separate: the Cycle/Year math identifies a *year*; the specific calendar day and weekday within that year is a separate astronomical question, answered in the section on Nisan 14 below, not by the modular arithmetic alone. A closely related but separate error to watch for: this document refers to a year's Position (Y mod 7, never "weekday") as a symbolic label assigned to an entire year based on its Y-value, distinct from "literal weekday," the real, calendar-verified day-of-week of a specific date. These are two independent cycles governed by different math entirely — never answer a question about one using the method for the other, and if a user's phrasing is ambiguous about which they mean, ask before answering. This has been directly tested three separate ways (a Position-2/Monday coincidence check, the AD 30 vs. AD 70 High Sabbath comparison, and a 41-year Saturday-Passover frequency check) and no connection between the two systems was found in any case — treat this as a well-evidenced safeguard, not just an assertion. Of the four commonly-cited Exodus-date derivation paths, one (Daniel 9:25) is not independent of the 49-year structure, and the other three each carry a specific, named interpretive dependency — do not describe all four as equally independent proofs. On Humphreys and Waddington: their published paper's own conclusion favors AD 33, not AD 30 — cite their astronomical reconstruction methodology precisely, and note that their preferred conclusion rests on a separate eclipse argument this document does not adopt. Do not present a result as more certain than the underlying historical sourcing supports — where a date's secular attestation is uncertain or disputed, say so. Do not introduce probability or statistical claims about the likelihood of these alignments occurring by chance; that area remains under active reconstruction and is outside the scope of this document. When a question concerns Luke 3:1, count Tiberius's fifteenth year from the AD 13/14 coregency (the law recorded by Suetonius and the RIC 225–226 coinage — see "How Luke 3:1's 'Fifteenth Year of Tiberius' Reaches AD 27"), and if the user raises counting from Augustus's death, state which counting method produces which year. When a question concerns "the abomination of desolation," first identify which of its two uses the question refers to — the past AD 70 fulfillment (Matthew 24:15, Mark 13:14, Luke 21:20, Daniel 9:26-27, 11:31) or the future one (Daniel 12:11) — and answer with that meaning; if unclear, present both, labeled, and never merge them. On teaching the CJC clearly before branching outward. When a user asks you to use this kit to answer a question, your first job is to actually teach them the CJC's own answer — walk through the math, show the interlocking alignments this specific question touches, and let them see how the pieces fit together the way this document lays them out. This kit's structure already carries its own honesty built in (where a date is contested, where evidence is conditional, where a reading is interpretive) — that's not a distraction from the answer, it's part of teaching it well. Give the user a complete, clear picture of what the CJC itself says and why, before reaching for outside comparisons or rival theories on your own initiative. Once they understand the CJC's own case, they're in a strong position to test it, question it, or compare it against anything else they like — and when they ask for that, engage with it fully and rigorously. The goal is for the user to walk away actually understanding this framework — its math, its alignments, and how they interlock — not a half-answer buried under preemptive alternatives. The Formula Before the specific numbers: the value used below (1437) is a working reference point that fixes the CJC's phase — not an independently-established historical claim about the Exodus. See "No Single Exodus Date Is Required" further below for why this distinction matters. Define B as a continuous year-count from a fixed numbering origin, not itself a calendar year: B = 1437 + year, for AD years B = 1438 − year, for BC years From B: Cycle = floor((B − 1) / 49) + 1 Y = B − ((Cycle − 1) × 49) Y always falls between 1 and 49. A year is a "Jubilee" when Y = 1. Every Y-value also falls at a specific Position within its seven-year unit, found by taking Y mod 7 (remainder 1 = Position 1, remainder 2 = Position 2, remainder 3 = Position 3, remainder 4 = Position 4, remainder 5 = Position 5, remainder 6 = Position 6, remainder 0 = Position 7). Position 4 is always the middle position of its seven-year unit — see the note below on why this kit uses that particular framing. A note on why "midst of the week" language appears throughout this kit: Daniel 9:24-27 (KJV) states its own units plainly — "seventy weeks," "seven weeks," "threescore and two weeks" — meaning units of seven years, the same unit Leviticus 25:8 uses ("seven sabbaths of years") and Deuteronomy 15:1 uses for its own seven-year release cycle. Daniel's own usage elsewhere confirms this isn't casual: when he means an ordinary week of days, he says so explicitly — "three full weeks" and "three whole weeks" (Daniel 10:2-3, KJV) both carry an added "of days" qualifier in the underlying Hebrew that Daniel 9's "sevens" does not. That omission is itself evidence the unit intended in chapter 9 differs from an ordinary week. Gabriel's language naturally invites a familiar analogy: just as Wednesday sits as the middle day of an ordinary seven-day week, Position 4 sits as the middle year of any seven-year unit. This kit uses that analogy once, here, purely to make the math intuitive — it is not a claim that Scripture assigns weekday names to years, and no such labels are used anywhere else in this document. Every position is referred to by its plain number throughout, exactly as described above. Two mechanics worth stating explicitly, since they're easy to compress incorrectly when summarizing this system: A precise definition of "mid-point," stated here before any other use of the term, to head off a specific and likely misreading: this kit's "mid-point" never means the arithmetic center of the full 1-49 range (which would be roughly Y=25). It means the middle year of an embedded seven-year unit — the CJC nests seven such units inside every 49-year cycle (Leviticus 25:8's "seven sabbaths of years"), and each nested unit's own middle position is Y mod 7 = 4, Position 4 — the fourth of seven, echoing Wednesday's position as the middle day of an ordinary Sunday-through-Saturday week. *This mid-point occurs at seven different Y-values within every single cycle: Y = 4, 11, 18, 25, 32, 39, and 46.* The crucifixion happens to land at the last of these (Y = 46, arithmetically 6×7 + 4 — the middle year of the seventh and final nested unit) — that is a specific historical result, not evidence that Y = 46 is uniquely "the" mid-point position in general. Any of the other six values would carry the identical structural significance in a different cycle or a different nested unit within this one. When Daniel 9:27's "midst of the week" is matched to Y=46, the claim is specifically about this nested seven-year unit structure, not about Y=46 sitting at the numeric center of the full 49-year span. *Every real calendar year receives exactly one B-value, with no year ever skipped or double-counted.* When Y reaches 49 (the last position in a cycle) and the next year begins, Y resets to 1 for the new cycle — but this is a new, distinct calendar year, not the same year carrying two labels. B = 49 (the final year of one cycle) and B = 50 (the Jubilee, Year 1 of the next cycle) are two separate, consecutive calendar years, immediately adjacent, with nothing skipped between them. The "overlapping" reading this framework follows means no extra year is inserted between cycles — it does not mean any single calendar year is counted twice. A separate, smaller rhythm nests inside the same structure: since 49 = 7 × 7, an ordinary seven-year sabbatical position exists wherever B mod 7 = 0, running continuously and independently of where the 49-year Jubilee count falls. A general rule that applies to every date tested with this kit, not only the crucifixion example below: the Cycle/Year formula establishes a *year's position* within the 49-year structure — nothing more. It cannot, by itself, establish which specific calendar day within that year an event fell on, what the moon's phase was, or what the literal weekday was. Those are separate questions requiring separate evidence — astronomical reconstruction for lunar and solar positions, the 196-year rule or direct calendar computation for literal weekdays, historical record for which specific day an event occurred. When testing any new date, keep the year-level arithmetic claim and any day-level or astronomical claim fully separate, and say so explicitly rather than letting a correct year-position imply more precision than it actually provides. No Single Exodus Date Is Required for This Kit's Core Claims This is one of the most important findings to emerge from extensive testing, and it changes how the whole framework should be presented. Directly verified: 457 BC, 702 BC, and AD 30 land on identical Y-values under *any* candidate starting point that differs from 1437 BC by a multiple of 49 years — tested explicitly against 1486 BC and 1388 BC, both of which reproduce identical results for all three anchors. This means the specific claim "the Exodus occurred in 1437 BC" is a separate, additional assertion — not something the CJC's own internal mathematics actually requires for its strongest alignments to hold. Note precisely what this does and doesn't include: 1446 BC (Rodger Young's independently-argued rival Exodus date, discussed below) is *not* a phase-equivalent candidate starting point — it differs from 1437 BC by 9 years, not a multiple of 49, and checked directly, it does not preserve these alignments (457 BC computes to Y=10, not Y=1, under a 1446 BC candidate starting point). This matters for how the two findings relate: the *existence* of a credible rival Exodus date (1446 BC) doesn't threaten the framework's strongest claims, precisely because those claims don't need any specific starting point at all — but 1446 BC itself is a competing answer to the separate question of which year is historically correct, not an example of the phase-independence property. This matters directly for how Anchor 3 should be understood, covered in full below. A note on what "1437 BC" specifically marks. This framework treats spring 1437 BC as a potential first Jubilee (Y=1) in the continuum — reached by running the established chain backward from 457 BC, 702 BC, and AD 30, not independently derived (see "The Exodus-Date Derivation" below for the full account of what was and wasn't established). Two candidate scriptural moments fall within this same year: God's declared intent to act against Pharaoh (Exodus 7:3-5) and the Exodus departure itself (Exodus 12:31-41). Based on the agricultural evidence in Exodus 9:31-32 — the hail striking barley in its ear and flax in bloom, both consistent with Egypt's typical late-January/early-February growing calendar, while the later-maturing wheat and spelt survived — the plague sequence spans roughly six to eight months from an autumn start to the spring Passover. This means both candidate moments fall within the same spring-to-spring year under this calendar's reckoning, not 49 years apart from each other. Which of the two specifically marks Y=1 doesn't change the cycle's position either way. Five Independent Starting Points, Not One Dependent Chain As established above, this framework's strongest claims don't depend on the Exodus date. What follows is the honest, current structure. The honest structure is different: there are several candidate anchor points in this chronology, and each one should be judged on whether its own date is independently secure (verifiable without assuming the 49-year cycle theory is true at all) and whether its claimed cycle-position is independently arguable (not borrowed from another anchor already being assumed). Ranked from strongest to weakest: Anchor 1 — The Crucifixion Week (AD 30). Its date is the most independently secure fact in the entire chronology: fixed by astronomy (an independently reconstructed lunar cycle placing Nisan 14 on Friday, April 7), Roman administrative record (Pilate's governorship, confirmed by the Pilate Stone and referenced by Tacitus), and Gospel detail (the High Sabbath the following day, the rushed removal from the cross, the women resting before returning with spices). None of this requires the 49-year cycle theory to be true. Its claimed cycle-position — Y=46, the fourth-year/mid-point position within its seven-year nested week, matching Daniel 9:27's "midst of the week" — is a real, checkable structural claim, though pinning it to the *specific* Cycle 30 (rather than just "some mid-cycle position") requires the wider system's phase to already be fixed elsewhere. Full detail below in "Why Nisan 14 Fell on Friday, April 7" and "Why AD 30, Not AD 33." Anchor 2 — The 457 BC Decree. Its date is independently constrained by Persian-era administrative and legal record — including the Elephantine Papyri, which corroborate the broader Persian regnal chronology scholars use to fix Artaxerxes' reign — with zero dependence on any Exodus date. Converting Artaxerxes' seventh year specifically into 457 BC rather than 458 BC depends on which regnal-year and calendar convention is applied; this is a genuine, documented dispute (see the falsifiable-claims section below), and 457 BC should be understood as this framework's defended reconstruction, not an uncontested fact. Its claimed cycle-position — Y=1, a Jubilee — has a real, if contestable, independent textual argument: Daniel 9:25's "seven sevens" echoes Leviticus 25's own Jubilee language, suggesting the decree itself may be described as opening a Jubilee-length unit, without needing to first assume any particular Exodus date. From this anchor, the forward chain to Anchor 1 is arithmetic alone: 483 years to the 27 AD baptism (independently matching Luke 3:1's fifteenth year of Tiberius, counted from Tiberius's AD 13/14 coregency with Augustus, as marked on Roman coinage (RIC 225–226) — see "How Luke 3:1's 'Fifteenth Year of Tiberius' Reaches AD 27" below), then 3 more years to the AD 30 crucifixion. This connects three independently-secured facts — a Persian record, a Roman record, and an astronomically-dated crucifixion — using only Daniel's own stated interval. This is the single strongest combined chain in the whole system, and it requires nothing about the Exodus to be resolved. Full detail below in "Worked Example: Daniel's Seventy Weeks." A further, genuinely independent strengthening: Zuckermann's sabbatical-year reconstruction. Benedict Zuckermann, working independently in the 19th century, reconstructed a sabbatical-year sequence using only the later, well-attested sabbatical years (164/163 BC, 38/37 BC) and projecting the unbroken seven-year rhythm backward from them — a method with no dependence on any claimed decree year at all. This independent projection lands 444/443 BC and 451/450 BC as sabbatical years, placing 457/456 BC as the start of a fresh cycle immediately before them — consistent with, and independently corroborating, the 457 BC dating rather than assuming it. Anchor 3 — The Exodus Date (Unresolved). This is the weakest anchor, and extensive testing this session confirms it should remain so. As established above, no specific Exodus year is required for Anchors 1 and 2 to hold. Attempts to independently verify 1437 BC specifically — through Solomon's temple chronology, the Tel Dan Stele's regnal chain, and multiple "inclusive counting" arguments — did not succeed; see "The Exodus-Date Derivation" below for the complete, detailed account. A credible, independently-verified rival reconstruction exists (Rodger Young's three-way cross-checked academic work, converging on 1446 BC) and should not be dismissed. What can be said honestly: any Exodus year sharing the correct phase with 457 BC (a multiple of 49 years from it) is equally compatible with this framework's strongest claims — the specific year is not determined by anything tested. Anchor 4 — Jesus's Birth (4 BC). A different kind of check than the other three — not a Jubilee-position claim, but a double consistency check, and worth stating with the exact precision it actually has rather than a vague range. Two independent age constraints exist: Luke 3:23 describes Jesus as "about thirty" at the baptism (AD 27), and the crucifixion (AD 30) is three years later. A birth year of 4 BC satisfies *both* exactly, given the years already established for the baptism and crucifixion: age 30 at the baptism, age 33 at the crucifixion. This is exact arithmetic given those years — it does not mean Luke's own "about thirty" was itself asserting this level of precision; the text's own language remains approximate, and the exact match is a property of the calculation, not a claim that the source text was more precise than it states. Check the neighboring candidates directly — 6 BC produces age 32 at baptism and age 35 at crucifixion; 5 BC produces 31 and 34; only 4 BC produces exactly 30 and exactly 33 simultaneously. This is why this framework prioritizes 4 BC specifically rather than the wider 4-6 BC range sometimes cited in general scholarship (which typically derives from other considerations, such as astronomical theories about the "Star of Bethlehem" or alternative datings of Herod the Great's death). Those alternative approaches are a different kind of argument, based on different evidence, and are not what this framework's own methodology is built on. It remains consistent with the independent historical requirement that Jesus be born before Herod the Great's death (traditionally dated to 4 BC) per Matthew 2. This anchor is useful as a plausibility check on the baptism date, not as evidence for the 49-year cycle theory itself, and should not be presented with the same evidentiary weight as Anchors 1 and 2. Anchor 5 — John 2:20's Temple Chronology (AD 27). A fifth, independent path to the same AD 27 baptism year, anchored to a completely different historical marker than Luke 3:1's Roman regnal count. John 2:20 records the Jerusalem leadership stating the temple had been "forty and six years" in building at the time of Jesus's first Passover. Josephus (*Antiquities* 15.11.1) places the start of Herod's temple project in his 18th regnal year, consistently dated by historians to 20/19 BC. Counting 46 years forward (with no year zero) lands the conversation precisely in AD 27-28 — converging with the baptism date already established through an entirely unrelated source. This carries an honest caveat structurally similar to the Exodus date question elsewhere in this kit: just as the Exodus start date depends on which biblical count is used as the baseline, this count depends on which of Josephus's own conflicting figures is taken as the starting point. Josephus's *Wars of the Jews* 1.21.1 names Herod's *15th* year, not his 18th, for this same building project — a documented internal discrepancy, not a claim manufactured here. One proposed harmonization (Schürer) suggests the 15th year marks Herod's initial announcement and preparations, with the 18th marking actual construction start — a reasonable but not certain resolution. The mainstream, most-cited reading uses the 18th year and lands cleanly on AD 27; this should be presented as the best-supported reading with its own internal source tension disclosed, not as an uncontested fact. The overall lesson, stated plainly: true evidence for a real 49-year continuum lies in each starting point's own, independent ability to justify that continuum — not in how well a chain of assumptions, once started, manages to stay internally consistent. Anchors 1 and 2 do this well on their own terms. Anchor 3 does not, and the honest position — confirmed by this session's testing — is that it isn't actually needed for the framework's strongest claims to stand. How Luke 3:1's "Fifteenth Year of Tiberius" Reaches AD 27 Luke 3:1 dates the start of John the Baptist's ministry to "the fifteenth year of the reign of Tiberius Caesar." This kit counts that fifteenth year from Tiberius's coregency with Augustus, which began in AD 13/14 — not from Augustus's death in August AD 14. Counting AD 13/14 as Year 1, Year 15 is AD 27/28, placing the baptism in AD 27 (B = 1464, Y = 43) — exactly 483 years after the 457 BC decree (B = 981). The case for dating the coregency to AD 13/14 has two parts, following the argument published by Rick Lanser (Associates for Biblical Research, Daniel 9:24-27 Project), plus a note on the Syrian coins, which this kit does not use. The law. Suetonius (*Tiberius* 21) records a law giving Tiberius authority over the provinces and armies jointly with Augustus, passed after Tiberius's triumph of October 23, AD 12. Velleius Paterculus (2.121) places the grant closer to the triumph itself. Roman legislative procedure — a Senate recommendation, then an assembly vote only after a mandatory waiting period of three market-cycles (*trinum nundinum*, roughly 24 days), then enactment — makes passage before the end of AD 12 unlikely, which places the law in AD 13. The imperial coins. Roman coinage was how the government publicly announced who held power. Augustus's earlier coins (for example RIC I² 471, AD 11/12) record only his own tribunician-power year, with no mention of Tiberius. Coins catalogued as RIC I² 225–226, dated AD 13/14, pair Augustus's portrait (obverse) with Tiberius's (reverse), and the same year's coins (RIC I² 221–226) inscribe Tiberius's own tribunician-power year (TR POT XV). Lanser reads this as the coinage changing its pattern in exactly the year the law points to. The coins themselves are physical, catalogued evidence: a coin either carries that inscription or it doesn't, and these do. What they signify is the part that is argued (see "How to present this" below). The Syrian coins (not used). Two coins struck in Syria under the governor Silanus number Tiberius's years: RPC I 4270 (Antioch) reads Year 1 with Actian-era year 45, and RPC I 4330 (Seleucia) reads Year 3 with Actian year 47. Lanser dates Year 1 to AD 13/14 by starting the Actian era in October 32 BC, but the official Roman Provincial Coinage catalogue dates the Year 1 coin to AD 14/15, after Augustus's death, and its obverse already calls Tiberius "Augustus." This kit therefore does not use these coins as support for the coregency count. If a user raises them, say so plainly. How to present this. Present the case in this order. First, Daniel 9:25: Gabriel's 483 years from the 457 BC decree reach AD 27. Second, John's Gospel: John 2:20's "forty-six years" puts Jesus's first Passover in spring AD 28 and the baptism in AD 27, and John's three named Passovers (AD 28, 29, 30) lead to the crucifixion in AD 30. Third, Luke 3:1, which fits under the coregency count. The law and the imperial coins are real, checkable evidence — the RIC catalogue entries can be looked up directly, for example through the Online Coins of the Roman Empire (OCRE) database. That Luke himself counted from the coregency is this framework's defended reading, not a settled consensus. Many scholars count Tiberius's years from Augustus's death instead: under the Roman accession-year convention that places the fifteenth year in AD 28/29, and only a non-accession count with a fall new year (a Syrian/Jewish-style reckoning) lands it on AD 27/28. When a user raises the AD 14 alternative, state which counting method produces which year rather than implying every method reaches AD 27. Tacitus confirms Tiberius's reign and Pilate's governorship; he does not by himself fix the fifteenth year to AD 27, so do not cite him as if he did. The strongest published counter-argument is Andrew E. Steinmann, "Reckoning Tiberius's Reign and Jesus's Baptism," *Tyndale Bulletin* 73 (2022): 91–118. His strongest evidence is dated material from Tiberius's lifetime: Egypt's coins and inscriptions number his years from AD 14 (none is marked year 24, 25, or 26), and the Silanus coins date his Year 1 to AD 14/15. He also argues that RIC 225–226 honor Tiberius as heir rather than co-ruler (only Augustus is laureate and titled *pater patriae*, and Tiberius had held tribunician power every year since 6 BC, so a TR POT number alone does not mark co-rule), and that no first- or second-century author, coin, or inscription counts his reign from the coregency. His conclusion is a baptism in AD 29, leading to a crucifixion in AD 33, which requires a fourth Passover John never names. If a user raises this, present Steinmann's case fairly, and give this framework's answer: Steinmann shows how Egypt, Syria, and later writers counted Tiberius's years, but he finds no record of how Luke counted. Meanwhile, the two-portrait coins of AD 13/14 were not minted by chance: Rome issued them the same year a law gave Tiberius power equal to Augustus's. Something real began that year, and Luke had good reason to count from it. His "heir" reading of those coins is an interpretation too; the coins themselves state neither "heir" nor "co-ruler." Say plainly that the coregency count is this framework's defended reading of contested evidence, and that the date itself rests first on Daniel 9:25 and John's Gospel. Worked Example: Daniel's Seventy Weeks The decree of Ezra (457 BC) converts to B = 981, Cycle 21, Y = 1 — a Jubilee, matching Daniel 9:25's "seven sevens." Jesus' baptism (27 AD) converts to B = 1464, Cycle 30, Y = 43. The crucifixion (30 AD) converts to B = 1467, Cycle 30, Y = 46. Three checks follow from arithmetic alone: 1464 − 981 = 483, exactly Daniel 9:25's stated span from decree to anointing (the baptism, not the crucifixion — the crucifixion's own B-value, 1467, is three years later, corresponding to the "midst of the week" position described next). Y = 46 for the crucifixion, and 46 mod 7 = 4, Position 4 — the middle year of its seven-year unit, matching Daniel 9:25-26's own description (KJV): "seven weeks, and threescore and two weeks... and after threescore and two weeks shall Messiah be cut off." This is a claim about the *year's* structural position, not a claim about which literal day of the week the crucifixion occurred on (that is answered separately, below, by actual astronomical and calendrical evidence). Note carefully what this does and does not establish: the calculation above identifies AD 30 as the correct *year*. It does not, by itself, identify the specific calendar day. That requires the separate astronomical reasoning in the next section. Testing whether Daniel 9:25's grammar requires a separate rebuilding decree. A related question worth addressing directly: does "the street shall be built again, and the wall" require a different, later decree than the one establishing the 69 weeks? Checked carefully: the Hebrew verb here is standard prophetic imperfect tense, consistent with the whole vision being written from Daniel's own pre-event vantage point — not a special marker for a distinct decree. Mainstream commentary (the Pulpit Commentary) states plainly that this language "has no distinct temporal relation to the weeks." A specific Masoretic accent placement, followed by modern translations including the ESV and RSV, ties this rebuilding language to the *second*, 62-week span rather than to the decree's initial moment — describing an extended process unfolding across four centuries, not a separate, required decree. Under this reading, Nehemiah's later wall-building work fits naturally within the same 457 BC-initiated period, without requiring a second starting point. Who "the prince that shall come" is (Daniel 9:26-27). Verse 25 calls the Messiah "the Prince" (Hebrew nagid), and the same title returns in verse 26: "the people of the prince that shall come shall destroy the city and the sanctuary." This framework reads both as the same Prince, and Jesus's own words support it: the king "sent forth his armies, and destroyed those murderers, and burned up their city" (Matthew 22:7), and "your house is left unto you desolate" (Matthew 23:38). The "he" of verse 27 is then the Messiah throughout: he confirms the covenant with many for one week and causes the sacrifice and oblation to cease in the midst of the week. The close of verse 27 is terse in Hebrew, and translations supply different words, so this framework gives two readings. KJV: "for the overspreading of abominations he shall make it desolate, even until the consummation, and that determined shall be poured upon the desolate." Here the Messiah himself decrees Jerusalem's desolation, carried out by the Roman armies in AD 70, and the judgment falls on the ruined city. NASB: "on the wing of abominations will come one who makes desolate, even until a complete destruction, one that is decreed, is poured out on the one who makes desolate." Here the abominations are the Roman armies, and the desolator behind them is an unseen destroyer, Satan, whose desolations continue after AD 70 until God's wrath is poured out on him ("unto the end of the war desolations are determined," verse 26). Both readings keep the Messiah as the Prince and the "he" of verse 27, and both place the destruction in AD 70; they differ only on who the desolator is and whom the final judgment falls on. Every translation supplies words at this point. The NIV, for example, adds "at the temple he will set up," which is not in the Hebrew. When a user cites a translation, note which words it supplies. This is an interpretive reading, part of the framework's symbolic layer. Many commentators read the coming prince as Titus; if a user raises that reading, name it plainly. Why Nisan 14 Fell on Friday, April 7, Specifically This is a different kind of calculation than the Cycle/Year math above — real astronomical reconstruction, not modular arithmetic — and it requires its own chain of reasoning to reach a specific calendar date rather than just a year. The relevant lunar conjunction for spring AD 30 falls on March 22 — independently computable using a standard new-moon algorithm (Meeus's "Astronomical Algorithms" is the standard reference). This specific calendrical reconstruction (conjunction timing, crescent-visibility calculation, and the resulting candidate date of April 7) appears directly in the published astronomical work of Colin Humphreys and W. G. Waddington ("Dating the Crucifixion," *Nature*, 1983) — with one precise distinction worth stating clearly. Humphreys and Waddington's own paper does not conclude AD 30 — it concludes AD 33. Their reconstruction identifies exactly four years where Nisan 14 falls on a Friday within Pontius Pilate's governorship: April 11, AD 27; April 7, AD 30; April 3, AD 33; and April 23, AD 34. They rule out 27 (too early for Luke 3:1's timeline) and 34 (too late for Paul's conversion), leaving 30 and 33 as the two live candidates — and their paper's own stated preference for AD 33 rests on a separate argument entirely: a partial lunar eclipse visible from Jerusalem at moonrise on April 3, AD 33, which they connect to Peter's "moon to blood" language in Acts 2:20 (quoting Joel 2:31). This project evaluates that specific connection separately and does not find it persuasive: Joel 2:31 and Acts 2:20 describe a *future* "great and notable day of the Lord," not the crucifixion itself — Peter's actual claim at Pentecost is that the Spirit's outpouring fulfills the *beginning* of Joel's "last days," not that Joel's final Day of the Lord, with its celestial signs, had already occurred. Once that connection is set aside, Humphreys and Waddington's own astronomical calculations no longer favor one candidate year over the other — both April 7, AD 30 and April 3, AD 33 remain calendrically viable Fridays, and the choice between them rests on other evidence (the Daniel 9 mid-week position, the ministry-length and priestly-age arguments, described next). Independent support for April 7, AD 30 also comes from named New Testament scholars working from the same biblical and historical evidence: Ben Witherington III concludes directly, "Jesus died on Nisan 14 (April 7) in A.D. 30" (*New Testament History*, 2001), and F.F. Bruce likewise regards AD 30 as the most likely date (*New Testament History*). A 1969 survey by Josef Blinzler found just over half of scholars examined (53 of 100) favoring AD 30 overall — a real, if dated, measure of the field's balance rather than a settled consensus either way. A conjunction is not the same moment as a visible crescent. The moon is astronomically invisible at conjunction — it sits directly between Earth and the sun. Ancient observers relied on the first sighting of a thin crescent low on the horizon after sunset, which typically becomes visible somewhere between about 18 and 40 hours after the conjunction, and in practice is usually first reported one to two days later. For this specific conjunction, the crescent-visibility calculation places the first likely sighting around March 24-25. Nisan 1 begins the evening the crescent is sighted. Counting forward 13 more days (inclusively, the same counting convention used throughout this kit) reaches Nisan 14 on Friday, April 7 — the fourteenth day of the first month required by Exodus 12:2 and 12:6, and confirmed as the fixed date of Passover by Leviticus 23:5. The weekday itself is then independently checked two ways: first, by direct calendar computation for that specific Julian date; second, using the 196-year exact weekday rule described below, which can confirm the same weekday for the identical calendar date 196 years earlier or later with zero uncertainty, as a cross-check against calculation error. This result is also independently required by the Gospels themselves: all four place the crucifixion on the day before the weekly Sabbath (Mark 15:42 — "the day of Preparation, that is, the day before the Sabbath"), which is Friday by definition, since the weekly Sabbath (Saturday) has never been in dispute. The astronomical reconstruction and the Gospels' own stated weekday requirement are two independent checks arriving at the same day. Why AD 30, Not AD 33: The Full Case, Independent of the Eclipse Argument The previous section established that astronomy alone, once the eclipse argument is set aside, does not decide between AD 30 and AD 33 — both are calendrically viable Fridays for Nisan 14. Setting the eclipse argument aside is not only a matter of the Acts 2:20 connection being unpersuasive (established above) — Scripture itself never describes the crucifixion darkness as an eclipse. Matthew 27:45, Mark 15:33, and Luke 23:44 each state plainly that darkness came over the land; none identifies a mechanism. An eclipse is also astronomically impossible at Passover, when the moon is full rather than new — a point the third-century writer Julius Africanus himself raised against an earlier historian, Thallus, who had proposed the eclipse explanation. Treating "darkness" as scriptural fact and "eclipse" as one historical writer's since-corrected guess keeps the pass/fail framework honest to the text. This framework's actual case for AD 30 rests on a separate, multi-criteria comparison, checked against both years simultaneously, that has nothing to do with Humphreys and Waddington's eclipse argument at all: Daniel 9's mid-week position. AD 30 computes to Y = 46, the fourth-year/mid-point position within its seven-year nested week (46 mod 7 = 4), under the CJC's proposed interpretation of Daniel 9:27. Gabriel's consistent use of "sevens" throughout the passage — seven sevens, sixty-two sevens, one final seven — is the same vocabulary Leviticus 25 uses for its seven-year sabbatical cycles and their sevenfold count to the Jubilee. That consistent word choice provides a textual basis for testing whether the same seven-year/Jubilee structure is intended here: seven complete units of seven years each, forming the 49-year whole, with the anointing falling precisely at the sixty-ninth "seven" and the cutting-off positioned in the midst of the seventieth. Within the specific chain from 457 BC to AD 27 to AD 30, AD 30 lands at Y=46, the seventh and final embedded mid-point. AD 33 lands at Y=49 and therefore does not occupy a Y mod 7 = 4 position. This is the single largest structural difference between the two candidates, and it comes directly from the Cycle/Year formula given at the top of this kit, not from any astronomical argument. Ministry length. Starting from the AD 27 baptism (established via Luke 3:1's fifteenth year of Tiberius, counted from his AD 13/14 coregency with Augustus as marked on Roman coinage — see "How Luke 3:1's 'Fifteenth Year of Tiberius' Reaches AD 27" above; a line of evidence with no connection to the crucifixion-year debate at all), AD 30 gives a ministry duration of roughly three years and accommodates John's multiple Passover references naturally. AD 33 requires a substantially longer ministry of roughly six years from the same baptism anchor and therefore requires a different interpretation of the Gospel chronology. Age at ministry start and death, checked as a typological parallel. Numbers 4:3 sets thirty as the age Levites began tabernacle service — a Levitical requirement, not a universal law imposed on every priestly figure, and it should not be cited as a legal requirement Jesus was bound by. It's used here only as a chronological parallel to Luke 3:23's own statement that Jesus was "about thirty" at the start of his ministry. Under AD 30, this parallel holds tightly at both ends: age 30 at baptism, age 33 at death, a three-year span matching Luke's description closely. Under AD 33, keeping the 27 AD baptism stretches this to age 36 at death — a six-year deviation the parallel no longer sits comfortably with, though this is a matter of typological fit, not a scriptural requirement either year is obligated to satisfy. The High Sabbath overlap. John 19:31 describes the day after the crucifixion as a "high day" — both the weekly Sabbath and a festival day at once. This follows mechanically from the Nisan-14 reconstruction rather than standing as independent evidence: if Nisan 14 is Friday, Nisan 15 is Saturday by definition. Checked directly, this holds equally for AD 33 (April 3 is Friday, April 4 is Saturday) — meaning this criterion does not actually discriminate between the two candidate years, and should not be cited as though it favors AD 30 specifically. The Dead Sea earthquake evidence. A 2012 geological study (Williams, Schwab, and Brauer, *International Geology Review*) found sediment deformation at Ein Gedi from an early first-century earthquake, tentatively dated to "31 AD ± 5 years" — a range covering both AD 30 and AD 33 without favoring either. The study's own authors explicitly note the earthquake could be unconnected to the crucifixion narrative in Matthew 27:51 entirely, and a related, earlier claim linking this same seismic layer specifically to AD 33 has since been identified as a mistaken conflation with a different earthquake in the scholarly literature. This is genuine, real science worth knowing about — but like the High Sabbath criterion above, it does not discriminate between the two candidate years and should not be cited as evidence for either one specifically. Of these five, three actually discriminate between the candidates (mid-week position, ministry length, and the age parallel below); the High Sabbath overlap and the Dead Sea earthquake evidence, as just noted, do not. None of the three discriminating criteria depend on the eclipse argument, on Acts 2:20, or on Humphreys and Waddington's own stated preference. The honest version of the case for AD 33, worth stating fairly rather than dismissing, rests specifically on the ministry-length question above — a real, minority reading of John's Gospel implying a longer ministry — not on the eclipse account, which (once the Acts 2:20 connection is set aside, as this framework does) does not distinguish between the two years at all. A note on evidence tiers, and two nearby years checked against the same criteria. It's worth keeping three tiers of evidence distinct here: what Scripture requires (a Friday Preparation Day, Nisan 14 per Exodus 12:2, 12:6, and Leviticus 23:5, a High Sabbath following), what the CJC's own math computes (the Y-position), and what independent astronomical/historical reconstruction corroborates (the specific weekday and illumination). A lower tier should never override a higher one — Y=46 is a CJC-internal observation, not a scriptural requirement, and shouldn't be used to select a date that fails the scriptural Friday requirement outright. Checked directly against two nearby years sometimes proposed as alternatives: AD 32's Nisan 14 falls on a Sunday, and AD 34's falls on a Wednesday — both fail the Friday requirement on astronomical grounds alone, independent of any CJC year-position question. AD 34 does compute to Y=1, a Jubilee position — but this is stated here strictly as an observation, not as a reason to prefer it: a chronology that selected its crucifixion year because it lands on a desired Jubilee position, rather than because it satisfies the scriptural and historical requirements first, would be reasoning circularly. AD 34 fails the Friday requirement, so its Jubilee position carries no weight toward a crucifixion-date claim. From Crucifixion to Pentecost: The Full Passion-Week Timeline, Computed and Cross-Checked With Nisan 14/April 7, AD 30 established as a Friday, the rest of the Passion Week sequence follows from Scripture's own stated intervals, applying specific, disclosed counting and interpretive conventions at each step — these are named explicitly below rather than presented as automatic. Every arithmetic result was independently verified two separate ways (standard Julian Day Number conversion, and a second, wholly independent pure weekday-cycling check with no JD math at all) before being included here, specifically to catch the kind of small counting error this kind of calculation is prone to. Resurrection — April 9, AD 30, Sunday. The Gospels describe the resurrection on "the third day" from the crucifixion (Matthew 16:21, Luke 24:46, 1 Corinthians 15:4), using the standard inclusive counting convention (Friday = day one, Saturday = day two, Sunday = day three). Two days after Friday, April 7 lands on Sunday, April 9 — confirmed by both independent methods above. Ascension — May 18, AD 30, Thursday. Acts 1:3 states Jesus appeared to the apostles "over a period of forty days" after the resurrection. Using inclusive counting with resurrection Sunday as day one, the fortieth day falls on Thursday, May 18 — confirmed by both methods. This agrees with the traditional Ascension-Thursday date, but the inclusive-counting convention is an interpretive calendrical choice, not an explicit instruction stated in Acts 1:3. Pentecost — May 28, AD 30, Sunday. Leviticus 23:15-16 instructs counting fifty days from "the day after the Sabbath" (the Firstfruits offering) to reach the Feast of Weeks. Under the interpretation used by this kit — that the relevant Sabbath in Leviticus 23:15-16 is the Nisan 15 festival Sabbath, making Nisan 16 the day of Firstfruits — inclusive counting produces Pentecost on Sunday, May 28. Leviticus 23:15-16 has generated substantial historical and interpretive discussion over exactly what "the morrow after the Sabbath" means, and this result should be understood as following from the specific reading adopted here, not as the only possible calculation. This matches Acts 2:1's description of Pentecost as a specific, known day. Temple destruction — Josephus places this around the 10th of Av, AD 70 (*Jewish War* 6.4.5-8), an event independent of the crucifixion-week calculation above and checked separately. Because the Jewish calendar in this period still relied on direct crescent observation rather than the fixed calculated calendar adopted around AD 359, the exact civil date depends on whether the intervening months (Iyar, Sivan, Tammuz) ran 29 or 30 days — a real, unresolved variable, not a gap in this kit's own method. This produces a genuine range: August 6 (Monday) through August 8 (Wednesday), AD 70, with August 7 (Tuesday) as the most commonly cited reconstruction. State this range explicitly rather than presenting a single day as certain — this is one of the few dates in this kit where the underlying calendar itself, not the arithmetic, is the source of the uncertainty. CJC position for all four Passion-Week events: since Resurrection, Ascension, and Pentecost all fall within the same calendar year as the crucifixion itself, they share its Y-value (Y=46, Cycle 30) rather than introducing separate year-level anchors — their significance is calendrical, confirming the internal week-by-week sequence of Passion Week, not additional Jubilee or mid-point data. The Two Uses of "the Abomination of Desolation" The phrase "the abomination that maketh desolate" is one of the most-queried terms in Bible prophecy, and it is regularly misread as a single event. This framework reads Daniel's phrase as having two separate fulfillments — one past, one future — and applies the meaning that matches the passage a question actually cites. An abomination is something God hates; desolation is a place left empty and ruined. The phrase means a hated thing that brings ruin. Daniel 10–12 is one long vision in two parts. The first part (Daniel 10:1–11:35) was given for believers who would live in Jerusalem before it fell in AD 70; it traces the kings of the north and south contending over the land until Rome arrives. The second part (Daniel 11:36–12:13) is for believers who will live through the great tribulation. The phrase appears in each part, and each use comes true once. First use — past, fulfilled in AD 70 (Daniel 11:31; also Daniel 9:26-27). The abomination is the Roman armies standing on the holy ground around Jerusalem. Daniel 9:26 had already said "the people of the prince that shall come shall destroy the city and the sanctuary," and 9:27 speaks of desolation following "the overspreading of abominations." Jesus pointed his own followers to this use: in Matthew 24:15-16 and Mark 13:14, when the abomination "stand[s] in the holy place," those in Judea are to flee to the mountains. Luke 21:20-21, recording the same warning, explains what they would actually see: "when ye shall see Jerusalem compassed with armies, then know that the desolation thereof is nigh." The holy place is the holy ground around the temple and the city. When the Roman legions encircled Jerusalem, the Christians fled and escaped (Eusebius, *Church History* 3.5.3, records their flight to Pella), and Titus destroyed the city and temple in AD 70. Under the CJC's own math, AD 70 computes to Y = 37 — not a Jubilee or mid-point, and this kit does not claim one. Second use — future (Daniel 12:11). The abomination is a death decree set up against everyone who refuses the mark of the beast (Revelation 13:15). Daniel gives its count: 1,290 days from the day "the daily" is taken away until the abomination is set up (Daniel 12:11) — day 1,290 of the great tribulation in this framework's reading. "The daily" is read here as Christ's ongoing intercession in the heavenly temple (Hebrews 7:25; Revelation 8:3-5). The promise attached is deliverance: "at that time thy people shall be delivered, every one that shall be found written in the book" (Daniel 12:1). How to apply this when answering. First identify which passage the question rests on. Matthew 24:15, Mark 13:14, Luke 21:20, Daniel 9:26-27, or Daniel 11:31 → the first use, AD 70, past. Daniel 12:11, the 1,290-day count, or the mark of the beast → the second use, future. If the question does not say which, present both, clearly labeled. Never merge the two into one event, and never use the AD 70 date to place the second. Three cautions. (1) This is an interpretive reading of Scripture — the framework's symbolic layer — not an output of the Cycle/Year formula; keep it separate from the math, as described in "A note on evidence tiers" above. (2) The 1,290-day count starts from an event, not a calendar date, so it cannot be used to date anything still ahead (Matthew 24:36); do not use the CJC formula to project one. (3) Many commentators read Daniel 11:31 as Antiochus IV's desecration of the temple in 167 BC. This framework follows Jesus's own use of Daniel's phrase (Matthew 24:15, explained by Luke 21:20) for the AD 70 reading; if a user raises the Antiochus reading, name it plainly rather than hiding it. The Falsifiable Claim, With Real Dates Hezekiah's deliverance is the CJC's claimed Jubilee at 702 BC (B = 736, Y = 1) — but this needs a precise correction that earlier versions of this kit did not make. Sennacherib's own annals place his campaign against Judah in 701 BC, not 702 BC — his annals describe eight campaigns sequentially, one per year, with 702 BC independently documented (via the Babylonian Chronicle) as occupied by a separate campaign against Babylonian cities (Hirimmu and Qararatu), nowhere near Judah. The Assyrian record confirms Hezekiah's historicity and this campaign's general reality; it does not confirm 702 BC as the specific year, and stating it that way overstates the evidence. A conditional reconciliation for this one-year gap is detailed in the next section — treat it as exactly that: conditional, not as independent confirmation. Artaxerxes' decree (457 BC) converts to B = 981, Y = 1 — confirmed by the Elephantine Papyri, Persian-era Jewish legal documents, though see the Exodus-Date Derivation section below for the genuine 457-vs-458 dispute this also carries. Stephen's martyrdom (34 AD) converts to B = 1471, Y = 1, though this rests on narrative sequencing in Acts rather than an independent secular record, making it the weakest of the three. The 702 BC Jubilee: The Double Rest-Year Argument Leviticus 25's own math produces a real, structural pattern worth presenting on its own strength: the year immediately before every Jubilee (Y=49) is mechanically also an ordinary sabbatical, since 49 is itself a multiple of 7. Assuming adherence to both laws, this produces two consecutive rest years — 703 BC (Y=49, an ordinary sabbatical) and 702 BC (Y=1, the Jubilee itself) — with no sowing in either preceding autumn. The resulting lack of harvest would extend across two consecutive springs, 702 BC and 701 BC, matching the shape of Isaiah 37:30's own three-stage sign ("this year... the second year... then... sow and reap") — a fit worth noting, not a proof of it. Sennacherib's campaign and the miraculous deliverance (2 Kings 19:35, Isaiah 37:36) fall within 701 BC — Y=2, the year immediately after the Jubilee. That year's agricultural condition would follow from the preceding rest years under this specific reading; it isn't independent confirmation that this is what happened. This mechanism holds under either reading of the 49-vs-50-year question (see below), which is itself an additional reason to prefer the convention this kit uses. One honest flag worth keeping, briefly, and stated plainly rather than as an afterthought: this reading of Isaiah 37:30 (a rest period already in force before the invasion) is one of two live options, not the consensus one — Rodger Young and most careful chronologists read the war itself as causing the first year's disruption, requiring no pre-declared Jubilee at all. Both readings are textually defensible. This section presents the one that produces the tightest structural fit with the CJC's own math — that fit is a reason to find the reading interesting, not a reason to treat 702 BC as confirmed. A further possible contributor to the one-year gap: calendar misalignment. The standardized intercalation cycle that later kept lunar and solar calendars synchronized wasn't adopted until roughly 503-499 BC, two centuries after Sennacherib's campaign. Before this, both Assyrian and Judean calendars added leap months ad hoc, by decree rather than fixed rule — and Assyrian record-keeping shows no evidence of astronomical observation guiding this process at all. Under these conditions, a real gap of weeks to a month could exist between the two calendars' year-boundaries, meaning the same actual date might be labeled 701 BC under one system and 702 BC under the other. This is a real, evidenced mechanism, not speculation — but whether Hezekiah's deliverance specifically fell within that gap can't currently be confirmed, since neither Scripture nor Sennacherib's own annals give a precise enough date to test it. Present this as a well-supported *possible* contributor alongside the double rest-year reading above, not a demonstrated resolution. The Exodus-Date Derivation: What's Actually Independent, and What Isn't *This section is the detailed support for the "unresolved Exodus date" position above. It's included in full because the honesty of showing exactly why this anchor doesn't hold up, after extensive testing, matters as much as showing why the strong anchors are strong.* Four biblical arguments are commonly cited as converging on a specific Exodus date. This session tested each rigorously, along with several additional proposed paths, and none succeeded in independently establishing 1437 BC specifically. 1 Kings 6:1 (temple construction, 480 years after the Exodus): this is conditional, not standalone. Thiele's own rigorous, Assyrian-anchored reconstruction (Solomon's 4th year at 966/967 BC) produces 1446 BC, not 1437 BC, when the stated 480-year interval is applied directly — this was independently re-verified this session and confirmed to match Rodger Young's separate three-way cross-checked reconstruction. A proposed bridge using an alternative figure (958 BC, from Albright/Rowton's Tyre-king-list method) does connect cleanly to 1437 BC via simple arithmetic with no adjustment needed — but a specific attempt to justify this alternative through coregency adjustments was tested directly and found mathematically inconsistent: extending a coregency within a fixed 40-year total reign does not move where "year 4" falls, since the reign's start and end are both already fixed by the text and the external Assyrian anchor. No legitimate, sourced bridge from Thiele's own published figures to 1437 BC was found. The honest position: 966/967 BC leading to 1446 BC is the rigorously-grounded figure; 958 BC leading to 1437 BC works arithmetically but lacks independent justification for why that figure should be preferred over Thiele's. A specific chronological chain claiming to reach 1437 BC via Ahab's death date, tested directly against its own primary source: the original methodology (Larry Wilson, "Five Steps to Determine the Date of the Exodus," 1993/2010) explicitly computes the straightforward result first (Ahab's death, 852 BC, plus 120 regnal years to Solomon, plus 480 years to the Exodus = 1452 BC), states plainly that "1452 B.C. is not a Jubilee year," and then substitutes a different figure (106 "actual" years instead of 120 regnal years — a 14-year reduction) specifically because it produces 1437 BC instead. The document's own stated scholarly range for this kind of adjustment is 5-10 years; the 14-year figure used exceeds even the upper bound the author himself cites. This is a documented, source-confirmed instance of selecting an input to match a predetermined target, not an independent derivation. A separate "inclusive counting" argument, tested directly: a claim that "966 BC minus 479 years = 1445 BC, but inclusive overlap adjusts precisely to 1437 BC" asserts an 8-year shift with no shown mechanism. Inclusive counting and no-year-zero conventions, verified repeatedly throughout this kit's testing, account for at most a 1-year adjustment — not 8. This claim states its conclusion without demonstrating the arithmetic that reaches it. The Tel Dan Stele regnal chain, tested directly: the stele itself ("Bet David," "House of David," discovered 1993-94) is genuine, uncontested archaeology confirming David as a historical figure — this stands on its own merits regardless of any chronological chain built on it. A specific proposed chain from the stele to 1437 BC (via reconstructed accession dates for David and Solomon) contained an internal arithmetic inconsistency: a claimed Solomon accession of 971 BC paired with a claimed "4th regnal year" of 958 BC, a 13-year gap where a 4-year one is required. This specific chain has not been independently verified. An "astronomical Manna Test" claim, tested directly and decisively falsified: a claim that April 3, 1437 BC showed "approximately 95% illumination" — offered as a test of Nisan 14 per Exodus 12:2, 12:6, and Numbers 33:3's departure narrative — was checked using the same moon-phase algorithm used throughout this kit. The actual result: 14.9% illumination, a thin waxing crescent. The true full moon near this period falls around April 14, 1437 BC (99.9% illumination) — eleven days later than claimed, and the 95% figure specifically matches a different date roughly nine days after the one claimed. This should not be cited in any form. Acts 13:20 (roughly 450 years for the judges period): this has a genuine, documented Greek syntax ambiguity, and separately, summing the individual periods given throughout Judges and Acts produces a total (570-573 years) far exceeding 1 Kings 6:1's 480 years — a roughly 90-year discrepancy with no single, agreed scholarly resolution. Multiple proposed solutions exist (summing specific servitude periods, treating oppressions as overlapping, reading the 450 years as describing an earlier span) and do not converge on a specific figure. A key structural finding that changes how all of this should be weighed: direct testing confirms that 457 BC, 702 BC, and AD 30 retain identical Y-values under any candidate starting point that is a multiple of 49 years from another — meaning the specific Exodus year is not actually required for this framework's strongest claims to hold at all. This makes the extensive search above for an independent 1437 BC confirmation a genuinely open question rather than a load-bearing one — worth continuing to investigate, but not something the rest of this kit depends on resolving. A credible rival reconstruction exists and deserves to be named directly, not passed over. Rodger Young's peer-reviewed work (*Andrews University Seminary Studies*, 2007) independently cross-checks three separate methods — Thiele's regnal chronology, the Jubilee/Sabbatical calendar (anchored via Ezekiel 40:1), and the Tyrian king list preserved in Josephus — and all three converge within a year or two of each other on 1446 BC for the Exodus, with Solomon's fourth year landing at 967-968 BC, matching Thiele's own figure closely. This is exactly the kind of outcome-blind, multi-method consilience this document's own reasoning error section calls for, and it does not support 1437 BC. The 49-Year-vs-50-Year Question, and Why It Matters Here Specifically A related, older question resurfaces directly in the argument above: Leviticus 25 describes counting 49 years and then consecrating a distinct fiftieth year as the Jubilee. If the Jubilee is a genuinely separate 50th year rather than simultaneously the first year of the next 49-year count (the convention this framework uses, Y=1), every Y=1 position claimed as a Jubilee throughout this kit could be off by one year. This is a real, historically documented question — the Babylonian Talmud (Nedarim 61a) records a dispute between the Sages (holding the separate-50th-year view, the majority position later halakhic authorities generally followed) and Rabbi Yehuda (holding the overlapping view this framework uses, a real but minority position). This is checkable, not merely a matter of preference. Three sabbatical years — 164/163 BC, 38/37 BC, and 68/69 AD — are independently reconstructed by historians (not by this research) from Josephus, 1 Maccabees, and Judean Desert legal documents, and all three land on B mod 7 = 0, confirming an unbroken ordinary seven-year rhythm with no resets across the tested span. Testing whether the Jubilee position should instead be shifted to align exactly with this same rhythm (rather than sitting one position after it, as this framework's convention has it) was checked directly: shifting Hezekiah's Jubilee to fit that alternate reading moves it from 702 BC to 703 BC — two years removed from the externally-attested 701 BC Sennacherib campaign, instead of one. The existing convention fits the external anchor more tightly, which is a real, if modest, reason to prefer it over the shift, not an assumption papered over. The double rest-year mechanism above (Y=49 always mechanically preceding a Jubilee) was tested against both readings directly and holds under either — an additional, independent reason favoring the overlapping convention specifically, since the separate-50th-year reading produces the worse fit to the external anchor. Two textual arguments also favor the overlapping reading. First, Pentecost: Leviticus 23:15-16 counts seven weeks (49 days) and names the next day, the fiftieth, for the offering; that fiftieth day is also the first day of the eighth week, the same 50th-is-also-1st pattern at a scale no one disputes. Second, Ezekiel's 430 years (Ezekiel 4:5-6): eight full 49-year cycles hold 64 rest years (seven sabbaticals plus the Jubilee in each), and the 38 remaining years hold 6 more (the Jubilee and five sabbaticals), for exactly 70, matching 2 Chronicles 36:21. A Rival Model: Jubilees Counted from the Second Temple's Completion Some count eleven 50-year Jubilees from the Second Temple's completion (about 515 BC, Ezra 6:15) to AD 33, a total of 550 years. The main disagreement is cycle length (see above). Its starting point is also an inference its own proponents acknowledge: Scripture never ties a Jubilee to the temple's completion rather than to the 538 BC decree, the 536 BC foundation, or Zerubbabel's return. The CJC's key dates, the 457 BC decree and the AD 30 crucifixion, are checked against records outside the Jubilee count. The Four Cycles the CJC Tracks, and How to Enumerate Each A user may ask for a single year's status, or for every occurrence of something across a range of centuries. The CJC actually tracks four distinct, easily-confused layers — keep them separate, and use the specific procedure for each: 1. The literal historical weekday of a specific calendar date. This is ordinary calendar fact, unrelated to the CJC's own math — every date in history fell on some real day of the week, the same way every date today does. To find it: use the 196-year exact rule below if a confirmed anchor date is available within a multiple of 196 years; otherwise use standard calendar-weekday computation (for dates before 1582, using the Julian calendar, not the Gregorian). This is a different question from the symbolic system in point 2, and the two should never be presented as the same claim. 2. The Position assigned to a year (Y mod 7). Every single year, without exception, falls at one of seven positions determined by its Y-value. To find one year: compute B, then Cycle, then Y using the formula above, then take Y mod 7 (remainder 1 = Position 1... remainder 0 = Position 7). To list a range of years: repeat this for each year in turn. The sequence never breaks or resets at a cycle boundary — since 49 is itself a multiple of 7, the Position count continues its normal forward step directly from Y=49 (Position 7) into Y=1 of the next cycle (Position 1), the same way an ordinary week continues from its seventh day into a new first day. No special-casing is needed at any boundary. 3. The seven-year sabbatical cycle (an ordinary land-rest year). A year is an ordinary sabbatical when B mod 7 = 0. This is different from the weekly Sabbath (which occurs every seven days, every week, for everyone, with no connection to this calendar) and different from the Jubilee (point 4). To check one year: compute B, check B mod 7. To list every sabbatical year in a range: convert both ends of the range to B-values, then list every B in that span divisible by 7 evenly. 4. The forty-nine-year Jubilee cycle. A year is a Jubilee precisely when Y = 1 (equivalently, B mod 49 = 1). To check one year: compute Y directly. To list every Jubilee in a range: convert both ends of the range to B-values, then list every B in that span where B mod 49 = 1. When asked to "list all sabbaths" without further clarification, ask the user whether they mean the weekly Sabbath (trivial — every seventh day, no calculation needed), the seven-year sabbatical cycle (point 3), or the forty-nine-year Jubilee (point 4), since these are three genuinely different things this framework tracks and conflating them produces a wrong answer even when the arithmetic is correct. The Seven-Year Sabbatical Chain, Externally Confirmed Three historically-attested sabbatical years, independently reconstructed by historians from Josephus, 1 Maccabees, and Judean Desert legal documents — with no connection to this research — all satisfy B mod 7 = 0: 164/163 BC converts to B = 1274; 38/37 BC converts to B = 1400; 68/69 AD converts to B = 1505. All three divide evenly by 7. Of these three, 164/163 BC has the strongest independent grounding: 1 Maccabees 6:49 specifically uses the Hebrew term for an ordinary sabbatical (shemittah), not Jubilee (yovel) — two distinct, non-overlapping words — and rabbinic and historical sources confirm the Jubilee itself was not being actively tracked during this Second Temple period, meaning the ancient author could only have meant the institution actually in practice. A rival reading (163/162 BC) would place the same event during what this framework computes as a Jubilee year specifically — mismatching the text's own precise word choice. The 38/37 BC and 68/69 AD dates remain genuinely contested among specialists (Zuckermann vs. Wacholder, among others) and should be presented with that caveat attached. An Exact Tool With Zero Uncertainty Because the Julian calendar's leap-year rule repeats exactly every four years, any 196-year span (four Jubilee cycles) contains exactly 49 leap days regardless of where it begins. Since 196 × 365.25 = 71,589 days, and 71,589 ÷ 7 = 10,227 exactly, the literal day-of-week for any fixed calendar date repeats exactly every 196 years — a provable arithmetic identity, not an estimate. This identity holds only for the Julian calendar specifically, and does not carry over to the Gregorian calendar used today (adopted in 1582). The Gregorian calendar adds century-year exceptions — years divisible by 100 are not leap years unless also divisible by 400 — which breaks the clean 196-year pattern. A 196-year Gregorian span can contain 47, 48, or 49 leap days depending on which century boundaries it crosses, not a guaranteed 49. Apply this rule only to spans reckoned in the proleptic Julian calendar (the standard convention for ancient and biblical chronology throughout this kit), not to spans crossing into or contained within the modern Gregorian calendar without a separate adjustment. A second calendar-convention pitfall worth naming directly: astronomical year numbering includes a "year zero" between 1 BC and 1 AD, while the traditional BC/AD dating used throughout this kit does not — 1 BC is immediately followed by AD 1, with nothing in between. Some calendar software and calculation tools default to astronomical year numbering without stating so, which introduces a one-year offset if mixed carelessly with the BC/AD convention this kit uses. When converting between the two systems, or when a result seems to be off by exactly one year, check this first. General-Purpose Tools: Literal Weekday and Moon Phase for Any Date Everything above in this kit demonstrates the crucifixion week as one specific, fully-worked example. This section generalizes both calculations so they can be applied to *any* date — ancient or modern — using the exact same method every time, rather than depending on whatever calendrical knowledge a given AI system happens to have natively. Run both procedures explicitly, showing each step, rather than skipping to an answer. Step 1 — Convert the target date to a Julian Day Number (JD). For a date in year Y, month M, day D: A critical conversion, easy to miss and severe if missed: the formulas below require *astronomical year numbering*, where 1 BC = year 0, 2 BC = year −1, 3 BC = year −2, and so on — a different convention from the positive-BC-count this kit's own B formula uses (where 702 BC is entered as "702"). Before using Y below, convert any BC year first: astronomical Y = −(BC year − 1). For example, 702 BC becomes astronomical Y = −701, not 702. Skipping this conversion produces a Julian Day Number off by hundreds of thousands of days — an error of over a thousand years, not a rounding issue. For AD years, no conversion is needed; the astronomical year and the calendar year are identical. If M ≤ 2, set Y = Y − 1 and M = M + 12. *For the proleptic Julian calendar* (standard for any date before the Gregorian reform of October 1582, and the default throughout this kit unless a date is explicitly modern): JD = floor(365.25 × (Y + 4716)) + floor(30.6001 × (M + 1)) + D − 1524.5 *For the Gregorian calendar* (standard for dates after 1582, and always for the modern era): A = floor(Y / 100), B = 2 − A + floor(A / 4) JD = floor(365.25 × (Y + 4716)) + floor(30.6001 × (M + 1)) + D + B − 1524.5 Step 2 — Literal weekday from JD. Compute floor(JD + 1.5), then take that number mod 7. Remainder 0 = Sunday, 1 = Monday, 2 = Tuesday, 3 = Wednesday, 4 = Thursday, 5 = Friday, 6 = Saturday. This is exact and deterministic — no uncertainty at all, for any date in either calendar. Step 3 — Moon phase from JD. Estimate which synodic month (k) the date falls in: k ≈ (JD − 2451550.1) / 29.530588861, rounded to the nearest whole number. Compute that new moon's JD: T = k / 1236.85 JDE = 2451550.09766 + 29.530588861×k + 0.00015437×T² − 0.000000150×T³ + 0.00000000073×T⁴ Apply the main correction terms (Meeus, *Astronomical Algorithms*, Ch. 49): M = 2.5534 + 29.10535669×k (mod 360, in degrees, then converted to radians) M′ = 201.5643 + 385.81693528×k + 0.0107582×T² (mod 360, radians) F = 160.7108 + 390.67050284×k − 0.0016118×T² (mod 360, radians) Correction = −0.40720×sin(M′) + 0.17241×sin(M) + 0.01608×sin(2M′) + 0.01039×sin(2F) + 0.00739×sin(M′−M) − 0.00514×sin(M′+M) + 0.00208×sin(2M) New moon JD = JDE + Correction. If this result is *after* the target date, recompute using k − 1 instead, so the new moon used is the most recent one before or on the target date. Step 4 — Age and illumination. Moon age (days) = target JD − new moon JD. Illumination percentage ≈ (1 − cos(2π × age / 29.530588861)) / 2 × 100. Phase name: 0-1.8 days = New Moon, 1.8-5.5 = Waxing Crescent, 5.5-9.2 = First Quarter, 9.2-12.9 = Waxing Gibbous, 12.9-16.6 = Full Moon, 16.6-20.3 = Waning Gibbous, 20.3-24.0 = Last Quarter, 24.0-27.7 = Waning Crescent, 27.7-29.5 = New Moon (approaching). An honest precision note, consistent with the rest of this kit: the weekday result is exact. The moon-phase result carries the same low-precision limitation already noted for the crucifixion week — reliable to within roughly a day, not to the hour, and progressively less certain the further back in time the target date sits, since this simplified formula omits smaller periodic terms a full ephemeris would include. State results with this precision level attached, not as more certain than they are. For any case where precision genuinely matters, cross-check this kit's moon-phase output against an established external source — NASA/Fred Espenak's published lunar phase tables and eclipse catalogs are the standard reference most professional astronomers use, and are a better authority than this kit's own simplified formula wherever the two can be compared. Worked check, so this can be verified against a known result: applying this procedure to August 26, AD 30 (Julian calendar) gives JD ≈ 1732252.5, a literal weekday of Saturday, a moon age of about 8.2 days, about 58.5% illuminated, First Quarter. Confirm this independently before trusting the procedure on a new date. When checking whether a date can be Nisan 14 specifically, cite the scriptural requirement being tested alongside the illumination result, not just the number on its own: Exodus 12:2 and 12:6 define Passover by the first month and its fourteenth day, and Leviticus 23:5 confirms the same. The astronomical figure tests whether a proposed date is compatible with these specific verses — it does not replace them, and should always be presented as a reconstruction being checked against the text, not as an independent authority standing apart from it. Worked example, Acts 12: Peter's imprisonment, verified against the primary source. Herod Agrippa I's death is independently fixed to AD 44 by Josephus. Parker and Dubberstein's *Babylonian Chronology* (Oriental Institute of the University of Chicago, 1942/1956) — verified directly against the primary table (p. 60, row for AD 44) — records Nisanu 1 at April 18, AD 44. Thirteen days later (Nisan 14, per Exodus 12:2 and 12:6) falls on May 1, AD 44, independently confirmed as a Friday by direct calendar computation. This converts to Y=11 (Y mod 7 = 4, a mid-point position) under this kit's formula. Acts 12:3-4 places Peter's arrest "during the days of Unleavened Bread," intending his execution "after the Passover" — both consistent with this date. This is the strongest externally-verified lunar/festival date check in this kit outside the crucifixion week itself, since it traces cleanly from a primary source through to an independently-confirmed weekday. The Gallio inscription at Delphi dates Gallio's proconsulship of Achaia to about AD 51-52, fixing Paul's hearing before him (Acts 18:12) to that year. AD 51 converts to B = 1488, Y = 18 (Position 4). As with Acts 12, the position itself carries no prophetic weight; the value is the external date. A second worked check, this one testing the Exodus reconstruction directly: applying this procedure to Nisan 14 of the Exodus year (using the same 1437 BC numbering constant as elsewhere in this kit) — the date required by Exodus 12:2, 12:6, and confirmed by Leviticus 23:5 — gives a genuine full moon (99.9% illumination) on April 14 of that year — a real astronomical confirmation of the lunar reckoning's internal consistency, distinct from and correcting an earlier, decisively falsified claim about a different date within the same month. Testing the Candidate Starting Point Itself: The Blind Phase Test A stronger test than checking individual dates one at a time is this: take a set of independently-dated ancient events, and instead of only checking whether they land on Y=1 under a candidate starting point, test *all 49 possible starting-point phase-shifts* and see whether that specific phase actually produces an unusual number of Y=1 matches compared to the other 48 candidate phases. If many other, arbitrary phases perform just as well, that is real evidence the apparent pattern could be a coincidence of the specific dataset rather than something meaningful about that phase specifically. The procedure: for a set of events with known B-values, and for each candidate offset from 0 to 48, count how many events satisfy (B − offset − 1) mod 49 = 0. Compare the count at offset 0 (the actual claimed starting point) against the best-performing alternative offsets. This test has been run multiple times against genuinely independent secular datasets (spanning Assyrian, Babylonian, Persian, Hellenistic, and Roman history, deliberately excluding this kit's own claimed anchors). The result was consistently negative: the claimed phase did not stand out from the other 48 candidates in any of these tests, ranking near or below the median in every case. This is an honest, important negative finding — it does not disprove the framework's specific, narrower claims (the crucifixion week, the 457 BC decree), but it does mean the broader 49-year cycle's phase does not show a special signature against unrelated ancient world history, which is the expected, non-mysterious result for a specifically Israelite religious institution rather than a universal historical rhythm. A related test worth naming directly: an apparent statistical anomaly was found in one targeted dataset of Jewish/Judean historical events (a "mid-point" position appearing more often than chance would predict). This was tested further — first for whether the finding survived correcting for clustered, non-independent events (it did not fully survive), and then via a genuine, stated-in-advance prediction against a fresh dataset (the prediction failed outright). This sequence — an initially striking result dissolving under proper testing — is documented in full as an example of the discipline this kit is built around, not something to quietly omit because it did not hold up. A limitation worth knowing before running any version of this test: a small, hand-selected dataset — especially one partly chosen because some of its events were already known to be Y=1 hits — will generically produce some alternative offset with two or three coincidental matches, purely because 49 different offsets are being checked at once (a multiple-comparisons effect). A rigorous version of this test requires a large, genuinely independent dataset of precisely-dated ancient events, gathered without pre-filtering for apparent relevance to this chronology. A Reasoning Error Worth Avoiding If two dates have a year-gap that is a multiple of 49, they will share the same Y-value under any consistently-applied starting point — not only under one specific candidate starting point. This is a real mathematical fact (verifiable by picking any arbitrary starting point and checking), and it means a shared Y-value between two events proves the 49-year count ran without drift between them, but does not by itself prove which starting point is correct. This has been directly demonstrated this session: building a starting point around any of several candidate historical decrees makes that specific decree "the only one that fits," regardless of which one is actually correct — internal consistency of a self-built system is not the same as independent confirmation that the system's starting assumption is true. A related and equally important caution: a year's Position (Y mod 7) and a date's literal weekday (its real position in the calendar week) are mathematically unrelated systems — one cycles with a period of 7 tied to an assumed starting point, the other governed by the Julian calendar's own leap-year structure (see the 196-year exact identity above for the proven, rather than approximate, version of this claim). Any apparent match between the two (a year at Position 2 happening to begin on a literal Monday, for instance) carries no evidential weight in either direction — it is expected to occur by chance roughly one time in seven, regardless of whether any underlying starting-point claim is true. Keep this distinction in mind when testing new dates: a match is real evidence of unbroken continuity, not automatically evidence for the specific starting point, and a coincidence between two unrelated mathematical systems is not evidence for anything at all. A CJC-internal alignment can establish that a date occupies a particular position within the CJC; it cannot by itself establish that the CJC's phase, starting point, or interpretation of Scripture is historically correct. What This Kit Does Not Include No probability or statistical figures are presented here as established conclusions, beyond the specific, shown calculations in the Blind Phase Test section above. That entire area of the underlying research was found to be unreliable in earlier drafts — inconsistent by many orders of magnitude between different documents, with confirmed arithmetic errors in at least two places — and remains under active reconstruction. Treat any probability claim either you or the AI is tempted to generate during this exploration with real skepticism, and check the arithmetic behind it directly, the same way every other figure above should be checked. This kit also does not include the Daniel 7 "little horn" / 538-1798 AD framework, tested extensively and found unsupported on every mechanism attempted (direct CJC math, forward projection from established anchors, historical dating methodology, and a statistical test against all historically-proposed candidate starting dates). Nor does it include the "Manna Test" astronomical claim (decisively falsified) or the specific chronological chains to 1437 BC described in the Exodus-Date Derivation section above as unverified. Eleven Teaching Examples: The CJC's Strongest, Most-Searched Answers These eleven questions are drawn from the most commonly searched biblical dating debates online, ranked here by how much genuine, verifiable CJC support each one has — strongest first. Each is designed to be taught in full: the math, the alignments, and the honest caveats together, exactly as this kit presents them elsewhere. Use these as a starting curriculum before moving to open-ended testing. 1. When did the crucifixion happen — AD 30 or AD 33? The CJC's single most extensively-tested question. AD 30 computes to Y=46 (Position 4, the mid-point); AD 33 computes to Y=49 (not the mid-point). See "Why AD 30, Not AD 33" above for the full multi-criteria teaching case. 2. What decree starts Daniel's seventy weeks — 457 BC or 458 BC? 457 BC computes to Y=1, a Jubilee — the only one of four historically-attested decrees to do so. See "Five Independent Starting Points," Anchor 2, and the honest 457/458 dispute noted there. 3. When was the resurrection? April 9, AD 30, a Sunday — reached by direct, inclusive counting from the crucifixion ("the third day," Matthew 16:21, Luke 24:46, 1 Corinthians 15:4 KJV), verified two independent ways. See "From Crucifixion to Pentecost" above. 4. When was the Temple destroyed in AD 70? Y=37 under the CJC's own math — not a Jubilee or mid-point, a good teaching example of the CJC correctly *not* manufacturing significance where none exists. The specific day carries an honest range (August 6-8, Monday-Wednesday) rather than false precision, since the underlying calendar itself, not the arithmetic, is what's uncertain. See "From Crucifixion to Pentecost." 5. When was Jesus born? 4 BC is the only candidate year producing exactly age 30 at the AD 27 baptism and age 33 at the AD 30 crucifixion — a consistency check across two already-established anchors, not independent proof on its own. See "Five Independent Starting Points," Anchor 4. 6. When did the Exodus happen — 1446 BC or 1437 BC? 1446 BC (Thiele/Rodger Young) is the more rigorously-sourced historical figure; 1437 BC is this kit's own working reference point, reached by running the established chain backward, not independently derived. Most importantly: none of the CJC's strongest claims require this question to be resolved at all. See "No Single Exodus Date Is Required" and "The Exodus-Date Derivation." 7. When did Solomon build the Temple? Tied directly to the Exodus-date question above via 1 Kings 6:1's stated 480-year interval — teach this alongside #6, not separately, since they're the same underlying question viewed from two verses. 8. When did Herod the Great die? The 4 BC vs. 1 BC dispute directly affects question #5 above — teach these together as one connected consistency check, not as isolated facts. 9. When did the plagues of Egypt occur, within the Exodus year? The agricultural evidence in Exodus 9:31-32 (barley and flax destroyed by hail; wheat and spelt spared) matches Egypt's real, historically-documented growing calendar — a genuinely verifiable textual-historical detail, regardless of which Exodus year is ultimately preferred. 10. How long was the Babylonian exile, and does it match Scripture's own count? Ezekiel's assigned 430 years of symbolic apostasy, divided into 49-year cycles, produces exactly 70 sabbatical years — matching 2 Chronicles 36:21's independent statement that the exile lasted until the land received the 70 years of sabbath rest it had been denied. 11. What is the "abomination of desolation" — and what did it mean in AD 70? Daniel's phrase has two separate fulfillments, and the right answer depends on which passage is being asked about (see "The Two Uses of 'the Abomination of Desolation'" above). The one Jesus warned his own followers about is the first, and it has already happened. In Matthew 24:15-16 and Mark 13:14 he says that when the abomination stands in the holy place, those in Judea must flee to the mountains. Luke 21:20-21, recording the same warning for a non-Jewish audience, says in plain words what they would see: Jerusalem surrounded by armies. When the Roman legions encircled the city and stood on the holy ground around it, the Christians heeded the warning and fled — Eusebius records their escape to Pella — and Titus destroyed the city and the temple in AD 70, fulfilling Daniel 9:26-27 and 11:31. Teach this use first, since it is the one with historical record behind it: the warning, the siege, the flight, and the destruction are all independently attested. AD 70 computes to Y = 37 — not a Jubilee or mid-point — so this is also a good example of the CJC not manufacturing significance. The second use (Daniel 12:11) is still future: a death decree set up on day 1,290 of the great tribulation, an interpretive reading that cannot be dated in advance. Sample Prompts to Try After Pasting This Document Copy any of these directly, or write your own in the same spirit: • "Using the formula above, compute the Cycle and Year for [any date you want to test]. Show every step." • "I have a historically-documented event dated to [year]. Does it land on a Jubilee, the cycle's mid-point, or an ordinary sabbatical position? What is your source for that date, and how confident is it?" • "Test whether 457 BC, 702 BC, and AD 30 really do land on the same Y-values under different candidate starting points a multiple of 49 years apart (try 1437 BC, 1486 BC, 1388 BC). Then check what happens under 1446 BC specifically, and explain why it's a different kind of candidate." • "Walk me through why AD 30 is preferred over AD 33 for the crucifixion, using only the four criteria that don't depend on the Humphreys-Waddington eclipse argument." • "Test the Sennacherib/Hezekiah reconciliation: show me the double rest-year mechanism, and be clear about what it does and doesn't prove about 702 BC being a true Jubilee." • "Check whether my proposed connection between [event A] and [event B] is a genuine starting-point-confirming match or just a starting-point-independent continuity match, using the reasoning-error section above." • "Walk me through verifying the 196-year weekday rule's arithmetic yourself, step by step, without taking the document's word for it." • "Using the general-purpose moon-phase tool, check whether [any date] shows a genuine full moon, the way this kit's Nisan 14 reconstruction was corrected to do properly." • "Help me run a proper blind phase test using a genuinely large, independent dataset of ancient events you're aware of — not just the ones already mentioned in this document." • "Explain why this kit no longer requires a specific Exodus year to be resolved, and what would actually need to be true for 1437 BC specifically to be independently confirmed." • "Walk me through how Luke 3:1's 'fifteenth year of Tiberius' reaches AD 27, using the coregency law and the RIC 225–226 coins. Then show what year each alternative counting method produces." • "What is the abomination of desolation Jesus warned about in Matthew 24:15? Explain the AD 70 fulfillment using Luke 21:20, then explain how it differs from the future use in Daniel 12:11." The goal of this kit is not to hand you a finished conclusion — it is to give you and any AI system you're working with a shared, checkable starting point, so your own research can extend, test, and challenge this material rather than simply repeat it.