File: File_16 Title: The 1876 BC Nexus Status: Final; bounded September 13 2026 Terah-inclusive −33 scope pointer applied; post-final pressure tested; File_18 section-label, 2nd Cainan variant-boundary clarification, Pentateuchal Funnel structural-harmony clarification, File_19 Sundial Mirror cross-file update, 1876 Cainan macro-vector update applied, File_26 18766/18756 Nexus rail cross-file update applied; 1876 Cainan macro-vector update focused pressure tested; 60-multiple Shelah / Plenty-Famine note, Mirror 60-spine addendum, File_26 Nexus rail note, and Samaria Node cross-file update focused pressure tested under current Register Agreement; four-roads shared-label display bounded update applied (July 2026); File_20 §8A corruption-symmetry corroboration pointer applied (July 2026); File_59 Judah 1500-year / AD 25–30 bracket pointer applied and focused checked July 16 2026; bounded File_62 male 7+33 / localized −33 reciprocal pointer applied (July 2026); bounded File_64 lesser Judges–Sanctuary Nexus reciprocal pointer applied July 26 2026; bounded File_64 expanded Nexus / Jacob–Daniel reciprocal pointer applied July 27 2026; bounded Final File_65 reciprocal pointer applied August 3 2026; bounded File_66 reciprocal pointer applied August 8 2026 Pressure-test status: Current; focused pressure test complete for later File_26 Nexus rail, 60-multiple Shelah / Plenty-Famine, Mirror 60-spine, and Samaria Node bounded updates and public-clean cleanup; prior post-final and 1876 Cainan macro-vector focused tests retained. Focused check complete for the four-roads shared-label display bounded update. Focused check complete for the File_20 §8A corroboration-pointer bounded update; focused check complete for the bounded File_59 Judah 1476 BC → AD 25 = 1500 application pointer; bounded File_62 reciprocal pointer machine-diff checked; focused reciprocal-routing verification complete July 26 2026 for the original File_64 pointer; focused reciprocal-routing verification refreshed July 27 2026 for the expanded File_64 Nexus / Jacob–Daniel pointer; no new full pressure test claimed; no publication blocker. Bounded File_65 pointer received focused diff, guard, dependency, and Markdown checks only; no new full pressure test and no File_65 pressure-tested status claimed. Reciprocal-routing verification status: File_62 and File_64 pointers applied and bounded machine-diff, arithmetic, dependency, Machine Guard, Markdown-structure, protected-section, and publication-clean checks completed through July 27 2026; no new full pressure test was performed for these pointer-only updates. Final File_65 pointer applied August 3 2026 and focused machine-diff checked; no new full pressure test. Register Agreement status: Existing File_16 states and Machine Guards retain their prior control basis. The exact File_65 reciprocal guard is registered at State Vocabulary Register v1.36 Part D §D.29 and routed through Restart Capsule v11.35. The bounded File_65 pointer imports no File_65 coordinate as a File_16 Primary anchor, adds no Bullseye witness, and changes no pre-existing arithmetic, modal-state logic, node-class, operator definition, sign convention, slash-pair, range, envelope, Mirror protocol, claim-status label, theological claim, or dependency boundary. Current bounded reciprocal routing is aligned to State_Vocabulary_Register v1.38 / Restart Capsule v11.37; no pre-existing proof-bearing arithmetic or Primary anchor is changed. Publication-cleanup status: Public-clean Markdown source; archival amendment history routed to Repository_Change_Archive; File_65 reciprocal replacement prepared in the August 3 2026 release package. Primary domain: Regular; Cumulative; Rounded; Comparative; Prophetic; Theological; Mirror; Inverse Traditions: MT; SP; LXX Canonical source: Markdown Primary anchors: 1876 BC; 1878–1871 BC; 1885–1878 BC; 18766/18756 BC; 1876.6/1875.6 BC; 726–721 BC; late 722 BC ±1; 725–722 BC ±1; 1670/1663/1656 BC; AD 1656/1663/1670; 1936 BC; 1816 BC; 1846 BC; 1661 BC; 1446 BC; 1231 BC; 1016 BC; 966 BC; 586 BC; 2091 BC; 4398–4391 BC; 4396 BC; 4391 BC; 4278–4271 BC; 4825–4818 BC; 4858–4851 BC; 2551 BC; 2336 BC; 3136 BC; 2458/2456 BC; 3058/3056 BC; 2558/2556 BC; 1843/1845 BC; AD 1843/1845; AD 1876/1878; 4106 BC; 5486 BC; AD 1875; 5096 BC; 14006 BC; AD 25; AD 30 Related files: File_00; File_01; File_02; File_04; File_05; File_07; File_08; File_09; File_10; File_11; File_12; File_13; File_14; File_16; File_17; File_18; File_19; File_22; File_26; File_51a; File_51b; File_52a; File_54; File_20; File_59; File_61; File_62; File_64; Restart Capsule v11.30; 490d Repository Style Guide v2.5; Project Procedures v3.5; State Vocabulary Register v1.31; File_65; File_66 Major operators: same-side BC span; civil cross-axis span BC + AD − 1; Protocol 1 Mirror target generation; base-10 inverse-number operator; Rounded inverse axiom; File_26 bounded 10x Nexus rail comparison; 18766 ÷ 10 = 1876.6; 18756 ÷ 10 = 1875.6; 18766 − 18756 = 10; 430; 400; 215; 645; 860; 1260; 1274; 1290; 1335; 1900; 2300; audit-controlled inclusive companion 2307; 2400; 2520; 2730; 2940; 60 × 42; 60 × 40; 60 × 49; 60 × 59; 60 × 99; 60 × 101; 60 × 108; 6 × 490; 3540; 5940; 6060; 6480; 7.5 × 364; 1260 → 1290 → 1260; Samaria Node schematic envelope; 1876 → 726 = 1150; 1871 → 721 = 1150; 726 → 586 = 140; Triple 430; 1876 → 1446 → 1016 = 430 + 430; +50 Jubilee Offset; +60 Terah; +130 regular 2nd Cainan; +460 cumulative 2nd Cainan; ±2; −33; +30 Apparent Age; 25/23; 70/69; 10x scaling; 364 × 3.5; 400 + 1500; 400 + 3900; 990 transfer delta; 9900 cumulative-to-regular bridge; File_64 downstream 430/450/490 opening–joint–closure convergence, Jacob final-70 triple-430 lattice, and uniform 860 Cainan–Judges translation by dependency; File_62 downstream generational male form H→K=7, K→V=33, H→V=40 by dependency Major modal states: 1876 BC shared year-label; bidirectional prophetic span / sundial mirror state; 1878/1876 BC paired target field; File_26 18766/18756 BC Nexus 10x rail comparison state; primary 1446 BC Exodus state; subordinate 1231 BC Ramesside Exodus state; MT 430 Egypt state; SP/LXX 215 + 215 Sojourn-division state; LXX −33 / 33 + 397 family-unit state; Sojourn 215; Exodus 215; Ramesside radius state; +60 Terah; SP-145 Terah state; regular restored 2nd Cainan; cumulative restored 2nd Cainan; 2nd Cainan variant-boundary state; Pentateuchal Funnel / all-even structural harmony state; Cainan death-window state; Cainan / Famine envelope-to-envelope state; cross-tradition 60-multiple Shelah / Plenty-Famine alignment state; Mirror 60-spine / Terah-Cainan death-rail state; regular-Cainan 460-year cross-modal symmetry state; Cainan triple-target matrix state; Cainan-to-Exile Daniel 12 sandwich state; Samaria / Jerusalem twin-city judgment vector state; Samaria Node actual / schematic firewall state; Famine window; Famine Year 1 / Year 2 display states; Affliction start; Triple-430 schematic ledger; historical Temple ledger; File_64 expanded great-/lesser-Nexus synthesis dependency state; File_64 Jacob final-70 / Daniel 1290 closure dependency state; File_64 Cainan–Terah / Judges translated-rail dependency state; localized −33 Mirror state; global −33 exploratory Mirror state; Protocol 1 AD 1875 Mirror target for 1876 BC; MT/LXX deep-time Mirror vector; appendix-only inverse-number state; 990 transfer-delta state; Flood-epoch slash-pair states; Christological bracket; AD 25/30 display field; Daniel Quadruple Lock; four-roads shared-label display state; File_59 Judah 1476 BC → AD 25 = 1500 application state; File_62 male 7+33 hybrid application state Revision basis: 490d Repository Style Guide v2.5; Restart Capsule v11.30; State Vocabulary Register v1.31; Project Procedures v3.5; prior finalized source; corrected Final File_61; Final File_62; Final full post-final pressure-tested File_64 including the July 27 substantive Nexus amendment; Repository_Change_Archive (non-controlling history); July 16 2026 bounded File_59 Judah / ministry-bracket reciprocal pointer; bounded File_62 reciprocal routing (July 2026); bounded File_64 reciprocal routing July 26 2026; bounded expanded File_64 reciprocal routing July 27 2026; Final File_65 and its August 3 2026 reciprocal-control package; State Vocabulary Register v1.36; Restart Capsule v11.35; Repository Change Archive v1.45 (non-controlling history). Current refresh note: Bounded reciprocal routing preserves File_16's existing control basis while recognizing the original File_64 registration at State_Vocabulary_Register v1.34 / Restart Capsule v11.33 and the July 27 amendment's Final-source control status. The expanded File_64 pointer records three downstream uses of File_16-controlled material: the great / lesser frame 1876 → 1446 → 1016 = 430 + 430; the localized-LXX Jacob rail carried through three 430 descents to 606/586/536 BC; and the lower Cainan–Terah 1936/1876/1816 BC rail translated by 860 to 1076/1016/956 BC. These additions create no Category A or Category B Bullseye witness, promote no File_64 coordinate to the File_16 Primary-anchor inventory, and do not alter the historical 966 BC Temple state, Kings +50, File_08's Northern +33, or any File_16 operator. Detailed history remains in Repository_Change_Archive. File_16 remains controlling for the great 1876 BC Nexus, Triple-430 architecture, localized LXX −33 / 33+397 family-unit state, Cainan macro-vectors, and Bullseye inventory; Final File_64 controls its Judges ledgers, Jacob–Daniel synthesis, translated rails, and lesser-Nexus interpretation. The August 3 2026 bounded File_65 pointer adds only the exact reciprocal dependency and non-collapse guard; no Primary anchor, source duration, historical chronology, operator, or existing proof spine changed. Source-history status: Finalized (Version 5.1) Source UUID: ANCHOR_1876_NEXUS

File_16 — The 1876 BC Nexus

Related Repository Files

File_65 reciprocal central-1290 note: Final File_65 correctly restores the regular-MT center 1876 BC → 586 BC = 1290 and treats the localized-LXX 1896 → 606 and 1826 → 536 columns as flanks rather than as the source of the center. Its 130 + 430 + 430 + 130 = 1120 = 16 × 70 outer frame is a corroborative closure around parent-controlled nodes. File_16 retains control of the great 1876 BC Nexus, Triple-430, localized −33, Danielic spans, and Bullseye inventory.

File_59 Judah / ministry-bracket note: File_59 uses the File_16-controlled 1476 BC → AD 25 = 1500 span to translate Judah’s three reverse-total states into 1260/1320/1380 × 360. The exact local landing is at AD 25; AD 30 remains the adjacent permitted Christological endpoint and is not substituted into the same equation. This pointer adds no new Category A road and does not alter the Bullseye Protocol.

