Melchizedek Calendar

Forensic Chon P3

R2 — 350-Year Rail Recovery Packet

Establish / Re-establish God-Appointed Rightful Order Within the Inheritance

RECOVERY / FORENSIC EDITION — VERSION 0.1

27 September 2026

Contents

1. Recovery mandate and non-flattening controls

2. The 350-year rail at a glance

3. What the 350-year clock seems to do

4. 2221 BC — Babel / Peleg / Eber-line narrowing and preservation

5. 1871 BC — deliberate blank / non-hit

6. 1521 BC — inheritance, possession, Shiloh, and rest

7. 1171 BC — Saul and the establishment / renewal of kingdom order

8. 821 BC — open event slot, strong functional confirmation

9. 471 BC — rightful order preserved at the 350/500 hinge

10. 121 BC — later Hasmonean candidate, not a settled assignment

11. AD 3030 — full 350/500 synchronization boundary

12. The four-coordinate dense run: 1521 → 1171 → 821 → 471

13. Cross-rail hooks to 500, 50, 7, 3,500, and 7,000

14. Functional-theme density matrix

15. Before-and-after discovery / supersession ledger

16. Verification priority and open recovery queue

17. Exact continuation point

Appendix A — Scripture register

Appendix B — tags and relationship labels

1. Recovery mandate and non-flattening controls#

The Recovery Master establishes the 350-year headline function as: establish / re-establish God-appointed rightful order within the inheritance. Fuller descriptors include appointment, anointing, covenant, kingdom, judgment, sanctuary/priestly restoration, rightful authority, possession, and rest.

Every coordinate is kept in four separate fields:

• Coordinate / arithmetic.

• Event identity or event cluster.

• Observed function.

• Status / evidence maturity.

R2 authority notes#

2. The 350-year rail at a glance#

3. What the 350-year clock seems to do#

The mathematical reason 350 appears is straightforward: 350 = 7×50. It is the first natural period at which the 7-year and 50-year rhythms can realign. But the later forensic work did not stop at arithmetic. It compared the scenes that occupied recovered 350 coordinates.

4. 2221 BC — Babel / Peleg / Eber-line narrowing and preservation#

Genesis 10:25 — Peleg is named in connection with the division of the earth in his days.

Genesis 11:1–9 — Babel ends in divine scattering and division of the nations.

Genesis 11:14–17 — The Eber-line genealogy continues through the division period.

The recovered 350-year observation is not that Babel itself is ‘good order.’ The point is the divine ordering after human consolidation and rebellion: the nations are divided, boundaries/history move forward, and the promise-bearing line is preserved through Eber/Peleg rather than dissolved into Babel.

This is a functional hit, not yet a fully audited civil-year date. R2 therefore preserves both the scene and the chronology-audit requirement.

5. 1871 BC — deliberate blank / non-hit#

This blank is structurally important. The patriarchal story is active in this region of the chronology, but no event has been recovered with enough independent support to occupy the 1871 marker.

• Do not drag Abraham, Isaac, Jacob, or another patriarchal event to 1871 merely because the coordinate exists.

• Do not treat a blank as a weakness that must be repaired.

• Preserve the blank in every future 350-year diagram and packet unless an independently derived chronology supplies an occupant.

6. 1521 BC — inheritance, possession, Shiloh, and rest#

Joshua 18:1–10 — The tabernacle is established at Shiloh; the land is subdued; remaining inheritances are ordered by lot before the LORD.

Joshua 21:43–45 — The land is given, possessed, dwelt in, and rest is granted round about.

Leviticus 25:8–10 — Jubilee later governs liberty and return to possession, presupposing an inheritance order to administer.

1521 is the clearest point where the mathematical and functional meanings of 350 meet. From the Fall it is 2,450 years = 7×350 = 49×50. The scene is not merely entry into Canaan. The recovered emphasis is inheritance ordered, possession administered, sanctuary established, and rest reached.

The exact occupant remains between the Shiloh/land-subdued/allotment phase and the later possession/rest culmination. R2 does not force one verse into the entire coordinate.

7. 1171 BC — Saul and the establishment / renewal of kingdom order#

1 Samuel 8 — Israel requests a king; the text preserves both the people’s motive problem and YHWH’s warning.

1 Samuel 9–10 — Saul is selected and anointed; the office is installed under YHWH’s direction despite the people’s compromised request.

1 Samuel 11:14–15 — Samuel calls Israel to Gilgal to ‘renew the kingdom’; Saul is made king before the LORD and sacrifices are offered.

The function here must be stated carefully. The 350-year rail is not validating every motive behind human monarchy or every later act of Saul. The scene is about installation of governing order: selection, anointing, public confirmation, covenantal setting, and the kingdom renewed before YHWH.

This makes 1171 a strong complement to 1521: land/inheritance order is followed one 350-year span later by national kingdom order.

8. 821 BC — open event slot, strong functional confirmation#

The coordinate is 3,150 years from the strict Fall coordinate = 9×350. The recovery must preserve an open identity while showing why the function became compelling.

Clearest cluster — Joash / Jehoiada#

2 Kings 11:4–21 — The hidden royal heir is brought out, crowned, covenant order is renewed, Baal’s order is broken, and the king sits upon the throne.