File_62 male 7+33 reciprocal note: Final File_62 uses File_16’s localized LXX −33 / 33+397 family-unit state as the second component in declared hybrid comparisons. Its generational form is H→K=7, K→V=33, H→V=40, where H and K are File_61/File_62 half- and full-clutch coordinates and V is a localized −33 comparison coordinate. File_16 remains the controller of the −33 source state and its bounded Terah-through-Levi scope; its displayed Mirror rows remain the Jacob-family subset unless a Terah node is explicitly opened. File_62 controls the cumulative midrail, local date landings, male-birth-law interpretation, and hybrid claim status. The terminal Moses form 1526→1519→1486=7+33=40 is File_62-local and does not use the LXX −33 operator.

File_64 expanded Nexus reciprocal note: Final, full post-final pressure-tested File_64 independently derives the already controlled schematic 1016 BC coordinate from the Book of Judges. Its direct route uses Jephthah's east-/west-Jordan 300/299 field and the post-Jephthah 91; its complementary printed-duration routes total 450 and 490, placing 1016 BC at the closure, joint, and opening of the final Philistine–Samson 40 + 20 module.

File_64 then uses File_16-controlled Nexus and localized-LXX states in two downstream structures:

1896 / 1876 / 1826
  ↓430   ↓430   ↓430
1466 / 1446 / 1396
  ↓430   ↓430   ↓430
1036 / 1016 /  966
  ↓430   ↓430   ↓430
 606 /  586 /  536

Each row preserves 20 + 50 = 70; each full column preserves 1290 = 3 × 430. File_64 also translates the lower Cainan–Terah death rail uniformly:

1936 / 1876 / 1816
  −860   −860   −860
1076 / 1016 /  956.

File_16 remains the controller of the great 1876 BC Genesis Nexus, the localized −33 source state, Cainan macro-vectors, and the literal / schematic Triple-430 firewall. File_64 controls the Judges arithmetic, the Jacob–Daniel literary-theological closure, the translated rails, and the lesser-Nexus interpretation. These pointers add no Category A event-node or Category B pattern-vector witness, do not alter the Kings +50 or File_08's Northern +33, and do not claim direct literary dependence between Genesis 49 and Daniel 12.

File_66 reciprocal third-1290 note: Final File_66 adds a downstream translated third 1290 comparison 1851 BC → 561 BC beside the already controlled 1991→701 and 1876→586 relations, and uses 626 BC in a Jeremiah pre-Fall translation field. These are File_66 structural comparisons. File_16 retains control of the regular-MT 1290, the 1876 BC Nexus, Cainan/Famine states, and Bullseye inventory.

0. File-function

File_16 documents why 1876 BC is designated the Super-Anchor of the 490d Unified Chronology.

The file argues that 1876 BC is:

1. pre-determined by prophecy through 586 BC + 1290;
2. independently confirmed by MT, SP, and LXX trajectory states;
3. valid under both the primary 1446 BC Exodus state and the subordinate 1231 BC Ramesside Exodus state;
4. targeted by both Regular and Cumulative chronological methods;
5. echoed by micro-patterns such as ±2, +30 Apparent Age, localized/global −33, and the Famine window;
6. bracketed at the 10x scale by the File_26 18766/18756 BC Nexus rail comparison;
7. extended by the File_00 Samaria Node twin-city vector, where 1876 BC → 726 BC = 1150 and 1876 BC → 586 BC = 1290 distinguish Samaria and Jerusalem as sister-city judgment nodes;
8. framed downstream by Final File_64 as the great Genesis Nexus standing 430 + 430 years before the lesser 1016 BC Judges–Sanctuary Nexus, with the Exodus at the center;
9. extended downstream by File_64 through Jacob's final 70, three 430 descents to the 606/586/536 BC restoration field, and the Jacob–Daniel last-days closure without adding a Bullseye witness.

The source classifies this convergence as the Bullseye Protocol. The arithmetic base is the state-tagged convergence inventory. The argument layer is structural inference and providential synchronization supporting the file’s theological claim of unified divine authorship across textual transmission.

Publication-cleanup note: This public-clean source preserves the Final, post-final pressure-tested, focused-pressure-tested, and now-current bounded-update labels in the header. Detailed pass logs, bounded update ledgers, pressure-test repetition, and replacement-workflow notes are archived rather than repeated in the public body.

Argument-control result: Arithmetic facts and textual data carry the base layer. Structural inference, Mirror corroboration, statistical / convergence language, and providential synchronization may support the Bullseye Protocol, but they do not replace the arithmetic or dependency controls.

0.1 Working state register

The following states are active in File_16. They are simultaneous, non-competing states unless a local section explicitly narrows the working state.

Modal-state rule: A shared date-label, number, or span does not create identity unless state, node-class, tradition, and operator agree.

0.1A Samaria Node cross-file dependency state

Active state: Samaria / Jerusalem twin-city judgment vector by File_00 dependency.

File_00 now registers the Samaria Node as a schematic envelope 726–721 BC, with the actual historical Fall of Samaria retained as late 722 BC ±1 after a siege beginning about 725 BC. In this dependency state, File_16 contributes the 1876 BC Nexus side of the argument:

1876 BC → 726 BC = 1150
1876 BC → 586 BC = 1290
726 BC → 586 BC = 140 = 2 × 70

Claim-status note: The arithmetic rows are same-side BC arithmetic facts. The twin-city relation is structural inference by File_00 dependency. The claim does not make 726 BC the actual Fall of Samaria and does not change the Jerusalem 586 BC state.

Machine Guard [FILE_16 SAMARIA NODE NEXUS FIREWALL]: When the Samaria Node is cited in File_16, treat it as a File_00 schematic envelope and Nexus extension. Do not make 726 BC an actual fall date, do not use the Samaria Node to correct Northern Kingdom regnal chronology, and do not allow the 1150 Samaria vector to replace the existing 1290 Jerusalem vector.

0.2 File map

0.3 Modal-state processing rules

1. 1876 BC is a shared year-label, not a single event. Identity requires state, node-class, tradition, and operator agreement.
2. The MT 430 Egypt path, SP/LXX 215 + 215 Sojourn-division path, LXX 33 + 397 family-unit path, +60 Terah path, SP-145 path, subordinate Ramesside path, and 2nd Cainan path must remain distinct.
3. The Sojourn 215, Exodus 215, and LXX −33 states answer different questions and must not be merged into one generic adjustment.
4. The subordinate Ramesside path uses 1231 BC as a subordinate Exodus lens and 645-radius midpoint. It must not replace the primary 1446 BC Exodus anchor.
5. The LXX −33 value is textual under the LXX Exodus 12:40 interpretation. The operative scope is now bounded Terah-through-Levi; the Terah extension is methodological/structural, while the Mirror rows in this file remain primarily Jacob-family corroboration. Global Noah/Adam −33 remains exploratory.
6. The LXX 33 + 397 state is a family-unit Sojourn state. It places Jacob’s return from Haran at 1876 BC and Entry into Egypt at 1843 BC; it does not convert MT Entry into 1843 BC.
7. Regular restored 2nd Cainan uses +130; cumulative restored 2nd Cainan uses +460. Do not feed the regular insertion into cumulative death-window arithmetic.
8. The Cainan death-window state preserves EnvNorm 7 as the source’s integer window label. EnvSpread 7.5 remains a phase-resolved dependency state and is not locally activated unless a section explicitly opens that envelope.
9. Slash-pairs such as 3058/3056 BC, 2458/2456 BC, 1843/1845 BC, and AD 1843/1845 are ordered state-pairs, not ranges, averages, or alternatives to be collapsed.
10. The Famine window, 1878–1871 BC, is an envelope with internal event labels. The 1878/1876 BC target-window language must not be reduced to one point.
11. Same-side BC spans use subtraction. Cross-axis civil spans use BC + AD − 1.
12. Mirror target generation, local numeric-year Mirror alignment, civil cross-axis span-counting, 10x scaling, and inverse-number reversal are distinct protocols.
13. The localized −33 Mirror state and global −33 exploratory Mirror state are coherent target-generation states, but neither is File_00 foundational Mirror protocol or Protocol 1 pure rounded A-space Mirror inside this file.
14. The Protocol 1 AD 1875 target is active only in the deep-time Mirror addendum. It is generated by the pure rounded A-space rule for 1876 BC and must not overwrite the localized numeric-year Mirror labels in §4.
15. The Cainan macro-vector material added in this update is B6 substructure. It may clarify the Cainan Category B witness, but it does not add new Category A event-node witnesses and does not alter the core 7 + 6 = 13 inventory.
16. The inclusive 2307 sanctuary / Hanukkah line and the solar 7.5 × 365 comparison are retained as audit-controlled companion notes unless a later file opens the required inclusive-sanctuary or phase-resolved solar operator.
17. The cross-tradition 60-multiple Shelah / Plenty-Famine alignment and its Mirror 3540 = 60 × 59 companion are structural inference / Mirror corroboration / providential synchronization. MT and SP target the Famine window; LXX targets the preceding Plenty window. Do not collapse Plenty with Famine, and do not make the common 60 factor a new operator.
18. The inverse-number addendum is appendix-only inverse corroboration. It is not Mirror protocol, not civil cross-axis arithmetic, and not part of the core 13 counted mechanisms.
19. The historical 966 BC Temple foundation and schematic 1016 BC Triple-430 pivot are dual-ledger states.
20. File_64's 430/450/490 Judges ledgers independently corroborate the schematic 1016 BC coordinate and may name it the lesser Judges–Sanctuary Nexus. They do not add a Category A or Category B witness to File_16, do not rederive the Kings +50, and do not turn the second 430 into a literal elapsed-history claim.
21. AD 25 and AD 30 in the Christological bracket are paired target members, not one collapsed Christological endpoint.
22. The File_00 Samaria Node 726–721 BC is a schematic envelope inside the broader File_16 728–721 BC Famine-window projection. It does not correct the actual Fall of Samaria, and it does not replace the broad window row.

0.4 Machine Guards for File_16

Machine Guard [FILE_16 FILE_66 THIRD-1290 / JEREMIAH NON-BULLSEYE]: Final File_66 may add a downstream third 1290 comparison 1851 BC → 561 BC beside File_16's existing 1991→701 and 1876→586 relations and may use 626 BC in the Jeremiah pre-Fall translation field. These are File_66 structural comparisons, not new File_16 Primary anchors or Bullseye witnesses, and do not redefine the regular-MT 1290, Famine/Exile, or Nexus controls.

Machine Guard [FILE_16 1876 YEAR-LABEL]:

1876 BC is a shared year-label. It may mark Jacob’s Entry under the MT 430 state, Abraham’s Call / Death of Terah under SP-215 or +60 Terah, Jacob’s return from Haran under the LXX −33 / 33 + 397 state, a subordinate Ramesside convergence point, or a Cainan death-window target under the cumulative-to-regular Cainan field. These are related convergence witnesses, not one collapsed event.

Machine Guard [FILE_16 SOJOURN / EXODUS / −33 FIREWALL]:

The Sojourn 215, Exodus 215, and LXX −33 states answer different questions. The Sojourn 215 concerns the Canaan/Egypt division under the primary 1446 BC Exodus anchor. The Exodus 215 concerns the subordinate 1231 BC Ramesside state. The LXX −33 concerns the family-unit interval from Jacob’s return from Haran to Jacob’s Entry. Do not combine them as one adjustment field.

Machine Guard [FILE_16 RAMESSES NON-REPLACEMENT]:

1231 BC is a subordinate Ramesside Exodus state. It is valid for the local convergence path and the 645-year radius, but it must not replace the primary 1446 BC Exodus anchor.

Machine Guard [FILE_16 RAMESSES NODE-CLASS SPLIT]:

In the subordinate Ramesside convergence path, 1231 BC is the Exodus node, 1661 BC is the Entry node, and 1876 BC is the Call of Abraham / Death of Terah node. In the Ramesside radius table, 1876 BC may function as the Prophetic Bondage Cycle start / Super-Anchor. These are related uses of the year-label, not one event.

Machine Guard [FILE_16 LXX 33 + 397]:

The LXX 33 + 397 reading is a family-unit Sojourn interpretation. It places Jacob’s return from Haran at 1876 BC and Jacob’s Entry into Egypt at 1843 BC. Do not collapse this with the MT 430-Egypt state, where Jacob’s Entry itself is 1876 BC.

Machine Guard [FILE_16 FILE_62 MALE 7+33 HYBRID]:

Final File_62 may combine File_61/File_62 half-clutch and full-clutch coordinates with File_16’s localized −33 family-unit comparison to display H→K=7, K→V=33, H→V=40. This is a declared cross-modal hybrid. Do not promote File_62’s H7/T14 coordinates into File_16 Primary anchors; do not present the hybrid as one MT, LXX, SP, or cumulative continuous chronology; do not extend the localized −33 beyond its declared bounded Terah-through-Levi scope without a controlling derivation; do not convert the resulting 7+33=40 into a new Category A/B Nexus witness; and do not collapse the terminal Moses form 1526→1519→1486 with the generational localized-−33 form.

Machine Guard [FILE_16 CAINAN REGULAR / CUMULATIVE]:

Regular restored 2nd Cainan uses +130. Cumulative restored 2nd Cainan uses +460. These are related Cainan states, not interchangeable operators. Any source wording that compresses cumulative Cainan and +130 remains a dependency-review issue unless the local calculation explicitly supplies the active Cainan state.

Machine Guard [FILE_16 2ND CAINAN VARIANT-PROPAGATION]:

When the restored 2nd Cainan regular variant is opened by File_18 / File_00 controls, 2nd Cainan itself has four possible dates, like Terah. The eight-date field begins with Arphaxad and propagates backward to Adam. Do not use File_16's Cainan death-window or regular +130 switch to assign eight possible dates to 2nd Cainan itself.

Machine Guard [FILE_16 CAINAN DEATH-WINDOW]:

The Cainan death-window state preserves the source integer window as EnvNorm 7. EnvSpread 7.5 remains a phase-resolved dependency state where the Aaron/Moses L = 3.5 or Nisan/Tishri spread is active. Do not introduce EnvSpread arithmetic into Cainan rows unless the active section explicitly opens that phase-resolved state.

Machine Guard [FILE_16 CAINAN MACRO-VECTOR B6]:

The Cainan / Famine 2520 envelope projection, regular-Cainan 460 same-side lifespan symmetry, Daniel 8 2300 vector, Enochian 2730 lower-bound vector, and Daniel 12 Cainan-to-Exile sandwich are Category B macro-vector substructure under B6. They do not become additional Category A event nodes, and they do not change the core 7 + 6 = 13 inventory unless a later author decision changes the inventory.

Machine Guard [FILE_16 SHELAH 60-MULTIPLE ALIGNMENT]:

The MT, SP, and LXX Shelah-envelope comparisons use same-side BC subtraction and multiples of 60. MT and SP target the Famine window; LXX targets the preceding seven years of Plenty. This state is structural inference / providential synchronization only. Do not promote it to a new operator, do not collapse Plenty with Famine, do not convert it into a Category A event-node witness, and do not collapse it with the direct +60 Terah state merely because the value 60 is shared.

Machine Guard [FILE_16 MIRROR 60-SPINE / DEATH-RAIL]:

The Mirror 3540 = 60 × 59 companion is valid only under explicit civil cross-axis display and reversed endpoint order: 1885n BC ↔ AD 1656n, 1878n BC ↔ AD 1663n, and 1871n BC ↔ AD 1670n. Same-order pairing of 1885/1878/1871 BC with AD 1670/1663/1656 does not yield a constant 3540. The Terah / Cainan death rail 1936n BC → 1876n BC → 1816n BC is a death-date variant rail only; it does not identify Terah and Cainan as the same node-class and does not create a new Category A witness.

Machine Guard [FILE_16 CAINAN INCLUSIVE / SOLAR AUDIT]:

The inclusive 2307 sanctuary / Hanukkah line and the solar 7.5 × 365 comparison are retained as exploratory or audit-controlled companion notes. Their same-side integer checks may be displayed, but this file does not open a new exact phase-resolved solar operator through them.

Machine Guard [FILE_16 SAMARIA NODE DEPENDENCY]: File_16 may state the 1876 BC → 726 BC = 1150 and 1876 BC → 586 BC = 1290 twin-city vector as a downstream expression of the 1876 BC Nexus. It must not use the File_00 Samaria Node to correct the actual Fall of Samaria, to replace the broad Famine-window projection 1878–1871 BC → 728–721 BC, or to turn 726 BC into a forced historical fall date. 726 BC is the File_00 schematic onset / collapse label; 721 BC is the terminal / latest-fall label.

Machine Guard [FILE_16 MIRROR / CIVIL FIREWALL]:

Mirror target generation and civil cross-axis span-counting are distinct. All cross-axis span counts use BC + AD − 1. In this file, the localized −33 Mirror rows function as Mirror corroboration for already defined textual / modal states. The global −33 rows function as an exploratory Mirror note. Neither replaces the local textual derivation of −33 or the Shem ±2 datum.

Machine Guard [FILE_16 FILE_19 SUNDIAL MIRROR]:

File_19 uses bidirectional language because the Dial of Ahaz narrative turns the shadow backward. In File_16, this is classified as Bidirectional Prophetic Span / Sundial Mirror. It is not Protocol 1 pure rounded A-space Mirror, not local numeric-year Mirror alignment, not civil cross-axis span-counting, not 10x Mirror scaling, and not inverse-number reversal unless a local section explicitly opens one of those protocols.

Machine Guard [FILE_16 FAMINE WINDOW]:

1878–1871 BC is a Famine-window envelope. It contains multiple internal event labels, including Year 1, Year 2, Entry-related claims, and 1876 BC as Super-Anchor. Do not treat the window as a single date.

Machine Guard [FILE_16 FILE_26 18766/18756 NEXUS RAIL]: The 18766/18756 BC display is a File_26 dependency-controlled 10x Nexus rail comparison. It brackets the 1876 BC Nexus through 18766 ÷ 10 = 1876.6 and 18756 ÷ 10 = 1875.6. It is not a new Category A event-node witness, not formal Protocol 1 Mirror, not inverse-number reversal, and not ordinary civil cross-axis arithmetic.

Machine Guard [FILE_16 CATEGORY A/B FIREWALL]:

Category A rows are direct event-node witnesses. Category B rows are pattern-vector witnesses. Both may support the Bullseye Protocol, but a Category B vector does not become a Category A event merely because it lands on 1876 BC or the Famine window.

Machine Guard [FILE_16 TRIPLE 430 DUAL LEDGER]:

The first 430 in 1876 → 1446 is literal under Exodus 12:40. The 1446 → 1016 and 1016 → 586 spans use the schematic 1016 BC pivot generated through the +50 Jubilee Offset from the historical 966 BC Temple foundation. The schematic pivot must not overwrite the historical anchor.

Machine Guard [FILE_16 FILE_64 GREAT / LESSER NEXUS NON-COLLAPSE]:

Final File_64 may identify 1016 BC as the lesser Judges–Sanctuary Nexus and may corroborate it through the Judges 430/450/490 ledgers. It may also apply File_16-controlled 1876 BC, localized −33, 1290, and Cainan/Terah states in its Jacob final-70 lattice, Jacob–Daniel closure, and translated 60 + 60 rails. File_16 remains controlling for the great 1876 BC Nexus, the 1876 → 1446 → 1016 = 430 + 430 frame, the Triple-430 literal / schematic firewall, the localized −33 source state, Cainan macro-vectors, and the Bullseye inventory. Do not import File_64's Judges rows, Jacob/Daniel synthesis, Cainan–Terah translations, Northern +33, paired 930, or Flood corroboration into the File_16 Category A/B count; do not claim that File_64 derives the Kings +50; do not make 1016 BC the historical Temple foundation; do not convert the schematic 430 blocks into uninterrupted literal history; and do not claim direct literary dependence between Genesis 49 and Daniel 12.

Machine Guard [FILE_16 SLASH-PAIR / WINDOW SAFETY]:

Slash-pairs such as 3058/3056 BC, 2458/2456 BC, 1843/1845 BC, AD 1843/1845, and AD 1876/1878 are ordered state-pairs. They are not ranges, averages, or loose alternatives. Famine windows and Daniel windows are envelopes. Compute or classify each member component-wise when cross-axis or same-side arithmetic is later verified.

Machine Guard [FILE_16 LOCAL MIRROR LABELS]:

The localized and global −33 Mirror sections use source-defined numeric-year Mirror target labels such as 1843 BC ↔ AD 1843 and 1876 BC ↔ AD 1876. These are local Mirror target alignments generated by the section’s span logic. They are not automatically Protocol 1 pure rounded A-space mirrors, where n BC normally mirrors as AD (n − 1). The civil span count remains BC + AD − 1 after the target label is supplied.

Machine Guard [FILE_16 PROTOCOL 1 DEEP-TIME MIRROR]:

The AD 1875 target is the Protocol 1 pure rounded A-space Mirror of 1876 BC. It is valid only where the active section opens the rounded deep-time Mirror field. It must not overwrite the localized numeric-year Mirror labels used in the −33 sections, where 1843 BC ↔ AD 1843 and 1876 BC ↔ AD 1876 function as local target labels. Civil span-counting remains BC + AD − 1 in both cases.

Machine Guard [FILE_16 INVERSE APPENDIX-ONLY]:

The 2230 → 3220, 5096 BC, 9200, 10000, and 990 transfer-delta material is appendix-only inverse corroboration. It is a derived transformation controlled by File_52a; it is not a Mirror protocol and must not carry the main Bullseye Protocol argument unless a future inverse-focused file promotes it.

Machine Guard [FILE_16 CHRISTOLOGICAL BRACKET]:

1876 BC → AD 25 and 1871 BC → AD 30 are paired Christological bracket members. The first belongs to the ministry target; the second belongs to the famine-completion / death target. Do not collapse AD 25/30 into one date or make either endpoint replace the other.

Machine Guard [FILE_16 FILE_65 CENTRAL-1290 / OUTER-FRAME NON-COLLAPSE]: Final File_65 correctly identifies 1876 BC → 586 BC = 1290 as the regular-MT central Triple-430 route and may place the localized-LXX flanks at 1896 → 606 and 1826 → 536. It may also display 2006 → 1876 → 1446 → 1016 → 886n BC = 130 + 430 + 430 + 130 = 1120 = 16 × 70. File_16 remains controlling for the great 1876 BC Nexus, Triple-430, localized −33, 1260/1290/1335, and Bullseye inventory. Do not count the File_65 outer frame as a new Bullseye category, convert 886n BC into a Primary anchor, or collapse the literal first 430 with the schematic later 430s.

0.5 Terminology controls

0.6 Arithmetic-control summary