2 Kings 11:17 — Jehoiada makes covenant between the LORD, the king, and the people.

2 Kings 12 — Temple repair becomes a central work of the restored reign.

2 Chronicles 23–24 — The same complex joins heir preservation, enthronement, priestly leadership, covenant renewal, removal of corrupt worship, and sanctuary repair.

This cluster has unusually high 350-function density: rightful heir preserved, royal authority restored, priestly guidance, covenant renewed, false order removed, Temple repaired.

Supporting witnesses — not automatic occupants#

Jehu and Hezekiah were retained as supporting functional witnesses because they exhibit parts of the same order-restoration vocabulary.

• Jehu: judgment against Ahab’s house and destruction of Baal worship, but with important limitations; not automatically the 821 occupant.

• Hezekiah: sanctuary reopening, priestly order, Passover restoration, worship reform, and national reordering; not automatically the 821 occupant.

9. 471 BC — rightful order preserved at the 350/500 hinge#

Esther 8 — Royal decrees and Mordecai’s elevation reverse the administrative direction of the crisis toward preservation.

Esther 9:1 — The threatened reversal becomes an actual reversal: the opposite result occurs.

Esther 9:16–18, 22 — Rest follows the threat; sorrow is turned to joy.

Esther 10:2–3 — Mordecai’s high royal administration is linked with the welfare and peace of his people.

R1 viewed 471 primarily from the 500-year side: inheritance-bearing people are administered and preserved through royal authority. R2 views the same coordinate from the 350-year side: attempted annihilation and disorder are reversed so rightful order and covenant continuity survive.

10. 121 BC — later Hasmonean candidate, not a settled assignment#

The available recovery sources do not yet provide a complete independent chronology receipt or a governing Scripture passage for this post-biblical candidate. Therefore R2 preserves the candidate without developing it into proof.

• Do not rewrite the earlier blank history out of the record.

• Do not use the candidate as evidence that every 350-year marker must contain an event.

• Do not use priest-king resemblance alone to prove exact historical placement.

• Required next step: dedicated historical/chronological verification before reader inclusion.

11. AD 3030 — full 350/500 synchronization boundary#

Fall → AD3030 = 7,000 strict elapsed years. The same span equals 20×350 and 14×500.

R2 preserves this as the long hook back to R1. It does not assign a Second Coming, resurrection, judgment, millennial endpoint, or other event merely from synchronization.

12. The four-coordinate dense run: 1521 → 1171 → 821 → 471#

This is the strongest sustained functional run on the recovered 350-year rail. Each coordinate is separated by exactly 350 years, yet the scenes are not duplicates. They develop the same function across different levels of biblical order.

This density is why the 350 function was refined beyond the older description ‘7×50 synchronization.’ The synchronization remains the mathematical mechanism; the repeated biblical scenes supplied the functional description.

13. Cross-rail hooks to 500, 50, 7, 3,500, and 7,000#

14. Functional-theme density matrix#

15. Before-and-after discovery / supersession ledger#

16. Verification priority and open recovery queue#

Following the user’s requested highest-density-to-lowest-probability method, R2 sets this verification order:

Open recovery queue#

• Attach exact message-level provenance for the Sep. 25–27 approvals/corrections where the platform exposes it.

• 2221: verify absolute chronology for Babel / Peleg / Eber-line narrowing.

• 1171: verify Saulic chronology from explicit regnal and narrative data.

• 821: independently date-test Joash/Jehoiada and compare Jehu/Hezekiah.

• 121: verify whether the Hasmonean candidate survives a dedicated historical chronology audit.

• Name-meaning ledger: verify source-language meanings before using them in final reader prose.

• Do not let R2 alter the R1 971 branch fork; 971 is a 500 coordinate, not a 350 coordinate.

17. Exact continuation point#

R2 endpoint#

The recovered 350-year rail is not a demand that a famous event occur every 350 years. Its strongest run is selective and functionally coherent: after division, the promise-bearing line is preserved; inheritance is ordered in the land; kingdom authority is installed; royal-priestly-covenant-sanctuary order is restored; and the covenant people are preserved after an annihilation threat. The blanks remain part of the evidence because the rail is not forced.

Appendix A — Scripture register#

Appendix B — tags and relationship labels#

• ORDER / ESTABLISHMENT — installed or reinstalled rightful structure

• KINGLY — throne, kingdom, royal authority, judgment/administration

• PRIESTLY — priesthood, covenant service, sanctuary order

• COVENANT — public or legal ordering of people/king/priesthood under YHWH

• INHERITANCE — possession, allotment, lawful dwelling, administration

• PRESERVATION — promise-bearing line/people/heir survives division or threat

• JUDGMENT — divine or covenantal ordering by decision

• SANCTUARY / DWELLING — Shiloh/Temple/worship order

• REST / PEACE — result-state after possession, deliverance, or restored order

• MELCHIZEDEK HOOK — King + Priest convergence without collapsing separate offices in shadows

Controlled relationship labels#

• CHRONOLOGICAL_SEQUENCE

• MATHEMATICAL_PATTERN

• TYPOLOGY

• SYMBOLIC_PARALLEL

• THEMATIC_EXPANSION

• QUALIFIES

• CORRECTS

• SUPERSEDES