Arithmetic-control result retained in Final source: The explicit same-side BC spans, civil cross-axis spans, factorization checks, 645 radius, Cainan 2520 / 2300 targets, localized/global −33 Mirror component checks, Christological 1900 bracket, Shem Death Lock, and Daniel Quadruple Lock check under their stated operators.

Arithmetic repair applied: Two source-retained same-side BC forward-duration displays in §5.2.6 were normalized from +430 wording to subtraction form:

2091 − 430 = 1661
1876 − 430 = 1446

The intended MT/SP 215 / 430 subset relation is unchanged.

Arithmetic repair applied: The source line 3 manuscript traditions × 2 Exodus dates × 2 methods = 13 potential trajectories was separated into two arithmetic statements:

3 × 2 × 2 = 12 baseline combinatorial slots
7 + 6 = 13 classified mechanisms

This preserves the source’s 13+ inventory language while correcting the displayed product and applying the final Category A / Category B classification. The prior raw 8 + 6 = 14 source-inventory display is retained only as source-history, not as the active classified count. Appendix B adds three dependency-controlled deep-time extension vectors without altering the core inventory count.

0.7 Claim-status register for File_16

0.8 Argument-control summary

File_16 argues by layering chronology data, arithmetic facts, structural inference, Mirror corroboration, statistical / convergence language, and theological interpretation.

Argument-control result: The file’s strongest local claim is structural convergence: multiple state-controlled textual and arithmetic witnesses land on 1876 BC or the 1878/1876 BC target-window. The theological claim of unified divine authorship is preserved as providential synchronization. Broad probability language is not treated as a formal statistical result inside File_16 unless a future dependency supplies the model.

1. The prophetic origin: the target comes first

1.1 The 586 BC fixed point

Active state: Exile fixed-point state.

The Fall of Jerusalem at 586 BC is the fixed point from which this file measures the main prophetic span.

Historical verification retained from source: Babylonian Chronicle BM 21946; Egyptian synchronisms; 2 Kings 25:8–9, Av 7–10, 586 BC.

Claim-status note: The historical fixed-point claim is source-retained chronology data. Full external historical corroboration is outside this pass.

1.2 The 1290-year backward span

Active state: Daniel 12:11 backward span from the Exile.

Source: Daniel 12:11, “From the time the daily sacrifice is abolished and the abomination that causes desolation is set up, there will be 1290 days/years.”

Calculation retained from source:

586 + 1290 = 1876 BC

Claim-status note: The arithmetic fact is 586 + 1290 = 1876 BC. The statement that prophecy prescribes the target before the genealogies confirm it is a structural inference drawn from the Daniel 12:11 reading and the subsequent convergence inventory.

1.3 The Triple 430 equivalence with 1290

Active state: Triple-430 prophetic ledger.

The 1290-year span decomposes into three cycles of Ezekiel’s 430-year “Iniquity of Israel/Judah” span (Ezekiel 4:4–6).

Arithmetic verification retained from source:

430 + 430 + 430 = 1290

Cross-reference retained from source: The Triple 430 pattern is structurally mirrored in the 2521 BC Priestly Expansion (see File_22, §5D), which creates a 430 + 215 + 430 chiasm targeting the 1876 BC Nexus.

1.4 The three 430s: literal vs schematic

Active state: Triple-430 dual-ledger state.

The 1016 BC pivot is derived from 966 BC, the historical Temple foundation, through the +50 Jubilee Offset. Both spans touching 1016 BC are therefore schematic. They depend on a derived anchor rather than on explicit biblical duration statements.

Terminology:

1.4A File_64: the lesser Judges–Sanctuary Nexus

Final, post-final pressure-tested File_64 supplies a downstream independent derivation of the schematic 1016 BC coordinate from the Book of Judges. Its simplest route is:

1446 → 1406 = 40
1406 → 1107 = 299
1107 → 1016 = 91

40 + 299 + 91 = 430.

Its complete printed-duration ledgers then place the same coordinate at all three boundaries of the final Philistine–Samson 40 + 20 module:

File_64 therefore names 1016 BC the lesser Judges–Sanctuary Nexus and frames it against File_16's great Genesis Nexus:

1876 BC ──430── 1446 BC ──430── 1016 BC

The first 430 remains the literal MT Sojourn state. The second remains schematic. File_64's independent landing strengthens the endpoint but does not replace the File_08 Kings derivation, does not generate the +50 operator, and does not add another Category A or Category B witness to the File_16 Bullseye inventory.

The July 27 File_64 amendment then carries a localized-LXX Jacob 20 + 50 = 70 rail through the same Nexus field:

1896 / 1876 / 1826
  ↓430   ↓430   ↓430
1466 / 1446 / 1396
  ↓430   ↓430   ↓430
1036 / 1016 /  966
  ↓430   ↓430   ↓430
 606 /  586 /  536

The rows preserve Jacob's final 70; the columns preserve 1290 = 3 × 430. The terminal comparison joins Jacob's Genesis 49 declaration concerning the latter days to Daniel 12's 1290/1335, rest, and allotted inheritance. File_64 classifies this as literary-theological and providential synthesis, not proof of direct literary dependence.

File_64 also carries the lower Cainan–Terah death rail into the Judges field:

1936 / 1876 / 1816
  −860   −860   −860
1076 / 1016 /  956.

This is a downstream uniform translation of File_16 / File_18 dependency states. It does not create new File_16 Bullseye witnesses, identify Cainan and Terah as one node-class, or convert the translated Judges labels into historical royal dates.

1.5 The +50 Jubilee Offset

Active state: Kings dual-ledger state.

The source states that the verbatim sum of the Kings of Judah exceeds the actual history by approximately 50 years, one Jubilee cycle.

Source-retained explanation: This 50-year offset arises from co-regencies, accession-year reckoning differences, and inclusive counting conventions in the source texts. The verbatim total is retained as a schematic ledger rather than treated as an error. The claim that the historical data approximates this template is a structural inference controlled by the Kings dependency.

Why the Triple 430 remains usable in the source argument:

1. 1290 years decomposes into 3 × 430.
2. This creates three equal watches from Bondage to Exile.
3. The Jubilee Offset, +50, embeds one liberation cycle in the transition from Judges to Kingdom.
4. The historical 966 BC and schematic 1016 BC are both valid anchors for different purposes.

Application:

Cross-reference retained from source: Data Verification: File_18, §2.5, Kings of Judah table with Verbatim vs Actual columns and +50 derivation.

1.6 Theological synthesis

Theological note: Ezekiel’s siege-symbol, 430 days as 430 years, and Daniel’s abomination-count, 1290 days as 1290 years, are treated as synonymous when the Triple-430 structure is recognized. In the source interpretation, the Babylonian Exile completes what the Egyptian Sojourn began; both are bondage under the same prophetic template.

2. Variant convergence: multiple trajectories, single target

2.1 MT path: 430 years in Egypt

Active state: MT 430 Egypt state.

Source: Exodus 12:40, MT: “Now the sojourning of the children of Israel, who dwelt in Egypt, was four hundred and thirty years.”

Node-class: 1876 BC = Jacob’s Entry into Egypt / Beginning of Sojourn (Genesis 46:6) under the MT 430 Egypt state.

2.2 SP-215 path: 215 years Canaan + 215 years Egypt

Active state: SP-215 / Sojourn-215 state.

Source: Exodus 12:40, SP: “Now the sojourning of the children of Israel and their fathers, who dwelt in Canaan and in Egypt, was four hundred and thirty years.”

Arithmetic retained from source:

215 + 215 = 430

Node-class: 1876 BC = Abraham’s Call (Genesis 12:1–4) / Death of Terah (Acts 7:4) under the SP-215 / Sojourn-215 state.

2.3 LXX 33 + 397 path

Active state: LXX −33 / 33 + 397 state.

Controlling precedent: File_04 treats this as the fourth direct chronological fork in the broader File_16 convergence inventory.

Node-class: 1876 BC = Jacob’s return from Haran under the LXX −33 / 33 + 397 family-unit state. 1843 BC = Jacob’s Entry into Egypt under the same state.

State note: This path does not replace the MT 430 Egypt state. It supplies a distinct LXX family-unit node landing on the same shared 1876 BC year-label. In this state, 1876 BC is Jacob’s return from Haran and 1843 BC is Jacob’s Entry. In the MT state, 1876 BC remains Jacob’s Entry.

2.4 Subordinate Ramesside path: subordinate Exodus + composite Sojourn

Active state: Subordinate Ramesside Exodus state.

The Ramesside Exodus at 1231 BC is retained as a subordinate historical reconstruction. It still yields 1876 BC.

Node-class note: Within the subordinate Ramesside path, 1661 BC is the Entry node and 1876 BC is the Call / Death-of-Terah node. In the Ramesside radius geometry (§2.6), 1876 BC functions as the MT Bondage-cycle origin imported into the geometric comparison. These are coordinated states, not one Ramesside Entry event.

Structural inference retained from source: Whether one adopts the primary 1446 BC Exodus state or the subordinate 1231 BC Ramesside state, the system preserves 1876 BC as the covenantal anchor.

Theological note: The source classifies this as the Providence Protocol in action: the timeline breathes to accommodate historical variance while maintaining the divine pattern.

State-control note: The subordinate Ramesside path does not replace the primary 1446 BC Exodus state.

2.5 Summary convergence table

All four framework rows converge on the same 1876 BC year-label despite different assumptions. The convergence is year-label convergence, not event identity.

2.6 The 645-year radius: resolution of the Ramesside paradox

2.6.1 The issue

Critics note that no single manuscript creates a 645-year interval between the Entry and the Exodus. The MT allows 430 years; the LXX/SP allow 215 years. A 645-year span, 215 + 430, appears textually baseless if one looks for a single verse citation.

2.6.2 The resolution

The source resolves this through a Dual-Lock system. The 645-year span is presented as the convergence of textual-geography pressure from Exodus 1:11 and geometric structure from Daniel 12:11. It functions as the radius of the Prophetic Bondage Cycle inside the subordinate Ramesside state.

2.6.3 Dual-lock corroboration

Active state: Subordinate Ramesside state.

The date 1231 BC is retained as the coordinate that, in the source argument, satisfies both the textual-geography pressure of the Torah and the schematic symmetry of the Prophets.

Textual anchor: Exodus 1:11 states that the Israelites built “Pithom and Raamses” as store cities for Pharaoh.

Modal-state handling: Within the subordinate Ramesside textual-geography state, Exodus 1:11 supplies pressure toward a 13th-century Ramesside setting, aligning the narrative geography with the 19th Dynasty / Ramesses II field in the source argument.

Source-history note: The legacy wording says this effectively rules out the 15th-century 1446 BC timeline. Current repository controls classify 1231 BC as subordinate and non-replacement. The active revised state therefore preserves the Ramesside textual-geography claim while preventing it from replacing the primary 1446 BC Exodus anchor.

Geometric corroboration: While Exodus 1:11 supplies the Ramesside textual-geography pressure in the source argument, the Unified Chronology algorithm selects 1231 BC as the bisector of the 1290-year Prophetic Bondage Cycle. This is a structural inference inside the subordinate Ramesside state, not a replacement of the primary 1446 BC anchor.

2.6.4 Arithmetic derivation: the bisector

1290 ÷ 2 = 645

Forward radius:

1876 − 645 = 1231 BC

Backward radius:

586 + 645 = 1231 BC

Composite verification:

430 + 215 = 645

Claim-status note: The source classifies 1231 BC as the Ramesside Radius. The 645-year bisector is an arithmetic fact. The claim that this satisfies the “Raamses” textual citation is a structural inference within the subordinate Ramesside state.

State-control note: The phrase “center of the Bondage Era” belongs to the subordinate Ramesside geometry. It does not redefine the MT Entry node or replace the primary 1446 BC Exodus anchor. The 645 value is a geometric radius between the Super-Anchor and the Ramesside fulcrum, not a manuscript-stated Entry-to-Exodus duration.

2A. The four-roads display on the 1876 BC label (bounded addition)

Active state: four-roads shared-label display state.

Four traditions, four distinct events, one year-label — each hanging its own 430-family span from the same numeral. This display consolidates three already-registered convergence states and adds the SOR Covenant member; the event-states remain distinct under the 1876 BC shared year-label state (do not collapse), and the Bullseye Protocol inventory (§6) is unchanged by this display — elevation of the SOR member into the inventory is deferred to a later author pass if desired.

Claim-status: arithmetic fact (each span within its own frame); structural convergence / providential synchronization (the four-fold coincidence of the label); dependency-controlled (File_20; File_04).

Cross-file corroboration pointer (bounded addition): File_20 §8A records an inverse witness on this label: BJ / Jubilees' principal internal contradiction — the Isaac +11 displacement — lays out four Isaac coordinates whose nested envelopes center exactly on 1876 BC (= AM 1981). Classification: holographic corroboration, controlled by File_20; not a fifth road and not a Category A member; the Bullseye Protocol inventory (§6) is unchanged.

3. The Cainan mechanism: the cumulative-to-regular gear

3.1 Function of the section

This section documents the source’s mathematical bridge between the Cumulative Chronology and the Regular Chronology by showing how the 2nd Cainan’s lifespan is interpreted as encoding the Sojourn constant.

Terminology-control note: Regular restored 2nd Cainan uses +130; cumulative restored 2nd Cainan uses +460. The source’s Cainan material should be read with that distinction active.

State-control note: This section contains three related but distinct Cainan states: regular insertion +130, cumulative lifespan insertion +460, and cumulative death-window projection into Regular History. The death-window projection may target 1876 BC or 2091 BC without making Cainan’s cumulative death itself occur in Regular History.

3.2 Source: cumulative 2nd Cainan’s death

Active state: Cumulative restored 2nd Cainan.

From the Cumulative MT + 2nd Cainan tables (File_09; external reference retained in source):

Source note retained: The 7-year death window of Cainan, 4398–4391 BC, results from the three-year Aaron/Moses gap, ±1.5 years each direction, combined with the ±2-year Shem anomaly.

2 + 3 + 2 = 7

Modal-state note: File_04 and Restart Capsule v11.15 require EnvNorm / EnvSpread awareness. The source’s integer 7 is preserved here as EnvNorm. EnvSpread 7.5 remains a phase-resolved dependency state and is not introduced as executable arithmetic in File_16 unless a later section explicitly opens that envelope.

3.3 The 2520 and 2300 spans

Active state: Cumulative Cainan death-window to Regular History.

Node-class note: 4396 BC and 4391 BC are selected members of the Cainan death-window state. They are used as source-window targets for 2520 and 2300 spans; they do not collapse the full 4398–4391 BC window.

Arithmetic verification retained from source:

4396 − 2520 = 1876
4391 − 2300 = 2091

Prophetic significance retained:

2520 = 7 × 360 = 1260 + 1260

2300 = Temple Restoration cycle, Daniel 8:14

Theological note: The source reads the Week of Death, Cainan’s seven-year death window, as the chronological prototype for the Week of Famine, Joseph’s seven years, 1878–1871 BC. The First Sinner’s end targets the Covenant’s beginning.

3.3A Cainan / Famine envelope-to-envelope projection

Active state: Cumulative Cainan death-window to Famine-window projection.

Claim-status: Macro-prophetic witness; Category B pattern-vector substructure under B6.

The 2520 span is now stated in both point and envelope form. The point form preserves the existing B6 core calculation, while the envelope form shows how the cumulative Cainan / Shelah boundary projects into the Famine window without collapsing either envelope.

Arithmetic verification:

4398 − 2520 = 1878
4396 − 2520 = 1876
4391 − 2520 = 1871

Modal-state note: The cumulative envelope 4398–4391 BC remains a Cainan / Shelah boundary state. The historical envelope 1878–1871 BC remains a Famine-window state. Their 2520 relation is a macro-structural bridge, not a claim that the cumulative Cainan death-window is the literal Famine event.

3.3A.1 Cross-tradition 60-multiple Shelah / Plenty-Famine alignment

Active state: Cross-tradition cumulative Shelah envelope comparison; MT, SP, and LXX kept distinct.

Claim-status: Structural inference; providential synchronization where theological reading is invoked.

The MT Cumulative + 2nd Cainan Shelah envelope projects to the Famine window by 2520 = 60 × 42. In the same comparative register, the SP Shelah envelope projects to the Famine window by 2400 = 60 × 40, while the LXX Shelah envelope projects to the preceding seven years of Plenty by 2940 = 60 × 49 = 6 × 490.

Arithmetic verification:

4398 − 2520 = 1878
4391 − 2520 = 1871
2520 = 60 × 42

4278 − 2400 = 1878
4271 − 2400 = 1871
2400 = 60 × 40

4825 − 2940 = 1885
4818 − 2940 = 1878
2940 = 60 × 49 = 6 × 490

State-control note: The common divisibility by 60 is collaborative evidence of design alignment around the cumulative Shelah / Arphaxad-Cainan boundary and Joseph's Plenty/Famine field. It is not a new operator by itself. The +60 Terah state may be noted as a related 1876 BC intersection, but it remains a direct chronological fork and must not be collapsed with the cumulative Shelah envelope vectors.

3.3A.2 Mirror 60-spine and Terah / Cainan death rail

Active state: Mirror corroboration for the cross-tradition 60-multiple Shelah alignment; Nisan-state display labels active.

Claim-status: Structural inference; Mirror corroboration; providential synchronization where theological reading is invoked.

The Plenty / Famine triad 1885n/1878n/1871n BC has a −215 companion triad 1670n/1663n/1656n BC.

Same-side companion relation:

1885 − 215 = 1670
1878 − 215 = 1663
1871 − 215 = 1656

When the −215 companion triad is placed on the AD side in reversed endpoint order, the civil cross-axis Mirror component is constant:

Audit note: The constant 3540 requires reversed endpoint order on the AD side. Same-order pairing of 1885/1878/1871 BC with AD 1670/1663/1656 does not produce 3540 in all three rows.

The same 60-multiple base then combines with the three Shelah-vector spans:

The LXX result is the standard precessional quarter in the repository's 25920 register:

6480 = 60 × 108
6480 = 25920 ÷ 4

This strengthens the earlier 60-multiple observation without creating a new operator. The evidence is collaborative because the Mirror base 60 × 59, the SP 60 × 40, the MT 60 × 42, and the LXX 60 × 49 all remain whole 60-multiples while the historical targets remain state-controlled as Plenty or Famine.

The same 60 register also helps explain the death-date rail around the 1876n BC Nexus. In the minimum Sojourn field, Terah and regular restored 2nd Cainan share 1876n BC as a possible death-date label, while their adjacent companion labels flank the Nexus by one 60-year unit:

State-control note: The 1936n BC → 1876n BC → 1816n BC display is a death-date variant rail. It does not identify Terah and Cainan as the same node-class. It states that both death-date fields share the 1876n BC node while the adjacent companion dates lie one 60 unit on either side.

3.3B The 460-year cross-modal symmetry

Active state: Regular restored 2nd Cainan, compared with cumulative restored 2nd Cainan.

The cumulative operator is +460. The regular restored 2nd Cainan operator remains +130 for insertion, but the figure's regular lifespan may still be measured as a same-side 460-year span. This creates a cross-modal symmetry without exchanging operators.

State-control note: The 460 value may mirror the cumulative lifespan insertion, but this does not convert regular restored 2nd Cainan into a cumulative table operator. It is a same-side regular lifespan span used as Category B corroboration.

3.3C Triple-target Cainan matrix

Active state: Cumulative Cainan macro-vector state; regular restored 2nd Cainan comparison; EnvSpread opened only for the Enochian line.

The Cainan macro-vector targets three state-controlled historical boundary labels. These are not three new counted mechanisms. They are sub-vectors inside B6.

Arithmetic verification:

4851 − 2300 = 2551
4391 − 2300 = 2091
4396 − 2520 = 1876
4391 − 2730 = 1661
2730 = 7.5 × 364

Theological note: The source reads this as a triple-target matrix: Daniel 8 2300 targets the 2091 BC Abraham / Cainan boundary; Daniel 9-style 2520 targets the 1876 BC Super-Anchor; the Enochian 2730 vector targets the 1661 BC lower-bound Entry state. This is preserved as providential synchronization where the theological meaning is invoked.

3.3D Inclusive and solar companion notes

Active state: Audit-controlled companion material.

The pasted source also supplies an inclusive sanctuary / Hanukkah-style 2307 line and a solar 7.5 × 365 comparison. The same-side integer checks are retained, but the operators are not promoted to core File_16 proof in this patch.

Audit note: The 2307 and solar companion lines are retained because they may be useful for a later sanctuary-calendar or phase-resolved solar file. They are not inserted into the core Category B inventory and do not alter the B6 count.

3.4 The begetting-age variable

Active state: 2nd Cainan begetting-age switch.

State note: This subsection uses Cainan's lifespan and begetting-age variable inside the Cainan mechanism. It must not be confused with the regular restored 2nd Cainan +130 insertion or the cumulative restored 2nd Cainan +460 insertion, even though the same figure and the value 130 appear.

The chronological switch lies in how old 2nd Cainan was when he fathered Shelah.

Remaining-years calculation:

The 430 as genealogical constant: Eber lives 464 years, begets Peleg at 34 years, and has 430 remaining years.

464 − 34 = 430

The source treats this as a structural inference that 430 functions as a post-Flood genealogical constant.

3.5 The Terah-Cainan parallel

Active state: Terah / Cainan covenantal death comparison, with Cainan dependency control.

The source compares Terah and 2nd Cainan as covenantal death witnesses, but by different mechanisms. Terah’s death alignment is locally textual / harmonized; Cainan’s alignment remains dependency-controlled through the cumulative-to-regular death-window mechanism.

Cross-verification retained from source: Terah’s death date is explicitly linked to Abraham’s Call through Genesis 11:32–12:1. The SP achieves this by setting Terah’s lifespan at 145 years; the MT achieves it by placing Abraham’s birth at Terah’s 130th year, 70 + 60.

Theological note: The source reads Cainan, the First Sinner of the post-Flood era, and Terah, the Father of Idolatry in Joshua 24:2, as death-witnesses coordinated with covenant initiation. Death yields to Promise. Curse yields to Blessing. The theological reading is preserved, but Cainan’s full chronological mechanism remains dependency-controlled.

3.6 The LXX/SP 130 chain

Active state: LXX/SP death-to-death chain.

While the cumulative MT + Cainan path targets 1876 BC / 2091 BC through the 2520 / 2300 spans, the LXX and SP maintain Abraham as the terminus through multiples of 130.

The 130-year significance retained from source:

• Adam begets Seth at 130 years, Genesis 5:3.
• The number 130 marks the propagation of the cursed / mortal lineage.
• Multiples of 130 appear throughout LXX/SP begetting ages where MT has 30.
• The 130-Year Curse is referenced in File_00 and File_11.

3.7 Structural comparison

Theological note: The source reads the LXX and SP as tracing the chain of fallen humanity from Arphaxad’s immediate descendant to Abraham’s death through the Curse Harmonic, multiples of 130. The MT + Cainan path traces prophetic redemption through Daniel’s sanctuary numbers, 2300 and 2520. Different schematics keep Abraham in focus.

Argument-status note: All three traditions keep Abraham in focus in the source argument. The MT uses prophetic numbers; the LXX and SP use genealogical constants. The claim that this convergence is structurally embedded is a structural inference, not a separate arithmetic fact.

4. Micro-pattern echoes: fractals within the anchor

4.1 Year 2 of Famine: the Shem echo

Active state: Famine window and Shem ±2 echo.

Window-state note: This subsection uses the Famine-window display state. Year 1 / Year 2 labels, Entry language, and the 1878/1876 BC target-window must not be collapsed into one exact date during arithmetic verification.

Jacob enters Egypt in Year 2 of the seven-year famine (Genesis 45:6: “For these two years the famine has been in the land”).

Derivation of the ±2: Genesis 11:10 states that Shem was 100 years old and became the father of Arphaxad two years after the Flood. This creates the ambiguity of whether Shem was 100 at the Flood and 102 at Arphaxad’s birth, or 98 at the Flood and 100 at Arphaxad’s birth.

Structural inference: Jacob’s Entry in Year 2 of the famine is read as replicating the ±2 pattern. The Sojourn anchor is therefore treated as echoing the same flexibility as the Flood anchor.

Arithmetic note: The window arithmetic checks as:

1878 − 1871 = 7
1878 − 1876 = 2

Claim-status note: Genesis 45:6 supplies the textual marker, “these two years.” The arithmetic 1878 − 1876 = 2 is retained as target-window arithmetic. The revised argument does not collapse the Famine window into one exact ordinal-year claim.

4.2 The +30 Bondage Shift: the Adam echo

Active state: +30 Apparent Age / Sojourn-to-Affliction offset.

The 400 / 430 distinction:

Arithmetic retained from source:

430 − 30 = 400

Theological note: The source reads Adam’s +30 as maturity before the curse takes effect and the Sojourn +30 as Israel’s neutral presence before active affliction begins. The +30 marks the transition from neutral presence to active curse in both cases.

4.3 The localized variant Mirror: ±2 and −33 corroboration

Mirror role note: This section contains Mirror material in a non-Mirror file. Cross-axis span counts use BC + AD − 1. The localized −33 Mirror rows are classified as Mirror corroboration because they stress-test textual states already established by Genesis 11:10 and the LXX 33 + 397 Sojourn reading. The global −33 rows are classified as an Exploratory Mirror note because they are coherent but not tracked in standard tables.

Author scope clarification (September 2026): repository-wide localized −33 now includes Terah as the upstream hinge, while remaining bounded before Noah/Shem. This section does not reinterpret its existing Mirror rows as Terah biography rows. File_60 controls the detailed Terah states 2296→2091, 2236→2031, 2203→1998 and the qualified composite 2263→2058; File_00 controls the scope rule.

Two chronological variants are treated as native baselines within their respective epochs. The local numeric-year Mirror corroborates their architectural coherence by connecting them across time.

4.3.1 The two localized variants

Methodological note retained: The former Abraham–Levi-only shorthand is superseded. The operative −33 scope is bounded Terah-through-Levi; the Terah step is structural/methodological, not an additional claim about the wording of Exodus 12:40.

4.3.2 The −33 position dates: localized application

Under the LXX 33 + 397 interpretation, the Sojourn dates shift by 33 years.

Window-state note: The famine labels in this table are internal Famine-window members. They must not be used to overwrite the broader 1878–1871 BC envelope or the 1878/1876 BC target-window language.

Arithmetic / window note:

1878 − 1845 = 33
1877 − 1844 = 33
1876 − 1843 = 33
1878 − 1876 = 2
1845 − 1843 = 2

The 1878–1876 BC and 1845–1843 BC labels are target-window endpoint forms. They are not converted into ordinary inclusive ordinal counts.

4.3.3 Flood-epoch dates: +215 position with ±2

Slash-pair note: The following pairs are ordered ±2 state-pairs, not ranges to be averaged or collapsed. Each member must be handled component-wise when paired with an AD target.

4.3.4 Mirror convergence: localized −33 target

The local numeric-year Mirror connects the Flood-epoch dates to the −33 Sojourn position.

Local Mirror-state note: The AD target labels AD 1843/1845 are source-defined local Mirror target labels generated by the −33 Sojourn field and the stated span families. They are not automatically Protocol 1 pure rounded mirrors. The span count is civil and component-wise after the AD target labels are supplied. Claim-status: Mirror corroboration.

Arithmetic verification retained from source:

3058 + 1843 − 1 = 4900
3056 + 1845 − 1 = 4900
2458 + 1843 − 1 = 4300
2456 + 1845 − 1 = 4300
2558 + 1843 − 1 = 4400
2556 + 1845 − 1 = 4400

4.3.5 Mirror target alignment

The Flood-epoch dates project through 4900, 4400, and 4300-year spans to land on the AD mirror of the −33 Sojourn dates.

Joseph echo retained:

4400 = 110 × 40

Theological note: Joseph preserves the family; Shem carries the blessing. The 110-year signature connects them across the Mirror.

4.3.6 The −33 as globally additive: unexplored permutation

Active state: Global −33 exploratory state.

Node-class note: This is an Exploratory Mirror note. It may show coherent Mirror alignment, but it does not become the standard repository table state and does not replace the bounded Terah-through-Levi −33 state.

The bounded Terah-through-Levi scope is a methodological/structural selection, not an arithmetic impossibility theorem. There is no inherent arithmetic reason −33 cannot be applied additively all the way back to Noah or Adam, but such global use remains exploratory.

If −33 is applied globally to the Flood epoch:

These shifted dates produce the following Mirror patterns:

Arithmetic verification:

3058 − 33 = 3025
3056 − 33 = 3023
2458 − 33 = 2425
2456 − 33 = 2423
3025 + 1876 − 1 = 4900
3023 + 1878 − 1 = 4900
2425 + 1876 − 1 = 4300
2423 + 1878 − 1 = 4300

Key observation retained:

Both produce coherent Mirror alignments. The −33 works whether localized or global; it targets different valid anchors.

Why localize: The source localizes for human comprehension and AI processing efficiency. The standard repository tables adopt:

Advanced analysis may explore the full permutation space, but standard tables do not track −33 as globally additive.

Cross-reference retained: File_00, §3.7, The −33 Variant: Nature and Scope.

4.3.7 Argument-status conclusion

The source treats ±2 and −33 as:

AI processing note retained:

• ±2 and −33 are baseline features, not additive variants like +60 / +215.
• Standard repository scope is bounded Terah-through-Levi; this file’s displayed Mirror arithmetic remains the Jacob-family subset unless Terah is explicitly opened.
• AI systems may model −33 as globally additive; results remain structurally coherent.
• The fact that both localizations produce valid patterns is preserved as Mirror corroboration for the local case and as an Exploratory Mirror note for the global case.

Cross-reference retained: File_00, localized baseline variants; File_04, LXX 33 + 397 interpretation; File_02, Shem ±2 anomaly; File_18, §1.5, Shem ±2 local variant.

4.3.8 File_62 male 7+33 downstream application

Dependency state: Final File_62 applies the localized −33 family-unit state to a separate cumulative–regular half-clutch field controlled by corrected File_61 and File_62.

For the generational form, define:

H = half-clutch coordinate
K = full-clutch coordinate
V = K − 33

Then:

H − K = 7
K − V = 33
H − V = 40

The principal downstream rows are:

Arithmetic:

2073 − 2066 = 7
2066 − 2033 = 33
2073 − 2033 = 40

1926 − 1919 = 7
1919 − 1886 = 33
1926 − 1886 = 40

1789 − 1782 = 7
1782 − 1749 = 33
1789 − 1749 = 40

State and claim-status control:

• File_16 controls the localized LXX −33 / 33+397 family-unit operator.
• Corrected File_61 and Final File_62 control H7, T14, the cumulative coordinates, and the meaningful regular landings.
• The combined rows are declared hybrid MT-cumulative / MT-regular / localized-LXX comparisons. They are not one manuscript’s continuous chronology.
• The arithmetic is exact. Applying the male-child 7+33=40 purification grammar is structural / typological, with Jubilees providing explicit ancient hermeneutical precedent by File_62 dependency.
• These rows add no Category A or Category B road to the Bullseye Protocol.

The terminal Moses form remains separate:

1526 → 1519 → 1486 = 7 + 33 = 40

Its final 33 is the fixed half-clutch-midpoint-to-Midian span, not an application of the LXX −33 operator.

4.4 File_26 10x Nexus rail: 18766/18756 BC

Active state: File_26 18766/18756 BC Nexus 10x rail comparison state.

Dependency note: File_26 controls the full derivation of the 18766/18756 BC rail inside the Nangishlishma / Balih / precessional-season and Pillar extension field. File_16 registers only the way this rail interfaces with the 1876 BC Nexus.

The local Nexus display is:

18766 ÷ 10 = 1876.6
18756 ÷ 10 = 1875.6
18766 − 18756 = 10

Structural inference: The pair 18766/18756 BC brackets the 1876 BC Nexus at the 10x scale. It therefore extends File_16's existing 10x Nexus vocabulary without creating a new direct convergence fork.

Claim-status note: The arithmetic rows are dependency-controlled arithmetic facts from File_26. Their use inside File_16 is structural inference / providential synchronization, not a new Category A event-node witness and not a new Mirror protocol.

5. Prophetic and Christological spans

5.1 Dual prophetic spans: 1260 and 1290 from Bondage

Active state: Sojourn-start / Affliction-start paired-span state.

The 30-year offset between 1876 BC, Sojourn, and 1846 BC, Affliction, generates paired prophetic spans to both the Exodus and the Exile.

5.1.1 From 1846 BC, Affliction start

Arithmetic verification retained from source:

1846 − 400 = 1446
1846 − 1260 = 586

5.1.2 From 1876 BC, Sojourn start

Arithmetic verification retained from source:

1876 − 430 = 1446
1876 − 1290 = 586

5.1.3 Prophetic equivalence table

The 30-year Apparent Age offset propagates through the system:

430 = 400 + 30
1290 = 1260 + 30

Structural inference: The source reads these paired spans as linking Creation, Adam +30; Sojourn, Entry +30 to Affliction; and prophecy, 1260 + 30 = 1290.

5.1.4 The Daniel 12 pair in context

Daniel 12:11–12 states: from the time the daily sacrifice is abolished, there will be 1290 days; blessed is the one who waits and reaches 1335 days.

Arithmetic verification:

1876 − 1335 = 541
1846 − 1335 = 511

The 1290 and 1260 are not alternatives. They are parallel tracks from two Sojourn anchors, 1876 BC Entry and 1846 BC Affliction, both terminating at 586 BC.

5.2 Christological criterion: the 4300 / 1900 chiastic lock

Active state: Christological cross-axis bracket.

Node-class note: AD 25 and AD 30 are paired target members: ministry beginning and death / crucifixion target. They are not one collapsed Christological endpoint.

In the source argument, 1876 BC qualifies as a Super-Anchor when genealogical convergence and prophetic targeting are supplemented by a Messianic span. The arithmetic supplies the base layer; the Christological reading is a structural and theological inference.

5.2.1 Ezekiel 4 reversal pattern

Ezekiel 4:4–6 prescribes sin-bearing spans.

The Christological spans reverse this order and scale by 10x.

5.2.2 Chiastic lock: Creation ↔ 1876 BC

Cross-embedding retained:

• Creation projects through MT’s number, 4300, but embeds LXX’s 190 as an internal subset.
• 1876 BC projects through LXX’s number, 1900, but embeds MT’s 215 / 430 as an internal subset.

Claim-status note: The reciprocal embedding is an arithmetic / structural relation under the stated dependencies. The claim that it supports paired-anchor design is preserved as a structural inference, not as an arithmetic fact.

5.2.3 The 1876 BC → Christ arithmetic

Same-side and cross-axis arithmetic note:

1876 − 1476 = 400
1476 + 25 − 1 = 1500
1876 + 25 − 1 = 1900

Alternate endpoint via famine completion:

Bracket-state note: The 1871 BC → AD 30 row uses the famine-completion endpoint. It is paired with, not a replacement for, the 1876 BC → AD 25 ministry row.

Cross-axis arithmetic note:

1871 + 30 − 1 = 1900

5.2.4 The five-year bracket: 10x Solar/Lunar Straddle

Both anchors exhibit a five-year flex window targeting Christ.

Structural requirement retained:

0.5 × 10 = 5 years

The five-year bracket is treated in the source as structurally required to maintain proportional coherence with the underlying 0.5-year Solar/Lunar Straddle at 10x scale. This is a structural inference controlled by the Solar/Lunar Straddle dependency.

Cross-reference retained: File_00; File_12, §2.

5.2.5 Ministry bracket

5.2.6 Internal subsets explained

At Creation, 4300 span: The LXX’s 190 appears as the Menorah Arms pattern, 60 + 70 + 60, doubled. This 190 is embedded within the MT-derived 4300 span.

Cross-reference retained: File_07, §8B.

At 1876 BC, 1900 span: The MT’s 215 / 430 appears as the Sojourn variants.

2091 BC − 430 = 1661 BC
1876 BC − 430 = 1446 BC
1876 BC − 215 = 1661 BC

Arithmetic-control note: The legacy +430 forward-duration display has been normalized to same-side BC subtraction. This does not change the intended relation: the 2091 BC Abraham Call state, the 1876 BC Super-Anchor state, and the 1661 BC Entry / Sojourn comparison node preserve the MT/SP 215 / 430 subset relation.

5.2.7 Theological significance

Theological note: The source treats the chiastic lock as Christological corroboration of 1876 BC, giving it a direct arithmetic trajectory to Christ’s ministry, not merely to Old Testament events.

Claim-status note: The displayed 1900-year spans are arithmetic facts under civil cross-axis counting. The claim that Creation and 1876 BC are structurally paired is a structural inference. The claim that MT and LXX are complementary witnesses is a theological / providential reading built on the arithmetic and manuscript-state controls. Altering either anchor would disrupt the displayed chiastic relation; this is a local structural claim, not a global derivation by itself.

Christological criterion retained, with paired endpoints stated component-wise:

1876 BC → AD 25 = 1900 years
1871 BC → AD 30 = 1900 years

Cross-reference retained: Prophetic Overlay: File_07; Scaling Logic: File_00; Technical Definition: File_12, §2; Messianic Data: File_13.

6. Convergence inventory: the Bullseye Protocol

6.1 Convergence classification

Active state: Bullseye Protocol classification.

The source classifies the mechanisms targeting 1876 BC into two categories. The Final source preserves the source material but tightens claim-status: Category A must remain direct event-node evidence, and Category B must remain pattern-vector evidence.

Enumeration result in the Final source: The source heading said “7 trajectories” for Category A, while the raw inventory displayed eight Category A rows because Cainan appeared both as a direct row and as a Cumulative-to-Regular pattern vector. The Final source classifies the Cainan mechanism only as a Category B vector unless a controlling Cainan file later supplies a direct death-at-1876 event-node state.

Category A: A1–A7 = 7 direct event-node rows
Category B core: B1–B6 = 6 indirect pattern-vector rows
Core counted inventory = 13 rows
Appendix B extension: B7–B9 = 3 dependency-controlled deep-time pattern-vector rows
Expanded inventory when Appendix B is active = 16 rows

The source’s 13+ language remains valid as an inclusive convergence-inventory label. The arithmetic product is 3 × 2 × 2 = 12; the core counted inventory is 7 + 6 = 13 rows after preventing the Cainan mechanism from being counted twice. Appendix B adds B7–B9 as dependency-controlled deep-time extension vectors and should be cited only when the File_51b / File_52a layer is active.

Claim-status note: The inventory count is an arithmetic fact. The Bullseye Protocol is a structural inference from the inventory. Broad probability or design language remains statistical / convergence rhetoric unless a defined probability model is supplied by File_10 or another dependency.

6.2 Category A: direct chronological forks

Definition: These trajectories place an actual event, death, Entry, Call, return, or Famine marker directly at 1876 BC or 1878 BC through a textual reading or manuscript variant. The date 1876/1878 BC is itself a biographical or narrative node in the chronological chain.

Characteristic: A manuscript reading, interpretive variant, or explicit narrative marker creates a fork where 1876/1878 BC is the date or target-window of a biographical or historical event.

Note on A7, Year 2 of Famine: Genesis 45:6 states that two years of famine had already passed. The file preserves this as a direct narrative marker inside the Famine sequence. Because the arithmetic also uses the 1878/1876 BC target-window, A7 should be read as a Famine-window event-node witness, not as a collapsed single-day ordinal claim.

Note on SP-145: The Samaritan Pentateuch lists Terah’s lifespan as 145 years. This native reading places Terah’s death at 1876 BC without requiring the +60 Terah harmonic adjustment used in the MT.

Argument-control classification of Cainan: The former Category A Cainan row is retained in the file’s argument as B6, not deleted. Under the revised modal-state controls, the visible Cainan arithmetic is a cumulative-to-regular target vector using cumulative +460, selected death-window nodes, and the 2520 / 2300 spans. That is Category B logic. This reclassification avoids double counting the same Cainan mechanism as both a direct event-node fork and a pattern-vector witness.

6.3 Category B: indirect pattern connections

Definition: These trajectories connect to 1876 BC or the 1878–1871 BC Famine window through prophetic spans, cycles, or harmonic multiples. The connection is mathematical rather than biographical; a calculated span points to 1876 BC from another anchor.

Characteristic: A prophetic number or harmonic span points to 1876 BC from another chronological anchor. The connection supports the source inference that 1876 BC is structurally central, but it does not place an event biography at that date.

Note on B1: 586 BC + 1290 is the Prophetic Origin. The target is supplied by Daniel 12:11 in the source argument before the Category A trajectories converge on it.

Note on B2: The LXX death of Shem, 2738/2736 BC under the source’s +215 / +275 variant positions, connects to 1878/1876 BC through 860 years, 430 + 430. This extends to 1290 years to 1448/1446 BC, Exodus, and 2150 years to 588–586 BC, siege / Exile.

Note on B6: The Cainan row remains dependency-controlled. 4396 BC is a selected cumulative death-window member; it targets 1876 BC through 2520. The expanded B6 substructure also preserves 4391 BC → 2091 BC = 2300, regular-Cainan 460 lifespan symmetry, and 4391 BC → 1661 BC = 2730 where the Enochian EnvSpread state is active. These are Cainan macro-vector subclaims, not additional Category A event-node forks and not additions to the core inventory count.

6.4 Distinction for AI processing

Classification logic:

Processing rules:

1. Both categories may support the Bullseye Protocol.
2. Category A supports textual / manuscript convergence.
3. Category B supports prophetic / structural convergence.
4. The categories operate on different axes, textual and mathematical.
5. Mutual convergence on 1876 BC from both axes is treated in the source as statistically notable, but this file supplies no formal probability model.

Probability assessment:

Claim-status note: The source interprets the combined convergence as structural design rather than coincidence. In this revised file, that statement is classified as structural inference and providential synchronization, not as a quantified statistical result.

The 1878–1876 BC window: The ±2 creates a target-window field, not a single-point anchor. This window language encompasses Famine Year 2, Jacob’s Entry, Abraham’s Call, Death of Terah, and the Cainan death-window target as state-tagged convergence claims. The window replicates the Shem ±2 at the Flood pivot.

6.5 Complete convergence inventory

The following table preserves the revised core counted inventory in compact form. Appendix B supplies the optional deep-time extension B7–B9 under dependency control.

Core inventory cross-reference retained: Derivation Logic: File_04, LXX 33 + 397; Axiom Definition: File_00, Structural Variators; Messianic criterion: §5.2.

Appendix B extension note: B7–B9 are not inserted into the core 13 count because they depend on the later rounded deep-time Mirror and inverse-number layer. They may be cited as Category B extension vectors where File_51b and File_52a are active.

6.6 The Shem Death Lock

Active state: Shem ±2 and Famine-window convergence.

The death of Shem in the LXX state, 2738/2736 BC, connects to 1878/1876 BC through 860 years, 430 + 430. The +60 Terah state, 2798/2796 BC, connects to the same target-window through 920 years, 460 + 460.

This links the two-year anomaly at Shem with Year 2 of the famine when Israel entered Egypt.

The source extends this:

Arithmetic verification:

2738 − 860 = 1878
2736 − 860 = 1876
2738 − 1290 = 1448
2736 − 1290 = 1446
2738 − 2150 = 588
2736 − 2150 = 586
2798 − 920 = 1878
2796 − 920 = 1876
920 × 25/23 = 1000

Claim-status note: The arithmetic checks. The claim that the Shem anomaly and Famine-window alignment are intentionally linked is a structural inference within the source argument.

6.7 Logical priority: target before trajectories

Critical framing retained as structural inference:

1. 586 BC is historically fixed in the source frame.
2. Daniel 12:11 supplies 1290 years.
3. Therefore 1876 BC is generated as the target within the source’s prophetic logic.
4. The genealogies are then read as converging on this pre-existing target from multiple directions.

The trajectories come from:

• MT, SP, and LXX;
• the primary 1446 BC Exodus state and subordinate 1231 BC Ramesside state;
• Regular and Cumulative methods;
• the deaths of Terah and the Cainan target-vector;
• micro-pattern echoes such as Year 2 and the +30 offset.

Source term retained: This is the Bullseye Protocol in the source argument: the target exists independently of the trajectories; the trajectories’ convergence on the target supplies the structural evidence.

6.8 Probability claim-status

Source-retained inventory frame, corrected arithmetically:

3 manuscript traditions × 2 Exodus-date states × 2 methods = 12 baseline combinatorial slots

Final counted inventory after argument classification:

7 Category A rows + 6 core Category B rows = 13 counted mechanisms
Appendix B extension: 3 additional dependency-controlled Category B vectors

Arithmetic note: The source’s 13+ language is preserved as an inclusive convergence-inventory label. It should not be read as the exact product of 3 × 2 × 2. The exact product is 12. The argument-classified core inventory is 13 rows after the Cainan duplicate is classified only as a Category B vector. The deep-time Appendix B extension raises the dependency-controlled expanded inventory to 16 only when the File_51b / File_52a layer is active.

Additional source-retained claims:

• Each trajectory has many possible landing points across the 4000-year span.
• Micro-patterns such as ±2 and +30 could fall elsewhere.

Claim-status note: The broad probability claim remains unquantified in this file. It is classified as statistical / convergence rhetoric and structural inference unless a later statistical dependency supplies a defined probability model.

6.9 Theological conclusion

Theological note: The source concludes that the 1876 BC Nexus supports the interpretation that chronological variants across MT, SP, and LXX are not merely scribal errors, textual corruptions, or competing traditions. They are interpreted as complementary witnesses, multiple lines of sight to the same covenantal bullseye.

Theological / providential conclusion retained: All converge on 1876 BC, supporting the source’s theological claim of unified divine authorship across manuscript transmission, chronological method, and historical reconstruction. The chronological system is described as antifragile: apparent contradictions are interpreted as strengthening the pattern rather than breaking it.

Claim-status note: The divine-authorship conclusion is preserved as theological interpretation and providential synchronization. It is supported by arithmetic and state-controlled convergence but does not replace the arithmetic base.

7. Daniel Quadruple Lock: Famine → Exile projection

7.1 Function of the lock

Active state: Famine-window to Exile / Return mapping.

Window-state note: All rows in this section are window-to-window projections from 1878–1871 BC. Destination windows such as 728–721 BC and 543–536 BC remain envelopes. They are not converted into inclusive counts or single-point anchors in this file.

The seven-year famine, 1878–1871 BC, brought Israel into Egypt and contains the 1876 BC Nexus as an internal focal member. The source projects this window forward through Daniel’s prophetic numbers to target Israel’s later judgment and restoration arc.

Samaria Node dependency note: File_00 now controls a narrower Samaria Node schematic envelope inside this broader 728–721 BC window. The File_16 row 1878–1871 BC → 728–721 BC remains the full famine-window projection. When the active state is narrowed to Jacob's Entry and the remaining five years of famine, the 1876–1871 BC sub-envelope projects to the 726–721 BC Samaria Node:

1876 − 1150 = 726
1871 − 1150 = 721

In that File_00 state, 726 BC is the idealized siege / collapse label for Samaria and 721 BC is the terminal / latest-fall label. The actual Fall of Samaria remains late 722 BC ±1 and is not corrected by either schematic endpoint.

Arithmetic note: 1878 − 1871 = 7. No exact midpoint claim is made by the revised wording.

7.2 Four prophetic spans

7.3 Arithmetic verification

7.4 Seven-year bracket mapping

7.5 The 1274 = Enochian 1260

The 1274-year span represents the Enochian, 364-day calendar, equivalent of the prophetic 1260.

The source states that this targets the exile of the prophets Daniel and Ezekiel, who received the visions containing these numbers.

7.6 Theological significance

Theological note: The famine that brought Israel into Egypt, bondage, projects through Daniel’s numbers to the complete judgment cycle.

Structural / theological note: The source treats the 1876 BC Nexus, as an internal focal member of the Famine window, as prophetically linked to Israel’s exilic experience. The bondage-to-redemption pattern established at Joseph’s famine is read as repeating at the Babylonian captivity. This is a structural inference and theological reading built on the window arithmetic.

Cross-reference retained: Schematic Parallel: File_08, Triple 430 to 586 BC; Biblical Authority: Daniel 8:14; Daniel 12:11–12; 2 Kings 17; 2 Kings 25; Ezra 1.

7.7 Cainan-to-Exile Daniel 12 sandwich

Active state: Cumulative Cainan core member; Affliction-start state; Exile fixed-point state.

This subsection records the pasted-source observation that 4396 BC, 1846 BC, 1876 BC, and 586 BC form a Daniel 12 macro-prophetic chain. It belongs to Category B macro-prophetic witness logic, not to Category A event-node logic.

Arithmetic verification:

1260 + 1290 + 1260 = 3810
4396 − 3810 = 586
1876 − 1290 = 586
1876 − 1846 = 30
1846 − 1446 = 400
1876 − 1446 = 430

Node-class note: 1876 BC and 1846 BC are coordinated but distinct. In the MT 430 state, 1876 BC is Jacob's Entry / Sojourn start. In the Affliction state, 1846 BC is the Genesis 15:13 / 400-year Bondage origin. The 30-year separation is a structural offset and does not collapse Entry into Affliction.

Theological note: The source reads the 1876 BC → 586 BC line as an Egypt-to-Exile cycle: Israel enters Egypt under famine in 1876 BC, and the later remnant returns toward Egypt and Babylonian exile at the 586 BC catastrophe. This meaning is preserved as typological / theological support. The arithmetic remains the burden-bearing layer.

8. Cross-reference index

Appendix A. Arithmetic verification table

Appendix note: This table preserves the source arithmetic ledger in Markdown form with verification and claim-status notes. Rows marked checks have been verified under the stated operator. Rows marked factorization checks; dependency-controlled target preserve correct arithmetic while retaining external provenance for the named death-chain or source-row target.

Appendix B. Deep-time Mirror and inverse extension

Appendix-status note: This appendix records dependency-controlled Category B extension vectors supplied by the rounded deep-time Mirror and inverse-number layer. These rows do not alter the core 7 + 6 = 13 inventory in §6. They extend Category B only when File_51b and File_52a are active.

Active state: Protocol 1 Mirror target for the pure rounded 1876 BC Super-Anchor, plus appendix-only inverse-number corroboration from the 4106 BC → 1876 BC rounded span.

B.1 Protocol 1 target for 1876 BC

Protocol 1 Mirror target generation:

1876 BC → AD 1875

Civil-span rule: After the Mirror target is generated, cross-axis spans still use the civil formula:

BC + AD − 1

Machine-control note: This Protocol 1 target is not the same node-class as the localized numeric-year Mirror labels in §4. Localized −33 may use labels such as 1843 BC ↔ AD 1843; the Protocol 1 rounded target for 1876 BC is AD 1875.

B.2 Category B extension table

B.3 Arithmetic verification

MT rounded deep-time vector:

4106 + 1875 − 1 = 5980
5980 = 13 × 460

LXX rounded deep-time vector:

5486 + 1875 − 1 = 7360
7360 = 16 × 460
7360 = 23 × 320
5980 + 1380 = 7360
1380 = 3 × 460

Inverse-number vector:

4106 − 1876 = 2230
2230 → 3220
3220 = 23 × 140
1876 + 3220 = 5096 BC
5980 + 3220 = 9200
9200 = 4 × 2300
9200 × 25/23 = 10000

Transfer-delta note:

3220 − 2230 = 990
14006 − 4106 = 9900 = 10 × 990
14006 − 5096 = 8910 = 9 × 990

Claim-status note: The 990 transfer-delta is arithmetically valid and structurally suggestive because it places the 1876 BC inverse displacement at one-tenth of the rounded cumulative-to-regular Creation bridge. Its status in this file is appendix-only inverse corroboration. It should not carry the main Bullseye Protocol argument.

B.4 Argument-control note

The deep-time Mirror vectors B7 and B8 show that the Protocol 1 Mirror target of 1876 BC, namely AD 1875, receives both the MT rounded Creation state and the LXX rounded Creation state through 460-based multiples. The LXX vector differs from the MT vector by 1380 = 3 × 460, preserving the known MT/LXX rounded Creation differential.

The inverse vector B9 subjects the same-side span 4106 BC → 1876 BC = 2230 to the File_52a inverse-number operator. This yields 3220, which relocates the Creation pole to 5096 BC when reapplied from 1876 BC. The resulting 9200 total expands by 25/23 to 10000.

Argument-control rule: These three extension rows strengthen the deep-time corroborative field around 1876 BC, but they do not replace the textual, prophetic, and chronological mechanisms that establish the core File_16 inventory.

Audit notes

Audit note [FILE_16 2307 / SOLAR COMPANIONS]: The 2307 inclusive companion and the solar 7.5 × 365 comparison remain exploratory / audit-controlled companion notes. They are not promoted as active File_16 operators.

Audit note [FILE_16 SHELAH / PLENTY-FAMINE AND MIRROR 60-SPINE]: The cross-tradition 60-multiple Shelah / Plenty-Famine alignment and the Mirror 60-spine remain structural inference / Mirror corroboration / providential synchronization. MT and SP target the Famine window; LXX targets the preceding Plenty window. Do not collapse Plenty with Famine, and do not convert the shared 60 factor into a new operator.

Dependency note [FILE_16 FILE_26 NEXUS RAIL]: The 18766/18756 BC 10x Nexus rail comparison is dependency-controlled by File_26. It brackets the 1876 BC Nexus at the 10x scale and is not a new Category A event-node witness, formal Mirror protocol, inverse-number reversal, or ordinary civil cross-axis operator in File_16.

Dependency note [FILE_16 SAMARIA NODE]: The Samaria Node twin-city vector remains controlled by File_00 for actual / schematic firewalling. File_16 preserves the Nexus relation 1876 BC → 726 BC = 1150, 1876 BC → 586 BC = 1290, and 726 BC → 586 BC = 140 = 2 × 70.

Dependency note [FILE_16 FILE_62 MALE 7+33]: Final File_62 uses the File_16 localized −33 family-unit state only as a declared downstream component in the generational rows 2073→2066→2033, 1926→1919→1886, and 1789→1782→1749. Corrected File_61 and File_62 control the half/full-clutch coordinates, regular node identities, and male-birth-law interpretation. File_16’s Nexus proof, Bullseye inventory, and Primary anchors remain unchanged; only the standard −33 scope pointer is broadened one generation upstream to Terah.

Dependency note [FILE_16 FILE_64 EXPANDED NEXUS SYNTHESIS]: Final, full post-final pressure-tested File_64 independently derives the schematic 1016 BC endpoint through the Judges 430/450/490 duration-ledger routes and uses the label lesser Judges–Sanctuary Nexus. Its July 27 amendment then applies File_16-controlled 1876 BC, localized −33, 1290, and Cainan/Terah states in the Jacob final-70 triple-430 lattice, the Genesis 49 / Daniel 12 literary-theological closure, and the uniform 1936/1876/1816 → 1076/1016/956 translation. File_16 remains controlling for the great Nexus, source states, Triple-430 literal / schematic distinction, Cainan macro-vectors, and Bullseye inventory. The pointer adds no Category A/B witness, alters no historical 966 BC Temple state, does not rederive the Kings +50 or Northern +33, and does not establish direct literary dependence.

Unresolved issues

No local source blocker remains. The 2307 inclusive companion and solar comparison remain audit-controlled; later bounded update caution labels remain preserved in the file header.

Revision and archive note

This public-clean Markdown source removes only archival amendment history, pass logs, pressure-test repetition, pointer-refresh records, and obsolete replacement-workflow notes.

Detailed revision history is preserved in the Repository_Change_Archive.

No pre-existing File_16 arithmetic, Primary anchors, source states, node-classes, sign conventions, operator definitions, slash-pairs, ranges, envelopes, Mirror protocols, claim-status labels, theological claims, Bullseye inventory, or dependency boundaries are changed. The previously applied File_62 and original File_64 guards remain; this bounded update expands only the File_64 dependency description, reciprocal note, state row, arithmetic audit row, §1.4A synthesis, and the existing great-/lesser-Nexus non-collapse guard.

Final pressure-test status is preserved in the file header. Detailed pressure-test records are archived rather than repeated in the public file body.

August 3 2026 File_65 reciprocal-control update

• Added Final File_65 as a bounded reciprocal dependency.
• Added the exact non-collapse Machine Guard registered at State Vocabulary Register v1.36 §D.29.
• Routed current control pointers through Restart Capsule v11.35 and Repository Change Archive v1.45.
• Changed no pre-existing arithmetic, Primary anchor, source duration, operator, historical chronology, or dependency boundary.
• Focused replacement checks performed; no new full pressure test.