File: File_24 Title: The First Dynasty of Kish Cipher: The En-tarah-ana Bridge and the 23-Kings Arrangement Status: Final; post-final pressure tested; File_26 companion dependency update applied and focused pressure tested during trust-status equalization; File_34 post-final citation-control update applied and focused pressure tested June 3 2026; sampled post-equalization pressure test complete Publication-cleanup status: Public-clean Markdown source; archival amendment history routed to Repository_Change_Archive. Pressure-test status: Current; sampled post-equalization pressure test complete for the First Dynasty of Kish 23-kings table, hidden-50 partition, SKL Short / Long rail-pair controls, File_21 / File_34 source-boundary routing, File_26 companion bridge states, biblical-interplay examples, and public-clean metadata; prior post-final, File_26 companion, and File_34 citation-control pressure-test results retained. Register Agreement status: Checked against State_Vocabulary_Register v1.17 and active companion controls; convergence / pointer update only; no arithmetic, anchors, modal states, node-classes, operators, sign conventions, slash-pairs, ranges, envelopes, Mirror protocols, Machine Guards, claim-status labels, theological claims, or dependency boundaries changed. Replacement status: Full replacement-ready Markdown file for bounded File_26 cross-file audit update Primary domain: SKL; Comparative; Prophetic; Theological Traditions: SKL; Hebrew Bible; MT; Danielic / prophetic by dependency; SP / LXX by background witness reference only Canonical source: Markdown Primary anchors: 262086 BC; 27366/27396 BC; 20886/20916 BC; 20888/20918 BC; 20886 BC; 20916 BC; 27366 BC; 27396 BC; 20888 BC; 20918 BC; 18726 BC; 18766/18756 BC by File_26 dependency; 18600; 1200; 432000; 19800; 2160; 2150 by File_26 dependency; 670; 50; 720; 241200; 17286 BC; 3600; 14400; 18000; 259200; 17980; 24510; 18030; 93.5 days; 2936/2906/2886 BC; 2906/2936 BC; 2856/2886 BC; 10136/10086 BC; 10750; 10800; 7200; 6480; 8640 by File_26 dependency; 8600 by File_26 dependency; 90; 30; 20; 25920; 25800 by File_26 dependency; 15536/15486 BC; 14696/14646 BC; 12600; 11760; 16800; 336; 490; 18056/18086 BC; 18058/18088 BC; 18006 BC; 17636/17638/17666/17668 BC; 17586 BC; 900; 625; 324; 1849; 30; 25; 18; 43; 2166 BC; 1526 BC; 1496 BC; 1446 BC; 6 BC; 966 BC; 1016 BC; 480; 1956/1958 BC; 16560; 1656; 16100; 18000; 19440; 1440; 2300; 270; 72; 71⅔ Related files: File_00; File_01; File_02; File_05; File_08; File_12; File_13; File_16; File_17; File_18; File_19; File_21; File_23; File_26; File_34; File_51a; File_54; Restart Capsule v11.15; State Vocabulary Register v1.17; 490d Repository Style Guide v2.5; Project Procedures v3.2 Major operators: same-side BC subtraction; SKL `360:1` scalar; SKL first-three-kings elapsed offset; `1200 × 360`; `18600 + 1200`; `1200 + 960`; hidden `50`-year drop; `670 × 360`; `50 × 360`; `(670 + 50) × 360`; `670 + 30 + 20 = 720`; `420 + 300`; `1200 + 960 + 670 + 50 + 420 + 300 = 3600`; `20886 − 17286 = 3600 = 60 × 60`; `17286 − 2886 = 14400 = 120 × 120`; `3600 + 14400 = 18000`; `20886 − 10136 = 10750 = 150 × 71⅔`; `20886 − 10086 = 10800 = 150 × 72 = 30 × 360`; `10136 − 2936 = 7200 = 20 × 360`; `10086 − 2886 = 7200 = 20 × 360`; `2936 − 2906 = 30`; `2906 − 2886 = 20`; `20916 − 2936 = 17980`; `20886 − 2906 = 17980`; `27396 − 2886 = 24510`; `27366 − 2856 = 24510`; `27366 − 20886 = 6480 = 18 × 360 = 90 × 72`; `27396 − 20916 = 6480`; perfect-square display `900 = 30^2`; `625 = 25^2`; `324 = 18^2`; `900 + 625 + 324 = 1849 = 43^2`; SKL `+30` / one-month straddle display; SKL `+2 local rail`; Kings dual-ledger `+50`; 1 Kings 6:1 `480`-year Temple-to-Exodus count; `966 + 480 = 1446`; `1016 + 480 = 1496`; `18726 − 16560 = 2166`; `18056 − 16560 = 1496`; `18006 − 16560 = 1446`; `46 × 360 = 16560`; `10 × 1656`; `20886 − 1446 = 19440 = 270 × 72`; `16560 × 25/23 = 18000`; `18000 − 16560 = 1440`; `1446 − 6 = 1440`; `18006 − 6 = 18000`; `7 × 2300`; SKL fractional-tail source-control; `27366 − 1446 = 25920`; `25920 = 360 × 72`; Kalumum terminal-alignment displays `15536 − 2936 = 12600`, `14696 − 2936 = 11760 = 24 × 490`, `15486 − 2886 = 12600`, and `14646 − 2886 = 11760 = 24 × 490`; `18000 − 1200 = 16800`; `18000 = 50 × 360`; `16800 = 50 × 336` Major modal states: File_24 re-scoped Kish-cipher state; First Dynasty of Kish 23-kings cipher state; conjectural cipher-premise state; First Dynasty of Kish first-four-kings state; Jushur post-Flood repair state; Kullassina-bel precessional-month state; Nangishlishma hidden-50 riddle state; En-tarah-ana fractional-tail state; first-six-boundary / 3600-14400 partition state; terminal square-chain clue state; Kish-to-Uruk transition square state; SKL Short / Long complementary variant state; universal SKL +30 rail state; `6480` three-month scale state; nested SKL scaling-law state; En-tarah-ana bridge example state; SKL Flood / Kish beginning rail-pair state; first-three-kings 2830 offset state; Nangishlishma-start / Abraham lock state; En-tarah-ana coordinate quartet state; En-tarah-ana endpoint / Babum-start quartet state; Alulim-to-Ubara-Tutu 670 × 360 state; 720 × 360 completion state; biblical interplay example state; Abraham / dual-Exodus 16560 triad state; File_26 companion bridge state; Kings +50 non-cascade state; precessional nine-month Exodus state; SKL Long Flood-to-Exodus precessional-year state; File_34 post-final citation-control state; File_34 rail-pair compatibility state; paired slash-display arithmetic by dependency; Kalumum terminal-alignment state; Jushur-subtracted 50-year dual-scale state; non-exhaustive alignment-support state; En-tarah-ana primary Mosaic-lock coordinate state; En-tarah-ana alternate Danielic coordinate state; Kings +50 / Exodus doublet state; schematic +50 Exodus display state; 16560-to-18000 Key-of-23 expansion state; Christological 1440 extension state; Sumerian-Hebrew +50 shared-grammar hypothesis state; Abraham birth state; Mosaic birth state; primary Exodus state; schematic +50 Exodus display; Christological `6 BC` terminal state; Shem death Gear 1/Gear 2 state; Danielic capstone state; no-formal-Mirror local state; no-Residue local state; Rounded Scaffold non-retrojection state Revision basis: 490d Repository Style Guide v2.5; Restart Capsule v11.15; State Vocabulary Register v1.17; Project Procedures v3.2; `File_00` foundation / archive-routing precedent; `File_51a`; `File_54`; prior finalized source; Repository_Change_Archive (non-controlling history) Current refresh note: Public-clean trust-status equalization aligns active control pointers to 490d Repository Style Guide v2.5, Restart Capsule v11.15, State_Vocabulary_Register v1.17, and Project Procedures v3.2. Register Agreement status is recorded in the header; no arithmetic, anchors, modal states, node-classes, operators, sign conventions, slash-pairs, ranges, envelopes, Mirror protocols, Machine Guards, claim-status labels, theological claims, or dependency boundaries are changed. Detailed pass logs, pressure-test records where applicable, pointer-refresh history, and replacement-workflow notes are preserved in Repository_Change_Archive. # File_24 — The First Dynasty of Kish Cipher: The En-tarah-ana Bridge and the 23-Kings Arrangement ## Related Repository Files | File | Function for `File_24` | |---|---| | `File_00` | Foundational control for source-map discipline, modal-state firewalling, same-side versus cross-axis arithmetic, Mirror / civil / inverse separation, and claim-status restraint. | | `File_01` | Controls Abraham biography anchors, especially Abraham birth at `2166 BC`, where the Nangishlishma-start `16560` display lands. | | `File_02` | Controls Flood / SKL terminology, especially Sumerian A / SKL Short and Sumerian B / SKL Long terminology, `+30 Apparent Mode`, `+2 local rail`, and `+720 scale-state`. | | `File_05` | Controls the primary `1446 BC` Exodus anchor, the 1 Kings 6:1 `480`-year Temple-to-Exodus count, and the rule that subordinate or schematic Exodus displays do not replace the primary anchor. | | `File_08` | Controls the Kings dual-ledger `+50`, distinguishing the Actual / Historical Temple foundation at `966 BC` from the Verbatim / Schematic Temple pivot at `1016 BC`. | | `File_12` | Controls the Priestly `336`-day Ledger where the `16800 = 50 × 336` companion display is opened by comparison. | | `File_13` | Controls the Christological `6 BC` anchor and the Dual Christ anchor distinction where `6 BC` is used as a terminal display. | | `File_16` | Controls the `1876 BC` Nexus, Triple `430`, `+50` Jubilee Offset, and Danielic locks where the Kings ledger or Exodus field touches the broader convergence structure. | | `File_17` | Controls prophetic span-component vocabulary, especially Danielic `2300`, `1260`, `1290`, Key-of-23 exact ratios, the standard precessional `72`-year component, and related exact span language. | | `File_18` | Supplies chronological data-table dependency for Shem-related states, SKL table-source checks, Kings of Judah baseline verification by dependency, and File_21 SKL Unified Protocol dependency. | | `File_19` | Supplies the applied Hezekiah / Temple `430` expansion and preserves File_08's Kings ledger distinction when Temple-month or post-exilic `430` coreference states are named. | | `File_21` | Controls the SKL Unified Protocol, the `360:1` scalar, Sumerian A / SKL Short and Sumerian B / SKL Long states, the `+30 Apparent Mode`, post-Flood Kish / Uruk fractal states, and the En-tarah-ana fractional coordinate state as a SKL source-control / fractional-payload coordinate. | | `File_23` | Immediate predecessor and forward companion. It isolates the SKL fractional payload `3 months and 3.5 days` before `File_24` opens the Kish-cipher and biblical-interplay examples. | | `File_26` | Forward companion file. It isolates the pre-branching `18726 BC` Nangishlishma-start anchor and extends File_24's `27366 BC → 1446 BC = 25920`, Balih `10086 BC`, hidden-`50`, and `18726 BC` states through the `430/432`, `8640/8600`, `1876 BC` Nexus, Pillar, and remote `434886 BC` circuits. | | `File_34` | Final; post-final pressure-tested dependency-controlled source for full SKL / Berossus derivation, month/day textual variants, the full Kish-table rail machinery, En-tarah-ana source metadata, paired slash-display arithmetic, and Appendix B phase-chain / corridor vocabulary where explicitly opened. `File_24` does not locally import File_34 Appendix B Pillar or restoration-corridor machinery unless a section names that state. | | `File_51a` | Procedural and Rounded Scaffold precedent. `File_24` does not open the Rounded Scaffold unless a later pass explicitly does so. | | `File_54` | Later-file style-control exemplar for claim-status restraint, Mirror classification, and non-inflated comparative synthesis. | Dependency note: `File_24` may state the local Kish-cipher displays and En-tarah-ana bridge examples needed for its argument. Full SKL / Berossus derivation, including exact source-table variants, the `17980` versus `24510` total-state distinction, and the rail-pair machinery, remains controlled by `File_34` and indexed by `File_21`. The author-decision layer resolves the authorial one-month straddle by treating it as local File_24 wording for the SKL `+30 Apparent Mode` rail. `File_34 Final; post-final pressure tested` now retains the full source-critical derivation; `File_24` does not revise that derivation locally. File_34 post-final citation-control note: `File_34 Final; post-final pressure tested` controls the post-final SKL / Berossus derivation and the File_34-specific vocabulary for paired slash-display arithmetic, Nisan / Tishri phase-chain arithmetic, the SKL-to-Berossus `2370` corridor, the `30 + 20 + 30` restoration corridor, Pillar / AD target state, Cosmic Pixel state, and Sanctuary Fractal machinery where those states are explicitly opened. `File_24` uses File_34 primarily to keep its Kish-table rails, fractional payload, and Short / Long source relation compatible with the full derivation. External source-control note: The author-approved external source-control link for this Final source is: - https://en.wikipedia.org/wiki/Sumerian_King_List The external source-control datum is used here only to state the public SKL context: the First Dynasty of Kish `23`-kings sequence, the public `24510` total-state report, the position of En-tarah-ana within that sequence, and Mesh-ki-ang-gasher as the first ruler listed under the First rulers of Uruk after Kish is defeated. It is not treated as the source of the repository's harmonic interpretation, SKL / Berossus derivation, or providential synthesis. Primary SKL / Berossus derivation remains `File_21` / `File_34` controlled. LXX source-control note: LXX chronology is not locally developed in the active Final argument. Henry B. Smith Jr.'s reconstruction of the LXX Genesis 5 and 11 chronology remains an important external source-reconstruction witness if a later pass opens detailed LXX Genesis chronology. Smith is not the source of `File_24`'s harmonic interpretation, SKL / Berossus integration, Kish-cipher argument, providential synthesis, or theological reading. ## 0. File-function `File_24` is re-scoped as an explanation of why the `23` kings after the Flood in the First Dynasty of Kish are arranged as they are in the repository's SKL operating state. `File_26` is now registered as the forward companion that isolates the pre-branching `18726 BC` anchor and extends selected File_24 values into the `430/432`, `8640/8600`, Nexus, Pillar, and remote Pre-Creation circuits. The file now has two layers: | Layer | Function | |---|---| | Main layer | Explain the `23`-kings Kish sequence as a mathematical cipher using the SKL `360:1` scalar, visible reign lengths, hidden gap logic, and rail-pair terminal displays. | | Applied examples | Show how the same Kish cipher interacts with biblical chronology through the En-tarah-ana / Moses `16560` lock, the Kings `+50` / Exodus return, the Abraham / dual-Exodus triad, and the Danielic `16100 = 7 × 2300` capstone. | The original File_24 material is therefore preserved but repositioned. The En-tarah-ana bridge is no longer the whole thesis of the file. It is one biblical-interplay example inside a broader argument about the First Dynasty of Kish cipher. Publication-cleanup note: This public-clean source preserves the file's Final, pressure-tested, post-final, focused-pressure-tested, current publication-clean, and dependency-controlled status labels in the header. Detailed pass ledgers, pressure-test records, post-final patch records, pointer-refresh history, and replacement-workflow notes are archived rather than repeated in the public body. Working theological and source-critical interpretation: The authorial working hypothesis is that the basic Kish cipher may have been created by the Sumerians or earlier as a scribal-priestly concealment of mathematical knowledge, while also being unwittingly guided by divine providence. Since no surviving source statement in this local file says that the `23` reigns are a riddle, the file begins with a conjectural cipher-premise state. The available support is internal: if the reigns are treated as a cipher, the hidden `50`, the `3600 + 14400 = 18000` partition, and the terminal square-chain displays allow the parts to scale together and solve the pattern. Human scribal intent therefore remains source-critical hypothesis / structural inference. Divine guidance is preserved as theological note / providential synchronization. Claim-status rule: Arithmetic facts and source-retained SKL data carry the base layer. Structural inferences explain how the checked values interlock. Providential synchronization and theological notes explain why the structure matters, but they do not replace arithmetic, source-control, or dependency control. Modal-state rule: A shared date-label, reign value, hidden-gap value, SKL rail, biblical anchor, or harmonic does not create identity unless state, node-class, tradition, and operator agree. ### 0.1 Working state register | State | Primary values / forms | Node-class / function | Handling in `File_24` | |---|---:|---|---| | File_24 re-scoped Kish-cipher state | whole file | revised file-function | The `23`-kings Kish arrangement is now the main file subject. Biblical chronology examples are subordinate applications. | | First Dynasty of Kish 23-kings cipher state | `23` kings; repository operating total `17980`; hidden-adjusted `18030`; ideal display `18000`; complementary SKL Long total `24510` | post-Flood SKL cipher | Core local state. Preserve Short / Long total-state distinctions and do not collapse `17980`, `24510`, `18030`, or `18000` into one correction sequence. | | Conjectural cipher-premise state | no explicit source statement that the reigns are a riddle; internal solution-fit through `+50` and square-chain clues | source-critical / methodological premise | Begin with conjecture, then test whether the displayed reigns solve coherently. Do not overstate demonstrable scribal intent. | | First-four-kings state | Jushur; Kullassina-bel; Nangishlishma; En-tarah-ana | opening Kish sequence | Establishes the first cipher units and explains why En-tarah-ana becomes active. | | Jushur post-Flood repair state | `1200`; `1200 × 360 = 432000`; `18600 + 1200 = 19800 = 55 × 360` | transition from antediluvian terminal king to post-Flood kingship | Source-retained / dependency-supported display. Arithmetic checked; no arithmetic blocker identified. | | Kullassina-bel precessional-month state | `1200 + 960 = 2160 = 6 × 360` | first-two-kings world-reboot display | Preserved as a structural display. Precessional-month interpretation remains dependency-controlled by `File_21` / `File_17`. | | Nangishlishma hidden-50 riddle state | `670`; hidden `50`; `670 + 50 = 720`; `50 × 360 = 18000` | visible reign plus hidden gap | Core cipher state. The hidden `50` is not a local rail, not `+30`, and not a correction of `670`. | | En-tarah-ana fractional-tail state | `420` years, `3 months`, `3.5` days | fourth Kish king / fractional-tail carrier | Explains why En-tarah-ana remains important inside the larger Kish-cipher file. | | En-tarah-ana / Babum 720 state | `420 + 300 = 720` | fourth-and-fifth-kings completion pair | Preserved as an author-supplied structural display. Expanded Adam / Kenan / Babel vector remains File_21 / File_34 dependency-controlled. | | First-six-boundary / `3600 + 14400` partition state | `20886 BC → 17286 BC = 3600 = 60 × 60`; `17286 BC → 2886 BC = 14400 = 120 × 120`; `3600 + 14400 = 18000` | opening-boundary and terminal-remainder partition | Preserved as solution-fit evidence under the conjectural cipher-premise state. The phrase “first six kings” is treated as boundary shorthand for reaching the sixth-row start at Puannum, not as completion of Puannum’s reign unless later opened. | | Etana / Balih precessional boundary state | Etana endpoint / Balih start `10136/10086 BC`; `20886 − 10136 = 10750 = 150 × 71⅔`; `20886 − 10086 = 10800 = 150 × 72 = 30 × 360` | famous Etana / promised-son boundary | Preserved as author-supplied cipher evidence. Balih's `400` years are noted typologically as an echo of the Abraham / promised-son `400` field, but the arithmetic burden is the Etana-to-Balih boundary span. | | `30 + 20` terminal-tail state | `2936 BC → 2906 BC → 2886 BC`; `2936 − 2906 = 30`; `2906 − 2886 = 20`; `10136 − 2936 = 7200 = 20 × 360`; `10086 − 2886 = 7200 = 20 × 360` | SKL +30 terminal perspective and scaled tail | The 23-kings perspective foregrounds `2936/2906/2886 BC` as the terminal split. The older `2856 BC` base rail remains valid as hidden-`50` base state but is not the primary tail breakdown in this section. | | `670 + 30 + 20` partition state | `670 + 30 + 20 = 720`; `30 × 360 + 20 × 360 = 50 × 360 = 18000` | subpartition of Nangishlishma's `670 + 50 = 720` pattern | The visible `670` and the hidden `50` now resolve internally as `670 + 30 + 20`, with the terminal local-year split mirroring the scaled `30 × 360 + 20 × 360` field. | | Terminal total-state window | `17980`; `18000`; `18030`; `50`; `1/360` | terminal 23-kings total / hidden-gap miniature | Preserved as main synthesis state. Arithmetic checked; no arithmetic blocker identified. | | SKL Short / Long complementary variant state | Short: `20916/20886 BC → 2936/2906 BC = 17980`; Long: `27396/27366 BC → 2886/2856 BC = 24510`; both with appended `3 months` and `3.5` days | complementary SKL witness states | Treat Short and Long as harmonious variant states generated by the same cipher field, analogous in function to complementary biblical witness states. Do not collapse them into contradiction or correction. | | Universal SKL `+30` rail state | base / `+30` pair for SKL dates; examples: `20886/20916 BC`, `27366/27396 BC`, `2906/2936 BC`, `2856/2886 BC` | SKL Apparent Mode rail | All SKL date displays in this file may carry the `+30` rail where the state is opened. The rail is not an error margin and not an ordinary date correction. | | `6480` three-month scale state | `27366 − 20886 = 6480`; `27396 − 20916 = 6480`; `6480 = 18 × 360 = 90 × 72`; `90 = 3 × 30` | Flood-variant gap / precessional three-month display | The Short / Long Flood separation scales to `90` precessional `72`-year units, corresponding to three schematic 30-day months. It complements En-tarah-ana's textual `3 months` without converting the fractional payload into ordinary whole-year arithmetic. | | SKL Long Flood-to-Exodus precessional-year state | `27366 BC → 1446 BC = 25920`; `25920 = 360 × 72` | Long Flood variant to primary Exodus | Preserved as a selective alignment display. It supports the complementary-variant frame by showing the Long Flood base rail landing one full precessional-year span from the primary Exodus anchor. Arithmetic checked; no arithmetic blocker identified. | | Kalumum terminal-alignment state | Kalumum standard `15536–14696 BC`; hidden-`50` variant `15486–14646 BC`; terminals `2936/2886 BC`; `12600`; `11760 = 24 × 490` | internal reign-to-terminal alignment | Preserved as non-exhaustive solution-fit evidence. The row shows that both Kalumum start states align to `12600`, while both Kalumum endpoint states align to `11760 = 24 × 490`, using the matching terminal rail. | | Jushur-subtracted `50`-year dual-scale state | `18000 − 1200 = 16800`; `18000 = 50 × 360`; `16800 = 50 × 336` | full-span minus first-king comparison | Preserved as a secondary scale display. It does not replace the full `18000 = 50 × 360` terminal field; it shows that removing Jushur's `1200` leaves a companion `50 × 336` Priestly-scale display. | | Non-exhaustive alignment-support state | representative examples only | argument-scope guard | The new examples are sufficient for local support but are not exhaustive. Later passes should not treat the absence of a listed example as evidence against the cipher premise. | | SKL appended `93.5`-day fractional-payload state | `3 months + 3.5 days = 93.5 days` | appended SKL textual payload | Preserved as fractional source payload attached to the SKL total states. Whole-year Short / Long arithmetic remains distinct from this payload unless File_34 opens month/day derivation. | | Terminal square-chain clue state | Enmebaragesi `900 = 30^2`; Aga of Kish `625 = 25^2`; Mesh-ki-ang-gasher `324 = 18^2`; sum `1849 = 43^2` | Kish-to-Uruk transition clue | Preserved as author-supplied evidence for deliberate arrangement. Mesh-ki-ang-gasher belongs to the next dynasty and must not be counted inside the `23` Kish kings. | | SKL Flood / Kish beginning rail-pair state | `20886/20916 BC`; `20888/20918 BC` | SKL Flood / Kish beginning display state | Preserve slash-pairs and rail-state distinctions. | | En-tarah-ana coordinate quartet state | `18056/18086 BC`; `18058/18088 BC` | En-tarah-ana arrival after first three kings | Coordinate family preserved; selected examples use individual members. | | En-tarah-ana endpoint / Babum-start quartet state | `17636/17638/17666/17668 BC` | whole-year endpoint after En-tarah-ana's `420` component | Fractional months/days remain textual payload and are not converted silently. | | Alulim-to-Ubara-Tutu `670 × 360` state | `262086 BC → 20886 BC = 241200` | deep-time scalar display | Dependency-controlled by `File_21` / `File_34`; visible arithmetic checked; source provenance remains dependency-controlled. | | `720 × 360` completion state | `262086 BC → 2886 BC = 259200` | full Adam-to-Babel completion display | Dependency-controlled terminal-pair display. | | Kings +50 / Exodus doublet state | File_08 `966/1016 BC`; primary Exodus `1446 BC`; schematic +50 Exodus display `1496 BC` | Kings ledger / Exodus return display | Preserves `1496 BC` as a schematic File_08 +50 display generated by applying the `480` count to `1016 BC`; it does not replace the primary `1446 BC` Exodus state. | | 16560-to-18000 Key-of-23 expansion state | `16560 × 25/23 = 18000`; `18000 − 16560 = 1440`; `18006 − 6 = 18000` | Key-of-23 expansion / Christological terminal display | Preserved as an author-supplied structural display; arithmetic checked. It is not formal Mirror, inverse-number, or Residue Protocol material. | | File_26 companion bridge state | `18726 BC`; `8640/8600`; `18766/18756 BC`; `29516 BC`; `434886 BC` by dependency | forward companion / pre-branching bridge | Dependency-controlled by `File_26`. It extends selected File_24 anchors and Balih / Nangishlishma states into precessional-season, Nexus, Pillar, and remote Pre-Creation displays without replacing the File_24 Kish-cipher argument. | | Sumerian-Hebrew +50 shared-grammar hypothesis state | hidden Kish `50`; Kings dual-ledger `+50`; MT `1656` interval; `18000 = 50 × 360` | structural inference / providential synchronization | The hypothesis may be stated as possible scribal awareness or shared mathematical grammar, not as direct proof of source-critical dependence. | | No-formal-Mirror local state | none locally opened | firewall state | Do not import formal Mirror protocol unless a later pass explicitly opens it. | | Rounded Scaffold non-retrojection state | clean values such as `18000`, `2160`, `16560` | rounded / actual chronology firewall | Clean values are local harmonic displays, not Rounded Scaffold by default. | ### 0.2 Node-class and display-state register | Date / value | Node-class | Active state | Do not collapse with | |---|---|---|---| | `20886 BC` | SKL Flood / Kish beginning base member | SKL Short / base rail | `20916 BC`; `20888 BC`; `20918 BC`; MT/SP/LXX Flood dates. | | `20916 BC` | one-month / `+30` display member | SKL Flood / Kish beginning `+30` member | `20886 BC`; ordinary date correction. | | `20888 BC` | `+2 local rail` base member | SKL Flood / Kish beginning local rail | `20886 BC`; `20918 BC`; `+720 scale-state`. | | `20918 BC` | `+2 local rail` plus one-month / `+30` display member | combined local rail / apparent display | `20888 BC`; `20916 BC`; ordinary range. | | `17980` | repository SKL Short 23-kings operating total | First Dynasty of Kish cipher state | public-source total `24510`; hidden-adjusted `18030`; ideal `18000`. | | `18030` | hidden-`50` adjusted 23-kings total | hidden-50 variant state | `17980`; ideal `18000`. | | `18000` | ideal terminal span and `50 × 360` deep-time span | terminal total-state / hidden-gap scalar | `17980`; `18030`; ordinary rounded correction. | | `2906 BC` | standard terminal after Aga of Kish | Sumerian A / SKL Short terminal base | `2936 BC`; `2856 BC`; `2886 BC`. | | `2936 BC` | standard terminal `+30` display member | `+30 Apparent Mode` / one-month display | `2906 BC`; hidden-50 terminal. | | `2856 BC` | Sumerian B / SKL Long terminal base and lower hidden-`50` terminal member | SKL Long terminal base rail | `2886 BC`; `2906 BC`; `2936 BC`; Short terminal base. | | `2886 BC` | Sumerian B / SKL Long terminal `+30` display member and terminal-pair completion display | SKL Long `+30` rail / ideal `18000` terminus | `2856 BC`; Short terminal base; ordinary correction. | | `2936/2906/2886 BC` | `+30` terminal-tail perspective | `30 + 20` terminal-tail state | lower/base hidden rail `2856 BC`; ordinary range; public-source total state. | | `27366 BC` | Sumerian B / SKL Long Flood base member | SKL Long Flood / Kish beginning base rail | SKL Short `20886 BC`; `27396 BC`; ordinary Flood date. | | `27396 BC` | Sumerian B / SKL Long Flood `+30` member | SKL Long Flood / Kish beginning `+30` rail | `27366 BC`; SKL Short `20916 BC`; ordinary correction. | | `24510` | SKL Long 23-kings total | complementary variant total-state | SKL Short `17980`; hidden-adjusted `18030`; ideal `18000`. | | `93.5 days` | appended fractional payload | `3 months` plus `3.5 days` | whole-year totals `17980` or `24510`; decimalized year conversion unless File_34 opens it. | | `6480` | Flood-level Short / Long separation | `18 × 360 = 90 × 72` scale-state | local `50` terminal gap; `+720 scale-state`; En-tarah-ana textual `3 months` unless state is named. | | `25920` | full precessional-year display | SKL Long Flood-to-Exodus precessional-year state | `19440` nine-month display; ordinary Exodus anchor replacement. | | `15536/15486 BC` | Kalumum start states | standard and hidden-`50` variant terminal-alignment display | En-tarah-ana coordinate quartet; terminal anchors; ordinary range. | | `14696/14646 BC` | Kalumum endpoint states | standard and hidden-`50` variant terminal-alignment display | Kalumum start states; terminal anchors; ordinary range. | | `12600` | Kalumum start-to-terminal span | internal Kish alignment / `35 × 360` display where opened | Cumulative MT `12600` unless a dependency explicitly links the states. | | `11760` | Kalumum endpoint-to-terminal span | `24 × 490` terminal-alignment display | `12600`; ordinary terminal total; local `720` unless state is named. | | `16800` | full `18000` span less Jushur `1200` | `50 × 336` companion display | `18000 = 50 × 360`; Priestly `336` as a replacement calendar year. | | `10136 BC` | Etana endpoint / Balih start, standard column | Etana / Balih precessional boundary state | Balih's full `400`-year reign; terminal Kish total; Abraham `400` typological echo. | | `10086 BC` | Etana endpoint / Balih start, hidden-`50` variant column | Etana / Balih precessional boundary state | `10136 BC`; primary Exodus anchor; terminal Kish total. | | `10750` | alternate precessional-day boundary span | `150 × 71⅔` display | standard `10800`; ordinary prophetic `360` without alternate precessional-day state. | | `10800` | standard precessional-day boundary span | `150 × 72 = 30 × 360` display | alternate `10750`; ordinary terminal total. | | `7200` | terminal continuation from Etana / Balih boundary | `20 × 360` display | `720 × 360`; local `720`; `+720 scale-state` unless explicitly opened. | | `900` | Enmebaragesi reign and `30^2` square display | terminal square-chain clue | ordinary decade multiple only; Enmebaragesi historical-attestation note. | | `625` | Aga of Kish reign and `25^2` square display | terminal square-chain clue | ordinary decade-multiple reigns; terminal total-state arithmetic unless opened. | | `324` | Mesh-ki-ang-gasher reign and `18^2` square display | Kish-to-Uruk transition square clue | the `23` Kish kings total; Mesh-ki-ang-gasher belongs to the next dynasty. | | `1849` | `900 + 625 + 324 = 43^2` | three-reign square-chain sum | individual square displays; ordinary SKL total unless locally opened. | | `17286 BC` | hidden-`50` variant start of Puannum / sixth-row boundary | first-six-boundary partition state | completion of Puannum’s reign; standard-column Puannum start `17336 BC`; terminal `2886 BC`. | | `3600` | opening-boundary span | `20886 BC → 17286 BC`; `60 × 60` | full 23-kings terminal span `18000`; visible standard-table total `17980`. | | `14400` | terminal-remainder span | `17286 BC → 2886 BC`; `120 × 120` | opening-boundary span `3600`; terminal total-state window. | | `18056/18086 BC` | En-tarah-ana arrival pair | base and one-month / `+30` members | `18058/18088 BC`; selected `18086 BC` example. | | `18058/18088 BC` | En-tarah-ana `+2 local rail` arrival pair | local rail and local rail `+30` members | `18056/18086 BC`; selected `18058 BC` example. | | `18006 BC` | hidden-`50` En-tarah-ana start in reduced table | hidden-50 variant start | coordinate quartet; selected `18086 BC` / `18058 BC` biblical examples. | | `17636/17638/17666/17668 BC` | En-tarah-ana endpoint / Babum-start quartet | whole-year `420` component endpoint | fractional-tail month/day payload. | | `966 BC` | Actual / Historical Temple foundation anchor | File_08 Kings dual-ledger state | schematic `1016 BC` pivot; `1496 BC` display. | | `1016 BC` | Verbatim / Schematic Temple pivot | File_08 Kings dual-ledger `+50` state | historical `966 BC` anchor; primary Exodus `1446 BC`. | | `1496 BC` | schematic +50 Exodus display | 1 Kings 6:1 `480` applied to schematic `1016 BC` | primary `1446 BC` Exodus anchor; subordinate Ramesside `1231 BC`; Mosaic birth `1526 BC`. | | `1446 BC` | primary Exodus anchor | File_05 primary Exodus state | schematic `1496 BC` display; subordinate Ramesside `1231 BC`. | | `6 BC` | Christological terminal anchor | File_13 pre-existent Son / Son-of-God New Creation anchor | AD 1 covenant anchor; ordinary cross-axis target unless locally opened. | | `1526 BC` | Moses birth | Mosaic birth state | SKL coordinate states; Aaron branch unless opened. | | `1956/1958 BC` | Death of Shem, MT no-`+60 Terah` Gear 1 / Gear 2 pair | Shem death Gear state | Generic Shem death label; MT `+60 Terah`; selected `1958 BC` Danielic display. | | `1958 BC` | Death of Shem, MT no-`+60 Terah`, Gear 2 / Shem-axis | selected Danielic capstone endpoint | Gear 1 companion `1956 BC`; MT `+60 Terah`; ordinary untagged Shem-death anchor. | | `16560` | Decimal Flood harmonic from selected En-tarah-ana coordinate to Moses / Exodus doublet | biblical interplay example | Kish `18000` cipher; other `16560` states unless state and operator are explicitly linked. | | `1440` | expansion gap from `16560` to `18000`; primary Exodus-to-Christ terminal span | Key-of-23 / Christological extension state | ordinary Exodus anchor replacement; formal Mirror unless locally opened. | | `16100` | `7 × 2300` Danielic capstone display | biblical interplay example | `16560`; terminal Kish cipher. | ### 0.3 File map | Section | Function | Active state / operator | |---|---|---| | §0 | Defines re-scoped file function, working states, node-class register, File map, and Machine Guards | Kish-cipher state; no Mirror / no Rounded / no Residue firewalls | | §1 | States the revised thesis: the 23-kings Kish sequence is the main cipher | SKL `360:1`; providential multi-tradition framing | | §2 | Identifies the source-text frame and first-four-kings context | Jushur; Kullassina-bel; Nangishlishma; En-tarah-ana | | §3 | Organizes the first cipher movements: Jushur repair, precessional month, Nangishlishma hidden `50`, En-tarah-ana / Babum `720`, and first-six-boundary `3600 + 14400` | `1200 × 360`; `18600 + 1200`; `1200 + 960`; `670 + 50`; `420 + 300` | | §4 | Records the reduced 23-kings start-date table | standard column; hidden-`50` variant column; terminal row | | §5 | Synthesizes the terminal total-state window, Etana / Balih tail-split, terminal square-chain clue, SKL Short / Long complementary rail system, and non-exhaustive alignment-support examples | `17980`; `24510`; `18000`; `18030`; `50`; `1/360`; `2936/2906/2886`; `2856`; `6480`; `93.5 days`; `25920`; `15536/15486`; `14696/14646`; `12600`; `11760`; `16800`; `10136/10086`; `10750/10800`; `7200`; `900`; `625`; `324`; `1849` | | §6 | Repositions the En-tarah-ana / Moses, Abraham / dual-Exodus, Kings `+50` / Exodus return, and Danielic capstone displays as biblical-interplay examples | `16560`; `2166 BC`; `1496/1446 BC`; `19440`; `18000`; `1440`; `16100` | | §7 | Collects claim-status and dependency controls | claim-status and source-control preparation | | §8 | Records the arithmetic ledger, argument controls, audit notes, unresolved issues, cross-file updates, and archive note | arithmetic facts; audit retention; publication tracking | ### 0.4 Modal-state and protocol controls Machine Guard [FILE_24 RE-SCOPE]: The controlling thesis is the `23`-kings First Dynasty of Kish cipher. The En-tarah-ana / Moses `16560` lock, the Kings `+50` / Exodus return, the Abraham / dual-Exodus triad, and the Danielic capstone are biblical-interplay examples rather than the main file thesis. Machine Guard [FILE_24 CONJECTURAL CIPHER PREMISE]: No local source statement says that the `23` reigns are a riddle. The file may argue from internal solution-fit: the hidden `50`, the `360:1` scalar, the terminal total-state window, and the square-chain display make the parts cohere if the cipher premise is granted. Do not turn solution-fit into direct proof of conscious scribal intent. Machine Guard [FILE_24 SKL SOURCE-TOTAL DISTINCTION]: The First Dynasty of Kish total-state field includes both Sumerian A / SKL Short `17980` years, `3 months`, and `3.5` days and Sumerian B / SKL Long `24510` years, `3 months`, and `3.5` days. `File_24` foregrounds the Short operating state for the `18000` cipher while preserving the Long state as a complementary variant. Do not collapse the two totals into a contradiction, correction, or ordinary range without opening `File_34` / File_21 source-table control. Machine Guard [FILE_24 UNIVERSAL SKL +30 RAIL]: All SKL date states in this file may carry the `+30 Apparent Mode` rail where that state is opened. The `+30` rail applies to the Short and Long systems alike: `20886/20916 BC`, `27366/27396 BC`, `2906/2936 BC`, and `2856/2886 BC`. Do not treat `+30` as a correction, tolerance, or optional error margin. Machine Guard [FILE_24 SHORT / LONG COMPLEMENTARY VARIANTS]: Sumerian A / SKL Short and Sumerian B / SKL Long are complementary SKL witness states. The Short field uses `20916/20886 BC → 2936/2906 BC = 17980`. The Long field uses `27396/27366 BC → 2886/2856 BC = 24510`. The terminal anchors are separated by `50` years on both base and `+30` rails. Preserve both calculations as harmonious variants unless a later File_34 source-control pass explicitly resolves the source-critical relation differently. Machine Guard [FILE_24 6480 THREE-MONTH SCALE]: The Short / Long Flood separation `6480` is a nested scale-state: `6480 = 18 × 360 = 90 × 72`, and `90 = 3 × 30`. This allows the Flood-level variant gap to echo the En-tarah-ana `3 months` fractional payload at precessional scale. It does not convert the textual `3 months and 3.5 days` into an ordinary whole-year offset and does not replace whole-year SKL arithmetic. Machine Guard [FILE_24 SKL RAIL PAIRS]: The displays `20886/20916 BC`, `20888/20918 BC`, `18056/18086 BC`, and `18058/18088 BC` are rail-pair / slash-pair states. They are not ordinary ranges, averages, or interchangeable dates. Preserve the pair relation and name the active rail whenever a local section narrows to one coordinate. Machine Guard [FILE_24 FILE_34 POST-FINAL BOUNDARY]: `File_24` depends on `File_34 Final; post-final pressure tested` for full SKL / Berossus derivation, source-table variants, paired slash-display arithmetic, phase-chain vocabulary, and post-final corridor controls. Do not import File_34 Appendix B Pillar / AD target spans, the `2370` corridor, the `30 + 20 + 30` restoration corridor, or Sanctuary Fractal machinery into `File_24` unless a local section explicitly opens those states. Machine Guard [FILE_24 SAME-SIDE BC SPANS]: All visible BC-to-BC spans in this file are same-side BC spans. Compute by subtracting the lower BC date from the higher BC date. No ordinary cross-axis `BC + AD − 1` span is active in the local source. Machine Guard [FILE_24 AUTHORIAL `+ 2830` SHORTHAND]: The authorial phrase that the first three kings total `2830` years “to arrive at” En-tarah-ana is treated as an elapsed-forward-in-time SKL offset. In same-side BC arithmetic, same-side BC arithmetic checks it as a movement from a higher BC beginning coordinate to a lower BC En-tarah-ana coordinate. Do not treat the source `+ 2830` wording as a mathematical instruction to increase the BC date label. Machine Guard [FILE_24 WHOLE-YEAR / FRACTIONAL-TAIL FIREWALL]: The first-three-kings offset `2830`, En-tarah-ana's `420`-year reign component, and the endpoint quartet are whole-year SKL displays unless a local section explicitly opens month/day arithmetic. The appended `3 months and 3.5 days` remain a textual fractional payload, not a silent full-year adjustment. Machine Guard [FILE_24 HIDDEN-50 NON-COLLAPSE]: The hidden-`50` Nangishlishma riddle state is a separate author-supplied structural inference. It does not replace the En-tarah-ana coordinate quartet, does not equal the `+2 local rail`, does not equal the `+30 Apparent Mode`, and does not generate the selected `18086 BC` or `18058 BC` coordinates used in §6. Machine Guard [FILE_24 FIRST-SIX BOUNDARY]: The display `20886 BC → 17286 BC = 3600` uses the hidden-`50` variant and lands at the start of the sixth row, Puannum. Treat “first six kings” as authorial boundary shorthand for the first-six-row boundary unless a later section explicitly includes Puannum’s full reign. Do not silently recalculate the display as the completion of the sixth reign. Machine Guard [FILE_24 30+20 TERMINAL TAIL]: From the perspective of the `23` Kish kings with the SKL `+30` rail active, the terminal field is foregrounded as `2936 BC → 2906 BC → 2886 BC`. The executable local split is `2936 − 2906 = 30` and `2906 − 2886 = 20`. The prior `2856 BC` hidden-`50` base rail remains valid in the lower terminal pair, but it is not the primary breakdown when the `23`-kings tail is being explained as `30 + 20`. Machine Guard [FILE_24 ETANA / BALIH PRECESSIONAL BOUNDARY]: The Etana endpoint / Balih-start boundary uses `10136 BC` in the standard column and `10086 BC` in the hidden-`50` variant column. The displays `20886 − 10136 = 10750 = 150 × 71⅔` and `20886 − 10086 = 10800 = 150 × 72 = 30 × 360` are precessional boundary displays. They do not replace the 23-kings terminal total-state or the En-tarah-ana coordinate family. Machine Guard [FILE_24 670+30+20 PARTITION]: The original Nangishlishma display `670 + 50 = 720` is now also preserved as `670 + 30 + 20 = 720`. The `30 + 20` subpartition belongs to the terminal-tail and scaled precessional field; it does not change Nangishlishma's visible reign value of `670` or silently insert a textual `50` into the SKL source row. Machine Guard [FILE_24 KISH / URUK SQUARE-CHAIN BOUNDARY]: The square-chain clue uses the last two Kish kings and the first Uruk ruler: Enmebaragesi, Aga of Kish, and Mesh-ki-ang-gasher. Mesh-ki-ang-gasher is not part of the `23` Kish kings and must not be added to the Kish total-state arithmetic. The square-chain functions as a transition clue, not a new 24th Kish row. Machine Guard [FILE_24 KINGS +50 / EXODUS NON-REPLACEMENT]: The `1496 BC` Exodus display belongs to the File_08 Kings dual-ledger `+50` state. It is generated by applying the 1 Kings 6:1 `480`-year Temple-to-Exodus count to the schematic `1016 BC` pivot. It does not replace the primary `1446 BC` Exodus anchor controlled by `File_05`. Machine Guard [FILE_24 BASE-RAIL / HIDDEN-50 EXODUS DOUBLET]: The Exodus doublet uses `18056 BC` and `18006 BC` as base / hidden-`50` Kish coordinates. These are not the same selected coordinates as the `18086 BC` Moses-birth example or the `18058 BC` Danielic example. Preserve the active coordinate and rail-state before computing a span. Machine Guard [FILE_24 SHEM DEATH GEAR STATE]: The Shem death pair `1956/1958 BC` is an MT no-`+60 Terah` Gear 1 / Gear 2 pair. `1958 BC` is the Gear 2 / Shem-axis endpoint used in the Danielic `16100` display. `1956 BC` remains the Gear 1 companion and must not be substituted into the `16100` display unless the active section explicitly shifts to Gear 1. Machine Guard [FILE_24 KEY-OF-23 / CHRISTOLOGICAL EXTENSION]: The display `16560 × 25/23 = 18000` is an exact-rational Key-of-23 expansion. The difference `18000 − 16560 = 1440` is then compared with `1446 BC → 6 BC = 1440` and `18006 BC → 6 BC = 18000`. This is not formal Mirror protocol, inverse-number reversal, Residue Protocol, or ordinary cross-axis span arithmetic. Machine Guard [FILE_24 KINGS +50 NON-CASCADE]: The File_08 Kings `+50` state is a temporary schematic ledger display reaching the `1496 BC` Exodus node through `1016 + 480`. It must not be allowed to cascade backward through the whole chronology to Adam unless a later file explicitly opens that propagation. In `File_24`, the `+50` is bounded by the Abraham / dual-Exodus `16560` triad and by the primary `1446 BC` Exodus anchor. Machine Guard [FILE_24 FORWARD-OFFSET LANGUAGE]: When the source says that a BC coordinate “+ `16560`” reaches Abraham or Exodus, the statement is a forward-in-time offset. The executable same-side BC display subtracts: `18726 − 16560 = 2166`, `18056 − 16560 = 1496`, and `18006 − 16560 = 1446`. Do not treat the source `+` wording as an instruction to increase the BC date label. Machine Guard [FILE_24 ABRAHAM / DUAL-EXODUS TRIAD]: The `16560` triad uses three different local Kish states: `18726 BC` as the start of Nangishlishma after Jushur and Kullassina-bel, `18056 BC` as the standard En-tarah-ana coordinate after Nangishlishma, and `18006 BC` as the hidden-`50` En-tarah-ana coordinate. These land respectively on Abraham birth `2166 BC`, schematic `1496 BC` Exodus, and primary `1446 BC` Exodus. Preserve all three node-classes. Machine Guard [FILE_24 PRECESSIONAL NINE-MONTH DISPLAY]: The display `20886 BC → 1446 BC = 19440 = 270 × 72` uses the standard precessional `72`-year component by dependency. It is a precessional nine-month / `270`-unit display, not a new SKL rail, not a replacement Exodus anchor, and not a formal astronomical proof beyond the stated repository precessional component. Machine Guard [FILE_24 NON-EXHAUSTIVE ALIGNMENT EXAMPLES]: The examples in §5.4 are selective. They are included to show that additional internal reign details support the terminal-anchor premise and the complementary Short / Long variant state. They do not claim to exhaust every possible alignment inside the `23`-kings field. Machine Guard [FILE_24 TERMINUS-SUPPORT / NON-CONTRADICTION]: The displays `27366 BC → 1446 BC = 25920`, the Kalumum `12600 / 11760` alignments, and the `18000 / 16800` dual-scale display support the premise that `2936/2906 BC` and `2886/2856 BC` are intended terminus points for the Short and Long `23`-kings variants. They are not corrections of the terminal anchors and not contradictions of the Short `17980` or Long `24510` total states. Machine Guard [FILE_24 NO MIRROR / NO ROUNDED / NO RESIDUE]: This file does not open formal Mirror protocol, inverse-number reversal, Residue Protocol, or the File_51a Rounded Scaffold. Clean values such as `18000`, `2160`, `16560`, and `16100` remain actual / local-state harmonic displays unless a later section explicitly opens another state. ## 1. Revised thesis: the 23-kings Kish sequence as mathematical cipher Active state: File_24 re-scoped Kish-cipher state; First Dynasty of Kish 23-kings cipher state; SKL `360:1` scalar state. The working thesis of `File_24` is that the First Dynasty of Kish sequence is not merely a list of post-Flood reign lengths. In the repository operating state, it functions as a mathematical cipher. The cipher works by arranging visible reign lengths, hidden gap values, terminal rail-pairs, and square-chain transition clues so that the post-Flood Kish sequence recapitulates larger SKL deep-time structures under the `360:1` scalar. Methodological premise: The file cannot begin by asserting direct proof that the Kish scribes intended a riddle, because the local source frame does not state that the reigns are a riddle. The argument must begin with the conjectural assumption that the `23` spans were arranged as a scribal-priestly cipher rather than merely assembled from earlier king-list fragments. The proof available inside this file is solution-fit: the proposed hidden `50` and the square-chain transition allow the visible reigns, terminal totals, and deep-time spans to scale together. The organizing sequence is: | Cipher movement | Local value | Scaled / structural function | |---|---:|---| | Jushur | `1200` | Reboots the post-Flood world and harmonizes with `1200 × 360 = 432000`. | | Jushur + Kullassina-bel | `1200 + 960 = 2160` | Establishes a new precessional-month / `6 × 360` display. | | Nangishlishma | `670` plus hidden `50` | Splits the `720` variable into `670 + 50`, mapping Adam-to-Flood plus Flood-to-Babel. | | En-tarah-ana + Babum | `420 + 300 = 720` | Repeats the `720` completion immediately after the hidden-`50` riddle. | | First-six-boundary partition | `3600 + 14400 = 18000` | Splits the hidden-adjusted Kish field into `60 × 60` from `20886 BC` to `17286 BC` and `120 × 120` from `17286 BC` to `2886 BC`. | | Total `23` kings | `17980`; hidden-adjusted `18030`; ideal `18000` | Creates the terminal `50`-year window around the intended `18000 = 50 × 360` span. | | Last two Kish kings plus first Uruk ruler | `900`; `625`; `324`; total `1849` | Three consecutive transition reigns are perfect squares, and their sum is also a perfect square. | Providential note: The file may say that the Kish cipher appears compatible with providential guidance. It should not state that the Sumerian scribes demonstrably understood the full biblical harmonic system unless later source-critical evidence is supplied. ## 2. Source-text frame and first-four-kings context Active state: First Dynasty of Kish first-four-kings state; En-tarah-ana fractional-tail state. The first four kings of the First Dynasty of Kish are the local entry point for the cipher. | Order | Ruler | Reign / value | Local handling | |---:|---|---:|---| | 1 | Jushur / Jushua | `1200` years | First post-Flood Kish reign; source of the post-Flood repair and `432000` scalar display. | | 2 | Kullassina-bel | `960` years | Second reign; combines with Jushur as `2160`. | | 3 | Nangishlishma / Nangishlisha | `670` years | Third reign; visible half of the `670 + 50 = 720` riddle. | | 4 | En-tarah-ana | `420` years, `3 months`, `3.5` days | Fractional-tail carrier and later biblical-interplay bridge figure. | Source-total note: The repository operating state used in this file treats the First Dynasty of Kish total as `17980` years, `3 months`, and `3.5` days, with a hidden-`50` variant total of `18030` and an idealized central display of `18000`. Public translations or summary pages may list `24510` years, `3 months`, and `3.5` days for a different source-state. This file preserves the repository operating state and records the difference as a source-control issue for `File_34`. Textual source-control datum: En-tarah-ana is the SKL figure assigned the anomalous reign form: ```markdown 420 years, 3 months, and 3.5 days ``` The structural issue is not merely that En-tarah-ana has a long SKL reign. The issue is that the extra `3 months and 3.5 days` are attached to this particular fourth Kish figure and not to the other SKL kings in the same way. ## 3. The opening cipher movements ### 3.1 Jushur: the post-Flood repair and the `432000` scalar Active state: Jushur post-Flood repair state; SKL `360:1` scalar state. Jushur is the first king after the Flood. His reign is `1200` years. Two displays are active: ```markdown 1200 × 360 = 432000 ``` and: ```markdown 18600 + 1200 = 19800 = 55 × 360 ``` The first display connects Jushur's `1200` to the `432000` years-to-Flood variant where that SKL state is active. The second display connects Ubara-Tutu / the Noah figure's `18600` years to Jushur's `1200`, producing `19800`, or `55` complete `360`-year cycles. Structural inference: Jushur functions as the transition from the antediluvian terminal king to the post-Flood Kish order. His reign supplies the first post-Flood repair of the `360` counter. ### 3.2 Jushur + Kullassina-bel: the `2160` world-reboot Active state: Kullassina-bel precessional-month state. The first two kings combine as: ```markdown 1200 + 960 = 2160 = 6 × 360 ``` Dependency-controlled interpretation: Where the precessional register is active, `2160` may also be read as one precessional month, using `30° × 72` years per degree. This precessional interpretation remains controlled by `File_21` / `File_17`; the visible arithmetic is checked in arithmetic-control review. ### 3.3 Nangishlishma: the hidden `50` partition Active state: Nangishlishma hidden-50 riddle state; Alulim-to-Ubara-Tutu `670 × 360` state; `720 × 360` completion state. Nangishlishma is given `670` years. Under the conjectural cipher-premise state, the proposed missing `50` years function as the solution-key to the mathematical riddle: ```markdown 670 + 50 = 720 ``` The visible `670` maps to the Adam-to-Flood span under the `360:1` scalar: ```markdown 670 × 360 = 241200 262086 − 20886 = 241200 ``` The hidden `50` maps to the Flood-to-Babel span: ```markdown 50 × 360 = 18000 20886 − 2886 = 18000 ``` Together, the visible and hidden components complete the Adam-to-Babel span: ```markdown (670 + 50) × 360 = 720 × 360 = 259200 262086 − 2886 = 259200 ``` Structural inference: Nangishlishma's `670` is read as incomplete only after the cipher premise is opened. The hidden `50` is not proof by itself. Its evidential role is that it makes the table solve: it creates the `18000` Flood-to-Babel gap and completes the `720 × 360` Adam-to-Babel display. ### 3.4 En-tarah-ana + Babum: the repeated `720` Active state: En-tarah-ana / Babum 720 state; En-tarah-ana fractional-tail state. The next structural pair is: ```markdown 420 + 300 = 720 ``` En-tarah-ana carries the visible `420` plus the fractional tail `3 months and 3.5 days`. Babum contributes `300`. Together they repeat the completed `720` register immediately after Nangishlishma's hidden `670 + 50 = 720` partition. Dependency-controlled expansion: `File_21` / `File_34` may expand the `420 + 300` pair into Adam / Kenan / Babel deep-time vectors. `File_24` preserves that dependency but does not locally rederive the full SKL / Berossus source machinery in this Final source. ### 3.5 The first-six boundary: `3600 + 14400 = 18000` Active state: first-six-boundary / `3600 + 14400` partition state; Nangishlishma hidden-50 riddle state; terminal-pair display state. Under the hidden-`50` variant, the opening sequence reaches the sixth-row boundary at Puannum's start: ```markdown 1200 + 960 + 670 + 50 + 420 + 300 = 3600 20886 − 17286 = 3600 = 60 × 60 ``` Boundary note: The source phrase “first six kings” is retained as authorial shorthand for the movement from the first Kish king to the sixth-row boundary. In the reduced table, `17286 BC` is the hidden-`50` variant start of Puannum. This display therefore includes the completed reigns from Jushur through Babum plus the hidden `50`; it does not include Puannum's `840`-year reign unless a later section explicitly opens that measurement. From that sixth-row boundary, the remainder to the terminal-pair completion member `2886 BC` is: ```markdown 17286 − 2886 = 14400 = 120 × 120 ``` Together, the opening boundary and the terminal remainder produce the intended central span: ```markdown 3600 + 14400 = 18000 20886 − 2886 = 18000 = 50 × 360 ``` Structural inference: This partition strengthens the solution-fit case for the hidden `50`. The added `50` does not merely repair Nangishlishma's `670` into `720`; it also allows the first-six-row boundary to become `3600 = 60 × 60`, while the remaining path to `2886 BC` becomes `14400 = 120 × 120`. The two square spans then sum to the ideal `18000` Kish terminal display. Terminal-tail note, revised by author clarification: The `23`-kings perspective foregrounds the `+30` tail: ```markdown 2936 − 2906 = 30 2906 − 2886 = 20 2936 − 2886 = 50 ``` The file therefore foregrounds `2936 BC`, `2906 BC`, and `2886 BC` as the active terminal-tail explanation. The older `2856 BC` hidden-`50` base rail remains valid in the terminal-pair system, but the active cipher breakdown here is `30 + 20`, not `20 + 30`. ## 4. Reduced 23-kings start-date table Active state: First Dynasty of Kish 23-kings start-table state; Nangishlishma hidden-50 riddle state. The reduced table uses start dates only. This removes the redundant end-date column, because each king's end is the next king's start. The terminal row after Aga of Kish is retained because it preserves the total and the hidden-`50` endpoint. | Order | Ruler | Reign | Standard start | Hidden-`50` variant start | |---:|---|---:|---:|---:| | 1 | Jushur | 1200 | 20886 BC | 20886 BC | | 2 | Kullassina-bel | 960 | 19686 BC | 19686 BC | | 3 | Nangishlishma | 670 | 18726 BC | 18726 BC | | 4 | En-tarah-ana | 420 | 18056 BC | 18006 BC | | 5 | Babum | 300 | 17636 BC | 17586 BC | | 6 | Puannum | 840 | 17336 BC | 17286 BC | | 7 | Kalibum | 960 | 16496 BC | 16446 BC | | 8 | Kalumum | 840 | 15536 BC | 15486 BC | | 9 | Zuqaqip | 900 | 14696 BC | 14646 BC | | 10 | Atab | 600 | 13796 BC | 13746 BC | | 11 | Mashda | 840 | 13196 BC | 13146 BC | | 12 | Arwium | 720 | 12356 BC | 12306 BC | | 13 | Etana | 1500 | 11636 BC | 11586 BC | | 14 | Balih | 400 | 10136 BC | 10086 BC | | 15 | En-me-nuna | 660 | 9736 BC | 9686 BC | | 16 | Melem-Kish | 900 | 9076 BC | 9026 BC | | 17 | Barsal-nuna | 1200 | 8176 BC | 8126 BC | | 18 | Zamug | 140 | 6976 BC | 6926 BC | | 19 | Tizqar | 305 | 6836 BC | 6786 BC | | 20 | Ilku | 900 | 6531 BC | 6481 BC | | 21 | Iltasadum | 1200 | 5631 BC | 5581 BC | | 22 | Enmebaragesi | 900 | 4431 BC | 4381 BC | | 23 | Aga of Kish | 625 | 3531 BC | 3481 BC | | Terminal | After Aga of Kish | — | 2906 BC | 2856 BC | Visible display set: ```markdown 1200 + 960 + 670 = 2830 20886 − 2830 = 18056 BC 18056 − 50 = 18006 BC 1200 + 960 + 670 + 50 + 420 + 300 = 3600 20886 − 17286 = 3600 = 60 × 60 17286 − 2886 = 14400 = 120 × 120 3600 + 14400 = 18000 20886 − 2906 = 17980 20886 − 2856 = 18030 20886 − 2886 = 18000 262086 − 20886 = 241200 = 670 × 360 262086 − 2886 = 259200 = 720 × 360 = (670 + 50) × 360 20886 − 10136 = 10750 = 150 × 71⅔ 20886 − 10086 = 10800 = 150 × 72 = 30 × 360 10136 − 2936 = 7200 = 20 × 360 10086 − 2886 = 7200 = 20 × 360 2936 − 2906 = 30 2906 − 2886 = 20 670 + 30 + 20 = 720 ``` Display-state note: The `2886 BC` endpoint in the final two displays is the terminal-pair / `+30` display member corresponding to the hidden-`50` terminal field. The table itself shows the base hidden-`50` terminal at `2856 BC`. Do not collapse `2856 BC` and `2886 BC`; they belong to different members of the terminal display pair. When the `23`-kings terminal-tail perspective is active, the preferred explanatory triad is `2936 BC → 2906 BC → 2886 BC`, yielding `30 + 20 = 50`. ## 5. Terminal total-state synthesis Active state: terminal total-state window; hidden-50 variant state; ideal `18000` display. The reduced table produces the following terminal state family: | Display | Calculation | Function | |---|---:|---| | Standard repository operating total | `20886 − 2906 = 17980` | Visible First Dynasty of Kish operating total in this file. | | Hidden-`50` variant total | `20886 − 2856 = 18030` | Adds the hidden `50` by shifting the post-Nangishlishma sequence forward by `50` years. | | Ideal central span | `20886 − 2886 = 18000` | Uses the `+30` terminal member to display the intended `50 × 360` span. | | Opening-boundary partition | `20886 − 17286 = 3600 = 60 × 60` | Hidden-`50` variant reaches the Puannum / sixth-row boundary as a square span. | | Terminal-remainder partition | `17286 − 2886 = 14400 = 120 × 120` | Remainder from the sixth-row boundary to the ideal `2886 BC` terminal member. | | Partition sum | `3600 + 14400 = 18000` | The two square spans reproduce the ideal central span. | | Total-state window width | `18030 − 17980 = 50` | The gap between the visible and hidden totals. | | Miniature relation | `18000 ÷ 360 = 50` | The visible `50`-year total-state window is the `1/360` miniature of the `18000` deep-time span. | Structural inference: The sequence encodes `18000` twice: once as the deep-time Flood-to-Babel span under `50 × 360`, and once as the idealized terminal span of the `23`-kings table. The added partition now gives the same `18000` as `3600 + 14400`, or `60 × 60` plus `120 × 120`. The gap between `17980` and `18030` is itself `50`, making the local table-window a miniature of the scaled `18000` span. Terminal-pair note: The base standard terminal is `2906 BC`; its `+30` display member is `2936 BC`. The base hidden-`50` terminal is `2856 BC`; its `+30` display member is `2886 BC`. The `2886 BC` member is the one used for the full `720 × 360` Adam-to-Babel completion display. For the internal `23`-kings cipher, the tail is now best stated from the `+30` perspective as `2936 BC → 2906 BC → 2886 BC`, or `30 + 20 = 50`. ### 5.1 Terminal square-chain clue: Enmebaragesi, Aga, and Mesh-ki-ang-gasher Active state: terminal square-chain clue state; Kish-to-Uruk transition square state; conjectural cipher-premise state. Before returning to En-tarah-ana, the terminal arrangement of the `23` Kish kings should be noted. The last two Kish kings and the first ruler of the next dynasty form a square-chain display: | Position | Ruler | Dynasty state | Reign | Square display | |---|---|---|---:|---:| | Last two Kish kings, first member | Enmebaragesi | First Dynasty of Kish | `900` | `30^2` | | Last two Kish kings, second member | Aga of Kish | First Dynasty of Kish | `625` | `25^2` | | First next-dynasty ruler | Mesh-ki-ang-gasher | First rulers of Uruk / E-anna transition | `324` | `18^2` | | Three-reign transition sum | Enmebaragesi + Aga + Mesh-ki-ang-gasher | Kish-to-Uruk transition display | `1849` | `43^2` | Visible display: ```markdown 900 = 30^2 625 = 25^2 324 = 18^2 900 + 625 + 324 = 1849 = 43^2 ``` Structural inference: This is a transition clue rather than a new Kish total. If the first two of these reigns close the Kish list and the third opens the next dynasty, then the square-chain suggests that the end of Kish and the beginning of Uruk were arranged with mathematical awareness. This supports the broader conjecture that the reign lengths function as cipher-values rather than as a loose compilation of fragments. Claim-status restraint: The square-chain does not independently prove source-critical intent. Its role is cumulative. Together with the hidden `50`, the `720` recurrences, the `18000` terminal window, and the `360:1` scaling, it strengthens the solution-fit case for a planned cipher. Audit note: The claim that the values before this point are mostly decade-based should be worded with restraint. In the displayed table, Tizqar has `305` years and Aga has `625` years; therefore the argument should not say that all earlier reigns are multiples of `10`. The safer claim is that the sudden cluster `900`, `625`, and `324` becomes conspicuous because it forms a consecutive square-chain across the Kish-to-Uruk boundary. ### 5.2 Etana / Balih boundary and the `30 + 20` scaled tail Active state: Etana / Balih precessional boundary state; `30 + 20` terminal-tail state; `670 + 30 + 20` partition state; SKL `+30` Apparent Mode by dependency. The terminal-tail state also appears at the Etana / Balih boundary. Etana is the famous Kish ruler described in source tradition as the shepherd who ascended to heaven and consolidated foreign lands. Balih follows him as the promised son and receives `400` years. Typological note: Balih's `400` years may be read as an echo of the Abrahamic `400`-year field associated with Abram, the promised son, and the Covenant of Pieces. This typological note does not carry the arithmetic burden of the section. The active boundary is Etana's endpoint / Balih's start: | Column | Etana endpoint / Balih start | Flood-to-boundary display | Precessional form | |---|---:|---:|---:| | Standard column | `10136 BC` | `20886 − 10136 = 10750` | `150 × 71⅔` | | Hidden-`50` variant column | `10086 BC` | `20886 − 10086 = 10800` | `150 × 72 = 30 × 360` | The standard column uses the alternate precessional-day display: ```markdown 150 × 71⅔ = 10750 ``` The hidden-`50` variant column uses the standard precessional-day display and locks the boundary to `30 × 360`: ```markdown 150 × 72 = 10800 10800 = 30 × 360 ``` From that boundary the terminal continuation supplies the remaining `20 × 360`: ```markdown 10136 − 2936 = 7200 = 20 × 360 10086 − 2886 = 7200 = 20 × 360 ``` The local terminal labels then display the same split at ordinary Kish-year scale: ```markdown 2936 − 2906 = 30 2906 − 2886 = 20 2936 − 2886 = 50 ``` Structural inference: The scaled field is therefore `30 × 360 + 20 × 360 = 50 × 360 = 18000`, while the local terminal-tail field is `30 + 20 = 50`. This mirrors the earlier Nangishlishma riddle, but with more internal resolution: ```markdown 670 + 50 = 720 670 + 30 + 20 = 720 ``` Claim-status restraint: This section strengthens the solution-fit argument under the conjectural cipher premise. It does not prove that a surviving SKL scribe stated the riddle. It shows that, once the hidden `50` and the SKL `+30` rail are active, the Etana / Balih boundary and the terminal tail scale together as `30 + 20`, with the `670 + 50 = 720` pattern resolving as `670 + 30 + 20`. Audit note: The `2936/2906/2886 BC` terminal-tail perspective should be treated as the preferred explanatory form for the `23` Kish kings. The lower `2856 BC` hidden-`50` base rail remains valid in the terminal-pair system and should not be deleted from the reduced table or source-control notes. ### 5.3 SKL Short / Long complementarity and the `6480` three-month scale Active state: SKL Short / Long complementary variant state; universal SKL `+30` rail state; `6480` three-month scale state; SKL appended `93.5`-day fractional-payload state. The terminal-tail discussion must keep the Short and Long SKL calculations in view. The two computations are not treated as contradictions inside `File_24`. They are complementary variant states built on the same cipher field. | SKL state | Flood / Kish beginning | Terminal anchor for the `23` kings | Whole-year span | Appended payload | Handling in `File_24` | |---|---:|---:|---:|---:|---| | Sumerian A / SKL Short | `20916/20886 BC` | `2936/2906 BC` | `17980` | `3 months + 3.5 days = 93.5 days` | Foregrounded operating state for the `18000` cipher. | | Sumerian B / SKL Long | `27396/27366 BC` | `2886/2856 BC` | `24510` | `3 months + 3.5 days = 93.5 days` | Complementary variant state preserving the same fractional payload. | The Short calculation checks by the same active rail on both ends: ```markdown 20916 − 2936 = 17980 20886 − 2906 = 17980 ``` The Long calculation does the same: ```markdown 27396 − 2886 = 24510 27366 − 2856 = 24510 ``` The two terminal systems are separated by the same hidden `50` already active in the Nangishlishma cipher: ```markdown 2936 − 2886 = 50 2906 − 2856 = 50 ``` From the preferred `23`-kings `+30`-tail perspective, the same `50` is split internally as `30 + 20`: ```markdown 2936 − 2906 = 30 2906 − 2886 = 20 2936 − 2886 = 50 ``` The Flood-side separation between Short and Long is the larger scale of the same nested grammar: ```markdown 27366 − 20886 = 6480 27396 − 20916 = 6480 6480 = 18 × 360 6480 = 90 × 72 90 = 3 × 30 ``` Structural inference: The Short / Long Flood separation of `6480` years is `90` standard precessional `72`-year units. Under the rounded 360-day calendar grammar, `90` units corresponds to three 30-day months. This supplies a scaled counterpart to the `3 months` appended to En-tarah-ana's reign. The same textual payload remains `3 months and 3.5 days`; the scale-state explains why that payload participates in the larger cipher without converting it into an ordinary whole-year coordinate. Witness-state note: The Short and Long SKL states are therefore read as complementary, in the same general witness-state sense that MT and LXX can be complementary inside the biblical chronology. They may preserve different total states and terminal anchors while participating in one shared mathematical grammar. Source-context note: The author-supplied SKL / Bible merger diagram is retained as source-context for this addendum. It does not replace `File_21` or `File_34` as the controlling source files for the SKL rail system, but it helps identify which rail-pairs and terminal anchors must remain visible during later arithmetic checking. Claim-status restraint: This section adds solution-fit evidence under the conjectural cipher premise. It does not prove by itself that a surviving SKL scribe consciously encoded the full nested scaling-law system. It does show that the Short / Long totals, the `+30` rail, the terminal `50`, and the Flood-level `6480` separation can be read as one coordinated cipher field. ### 5.4 Non-exhaustive alignment examples supporting the terminal anchors Active state: non-exhaustive alignment-support state; SKL Long Flood-to-Exodus precessional-year state; Kalumum terminal-alignment state; Jushur-subtracted `50`-year dual-scale state. The preceding examples are not exhaustive. The present file only needs enough internal alignment to show that the details within the `23`-kings period support, rather than contradict, the premise that the terminal points `2936/2906 BC` for the Short state and `2886/2856 BC` for the Long state are intended terminus points. First, the Long Flood variant at `27366 BC` lands one full precessional-year span from the primary Exodus anchor: ```markdown 27366 − 1446 = 25920 25920 = 360 × 72 ``` This display complements the earlier Short Flood / Exodus display: ```markdown 20886 − 1446 = 19440 = 270 × 72 ``` The Short display reaches the Exodus through `270` standard precessional `72`-year units, or nine schematic months. The Long display reaches the Exodus through the full `360` such units, or one complete precessional-year display. The two are therefore not competing Exodus anchors; they are complementary scale displays anchored to the same primary `1446 BC` Exodus state. Second, Kalumum's `840`-year row supplies a local example that both terminal systems continue to align internally: | Kalumum row-state | Start / endpoint | Terminal anchor | Span | Display | |---|---:|---:|---:|---| | Standard start | `15536 BC` | `2936 BC` | `12600` | `15536 − 2936 = 12600` | | Standard endpoint | `14696 BC` | `2936 BC` | `11760` | `14696 − 2936 = 11760 = 24 × 490` | | Hidden-`50` variant start | `15486 BC` | `2886 BC` | `12600` | `15486 − 2886 = 12600` | | Hidden-`50` variant endpoint | `14646 BC` | `2886 BC` | `11760` | `14646 − 2886 = 11760 = 24 × 490` | Kalumum's own reign length separates the two spans: ```markdown 12600 − 11760 = 840 ``` This does not make Kalumum the center of the file. It functions as an illustrative internal row showing that the `2936/2886 BC` terminal rail remains productive inside the `23`-kings table. Third, the full ideal `18000` span can be read beside the first king, Jushur: ```markdown 18000 − 1200 = 16800 18000 = 50 × 360 16800 = 50 × 336 ``` The full span is `50` prophetic years at `360`. Once Jushur's opening `1200` is removed, the remaining `16800` is `50` Priestly `336`-day ledger years. This is a companion scale display, not a replacement for the full `18000 = 50 × 360` terminal field. Claim-status restraint: These examples are non-exhaustive solution-fit evidence under the conjectural cipher premise. They strengthen the claim that the Short and Long terminal anchors are deliberate components of one mathematical field, but they do not by themselves prove a surviving source-critical statement of scribal intent. ## 6. Biblical-chronology interplay examples Active state: biblical interplay example state. The earlier En-tarah-ana bridge material is preserved here as applied examples. These examples show how the Kish cipher interacts with biblical chronology, but they no longer define the whole file. ### 6.1 The `16560` En-tarah-ana / Moses lock Active state: En-tarah-ana primary Mosaic-lock coordinate state; Mosaic birth state; Decimal Flood harmonic state. | Component | Value | State | |---|---:|---| | Selected En-tarah-ana coordinate | 18086 BC | selected member of the En-tarah-ana coordinate quartet | | Mosaic anchor | 1526 BC | Birth of Moses | | Source span display | `18086 − 1526 = 16560` | same-side BC span display | | Harmonic display | `16560 = 10 × 1656` | Decimal Flood harmonic | Structural inference: The span from the selected En-tarah-ana deep-time coordinate to Moses' birth is presented as a decimal expansion of the MT Creation-to-Flood interval. The movement from the SKL “broken time” register to the Mosaic deliverer register is read through the `10 × 1656` relation. Terminology note: The value `1656` is retained as the MT Creation-to-Flood interval / Flood-year harmonic. It is not a BC date in this display. ### 6.2 The Danielic capstone Active state: En-tarah-ana alternate Danielic coordinate state; Shem death Gear 1/Gear 2 state; Danielic capstone state. | Component | Value | State | |---|---:|---| | Selected alternate En-tarah-ana coordinate | 18058 BC | selected member of the En-tarah-ana coordinate quartet | | Death of Shem, Gear 1 companion | 1956 BC | MT no-`+60 Terah`, Gear 1 / Japheth-side companion state | | Death of Shem, selected endpoint | 1958 BC | MT no-`+60 Terah`, Gear 2 / Shem-axis endpoint | | Source span display | `18058 − 1958 = 16100` | same-side BC span display using the Gear 2 endpoint | | Danielic display | `16100 = 7 × 2300` | Danielic `2300` cycle display | Dependency note: The Danielic `2300` component remains controlled by `File_17`. The author has clarified that Shem's `1956 BC` and `1958 BC` death states are MT no-`+60 Terah` Gear 1 and Gear 2 respectively. `File_24` uses the Gear 2 / Shem-axis `1958 BC` member for the `16100` capstone, while preserving `1956 BC` as the Gear 1 companion state. ### 6.3 The Kings `+50` / Exodus return to the `16560` lock Active state: Kings dual-ledger `+50` state; primary Exodus state; schematic +50 Exodus display state; En-tarah-ana hidden-50 base coordinate state; Key-of-23 expansion state; Christological `6 BC` terminal state. The Kish cipher returns to the original `16560` bridge through the Kings ledger. In `File_08`, the historical Temple foundation anchor remains `966 BC`, while the schematic Kings ledger uses `1016 BC`; the `+50` links the ledgers without collapsing them. Under the 1 Kings 6:1 `480`-year Temple-to-Exodus count, the historical Temple foundation line gives: ```markdown 966 + 480 = 1446 BC ``` If the same `480`-year rule is applied inside the schematic `1016 BC` Kings ledger, the Exodus display pushes to: ```markdown 1016 + 480 = 1496 BC ``` The En-tarah-ana / Exodus doublet then resolves as follows: | Track | En-tarah-ana coordinate | Exodus coordinate | Calculation | State | |---|---:|---:|---|---| | Schematic Kings `+50` track | 18056 BC | 1496 BC | `18056 − 1496 = 16560 = 46 × 360` | schematic +50 Exodus display | | Hidden-`50` Kish / primary Exodus track | 18006 BC | 1446 BC | `18006 − 1446 = 16560 = 46 × 360` | hidden-50 Kish coordinate with primary Exodus | The `16560` bridge is therefore not only a Moses-birth example from `18086 BC → 1526 BC`. It also appears as an Exodus doublet when the File_08 `+50` Kings ledger is set beside the Kish hidden-`50` rail. Key-of-23 expansion: ```markdown 16560 × 25/23 = 18000 18000 − 16560 = 1440 1446 − 6 = 1440 18006 − 6 = 18000 = 50 × 360 ``` Structural inference: The hidden `50` in the Kish cipher and the Kings dual-ledger `+50` are now set beside one another as a shared-mathematical-grammar display. The `16560` Exodus doublet expands by `25/23` to `18000`, and the expansion gap `1440` is the same same-side span from the primary Exodus `1446 BC` to the Christological `6 BC` terminal. This brings the Kish hidden-`50`, the Kings `+50`, the MT `1656` Creation-to-Flood interval, and the Christological endpoint into one applied biblical-interplay example. Claim-status note: The arithmetic displays are checked and retained as author-supplied structural displays. The interpretive claim that the Hebrew scribal `+50` may indicate awareness of, or providential synchronization with, the Sumerian hidden-`50` cipher is preserved as structural inference / providential synchronization under the shared mathematical grammar state. It is not treated as direct proof of source-critical dependence unless a later dependency supplies such evidence. State-control note: `1496 BC` is not a replacement Exodus anchor. It is a schematic File_08 `+50` / 1 Kings 6:1 display. The primary Exodus anchor remains `1446 BC`. The Christological `6 BC` point is controlled by `File_13` and is used here only as the terminal endpoint of the `1440` extension and the `18000 = 50 × 360` completion from `18006 BC`. ### 6.4 The Abraham / dual-Exodus triad: why the Kings `+50` stops at Exodus Active state: Abraham / dual-Exodus `16560` triad state; Kings `+50` non-cascade state; primary Exodus state; schematic +50 Exodus display state; precessional nine-month Exodus state. The same `16560` span also explains why the File_08 Kings `+50` should be treated as a temporary schematic node at `1496 BC`, not as a global `+50` cascade backward to Adam. Source-direction note: The authorial shorthand may say that the Kish coordinates are “+ `16560`” to Abraham or Exodus because the movement is forward in time. Under the local same-side BC operator, the executable display subtracts the elapsed span from the higher BC coordinate. | Kish coordinate | Local state | Executable display | Biblical landing | Node-class control | |---:|---|---|---:|---| | 18726 BC | start of Nangishlishma after Jushur and Kullassina-bel | `18726 − 16560 = 2166` | 2166 BC | Birth of Abraham by `File_01` dependency | | 18056 BC | standard En-tarah-ana coordinate after Nangishlishma | `18056 − 16560 = 1496` | 1496 BC | schematic Kings `+50` Exodus display | | 18006 BC | hidden-`50` En-tarah-ana coordinate | `18006 − 16560 = 1446` | 1446 BC | primary Exodus anchor by `File_05` dependency | Structural inference: The triad places Abraham's birth, the schematic Kings `+50` Exodus, and the primary Exodus anchor into one `16560` field. This supports the interpretation that the Kings `+50` is an intentional ledger display reaching the temporary `1496 BC` Exodus node, while the hidden-`50` Kish rail returns to the actual primary Exodus anchor at `1446 BC`. Non-cascade control: The `1496 BC` Exodus display should not be pushed backward as a new universal chronology. In this file, the `+50` is bounded by the File_08 Kings ledger and by the fact that the hidden-`50` En-tarah-ana coordinate already locks directly to the primary `1446 BC` Exodus anchor. The SKL Flood / Kish beginning also locks to the primary Exodus through a precessional display: ```markdown 20886 − 1446 = 19440 19440 = 270 × 72 270 = 9 × 30 ``` Structural inference: The SKL Flood / Kish beginning at `20886 BC` to the primary Exodus at `1446 BC` forms `19440`, which is `270` standard precessional `72`-year units. This supplies a nine-month / `270`-unit precessional display around the primary Exodus anchor. It reinforces the non-cascade handling: the `1496 BC` node is a schematic Kings-ledger push, while `1446 BC` remains the actual anchor that receives both the hidden-`50` En-tarah-ana lock and the SKL Flood-to-Exodus precessional display. Claim-status note: The new displays are checked and retained as author-supplied structural displays. The non-cascade interpretation is a structural inference from solution-fit: the `+50` produces the temporary `1496 BC` Kings display, but the `16560` and `19440` locks preserve the primacy of the `1446 BC` Exodus anchor. State-control note: `2166 BC` is an Abraham biography anchor controlled by `File_01`. `1496 BC` is a schematic File_08 / File_05 Exodus display. `1446 BC` is the primary Exodus anchor controlled by `File_05`. `20886 BC` is the SKL Flood / Kish beginning state controlled by `File_02`, `File_21`, and `File_34` by dependency. ## 7. Claim-status and dependency controls Argument-control rule: This section assigns proof burden without changing arithmetic. Arithmetic facts and source-retained SKL data carry the base layer. Structural inferences identify how verified spans interlock under the conjectural cipher premise. Providential synchronization and typological notes explain theological meaning but do not replace source-control, arithmetic, or explicit dependency control. | Author-decision item | Final handling | |---|---| | Mesh-ki-ang-gasher source-control | Classified as the first ruler listed under the First rulers of Uruk after Kish is defeated and kingship is taken to E-anna. He remains outside the `23` Kish kings while participating in the Kish-to-Uruk terminal square-chain clue. | | En-tarah-ana external citation | Use the public Sumerian King List page as the temporary external source-control link. Primary SKL / Berossus derivation remains `File_21` / `File_34` controlled and may be upgraded later before publication. | | One-month straddle | Treat as local File_24 language for the SKL `+30 Apparent Mode` rail. It is not a separate operator, correction, or tolerance. Full source-critical derivation remains `File_34` controlled. | | `17980` versus `24510` | Treat as complementary Short / Long SKL total states from different source streams. The public `24510` report does not contradict the repository operating `17980` state. | | File_34 boundary | Keep File_34 as the full source-critical derivation for SKL / Berossus, terminal-pair machinery, and Short / Long source relation. File_24 may state local operating displays only. | | LXX source-control | Detailed LXX Genesis 5 / 11 source-control is not opened locally in the Final source. Retain only the one background source-control note in case a later revision reopens LXX chronology. | | Non-exhaustive alignment examples | Retain in the main argument as selective corroborative solution-fit evidence. They remain main-body support in the Final source. | | Claim / datum | Final claim-status handling | |---|---| | File_24 re-scope to the `23`-kings Kish cipher | Author-directed file-function change. Treated as the controlling local thesis. | | Sumerian or earlier origin of the cipher | Source-critical hypothesis / structural inference. The local file does not claim a surviving source statement that names the cipher. | | Scribal-priestly concealment premise | Conjectural cipher-premise state. The local evidence is solution-fit: the parts scale coherently when the hidden `50`, the rail system, and the terminal displays are read together. | | Divine providential guidance of the cipher | Theological note / providential synchronization. Preserved as the author's interpretation without making it a replacement for arithmetic proof. | | First Dynasty of Kish first-four-kings context | Author-clarified modal state. Source metadata remains dependency-controlled by `File_21` / `File_34`. | | Public-source `24510` total versus repository operating `17980` total | Source-state distinction. Short and Long totals are complementary SKL witness states, not contradictions, until File_34 source-control opens the full table mechanics. | | Universal SKL `+30` rail | Modal rail rule. The `+30 Apparent Mode` is not a correction, tolerance, or error margin. | | Appended `93.5`-day payload | Textual fractional payload: `3 months + 3.5 days = 93.5 days`. Whole-year arithmetic remains separate unless File_34 opens month/day mechanics. | | `6480` Flood-level Short / Long separation | Structural inference / nested scaling-law state: `6480 = 18 × 360 = 90 × 72`, with `90 = 3 × 30`. | | Full reduced `23`-kings start-date table | Source-retained / author-supplied structural table. Arithmetic-control review verified table continuity under the active hidden-`50` state. | | Jushur `1200`, Kullassina-bel `960`, Nangishlishma `670`, En-tarah-ana `420`, `3 months`, `3.5` days | Source-control values and opening cipher states. Their interpretive role is structural inference, not an independent proof of source-critical intent. | | Jushur repair displays | Structural inference supported by arithmetic facts: `1200 × 360 = 432000`; `18600 + 1200 = 19800 = 55 × 360`. | | First-two-kings `2160` display | Structural inference; precessional-month interpretation remains dependency-controlled by `File_17` / `File_21`. | | Nangishlishma hidden-`50` riddle | Structural inference under the conjectural cipher premise. The `+50` is evidential because it solves scale-alignment; it is not direct source-critical proof by itself. | | `262086 BC → 20886 BC = 241200 = 670 × 360` | Arithmetic fact plus structural inference; source provenance remains `File_21` / `File_34` dependent. | | `262086 BC → 2886 BC = 259200 = 720 × 360` | Arithmetic fact plus structural inference. The `2886 BC` endpoint belongs to the terminal-pair / `+30` display state. | | `420 + 300 = 720` | Arithmetic fact and structural inference. Expanded deep-time partition remains dependency-controlled. | | First-six-boundary `3600 + 14400 = 18000` | Solution-fit evidence under the conjectural cipher premise; not direct proof of scribal intent. | | `30 + 20` terminal tail | Author-clarified explanatory form for the `23`-kings terminal-tail perspective. Lower `2856 BC` remains a base rail. | | Etana / Balih precessional boundary | Structural inference / solution-fit evidence. Balih's `400` typological echo remains a typological note and does not carry the arithmetic burden. | | `670 + 30 + 20 = 720` partition | Structural refinement of the hidden `670 + 50 = 720` state; it does not alter Nangishlishma's visible `670` reign value. | | Terminal square-chain `900`, `625`, `324`, `1849` | Structural clue / probable authorial design under the conjectural cipher premise; Mesh-ki-ang-gasher is classified as the first ruler under the First rulers of Uruk after the `23` Kish kings and must not be counted as a 24th Kish king. | | `20886/20916 BC`; `20888/20918 BC` | SKL Flood / Kish beginning rail-pair states. Preserve slash-pairs, `+30`, and `+2 local rail` distinctions. | | `18056/18086 BC`; `18058/18088 BC` | En-tarah-ana coordinate quartet. Selected coordinates `18086 BC`, `18058 BC`, `18056 BC`, and `18006 BC` remain distinct display states. | | `17636/17638/17666/17668 BC` | En-tarah-ana endpoint / Babum-start quartet. Fractional month/day payload remains separate. | | `18086 BC → 1526 BC = 16560`; `16560 = 10 × 1656` | Biblical-interplay example. Distinct from Kish terminal `18000` and from any other `16560` state in the repository. | | Shem deaths `1956/1958 BC` | Author-clarified MT no-`+60 Terah` Gear 1 / Gear 2 pair. `1958 BC` is selected for the `16100` Danielic capstone. | | `18058 BC → 1958 BC = 16100`; `16100 = 7 × 2300` | Biblical-interplay example and Danielic display. The `2300` component remains controlled by `File_17`. | | File_08 Kings dual-ledger `+50` | Dependency-controlled Kings ledger state: `966 BC` historical Temple foundation versus `1016 BC` schematic Temple pivot. | | `1016 + 480 = 1496 BC` | Schematic `+50` Exodus display. It is not a replacement for the primary `1446 BC` Exodus anchor. | | `18056 BC → 1496 BC = 16560`; `18006 BC → 1446 BC = 16560` | En-tarah-ana / Exodus doublet under the Kings `+50` and hidden-`50` Kish states. | | `16560 × 25/23 = 18000` | Exact Key-of-23 expansion display; exact-ratio handling remains `File_17` controlled. | | `18000 − 16560 = 1440`; `1446 BC → 6 BC = 1440`; `18006 BC → 6 BC = 18000` | Christological extension / terminal completion display; `6 BC` remains `File_13` controlled. | | Hebrew scribal `+50` awareness hypothesis | Shared mathematical grammar / providential synchronization. The file does not claim direct source-critical proof of Hebrew scribal awareness. | | Abraham / dual-Exodus `16560` triad | Biblical-interplay display: `18726 − 16560 = 2166`, `18056 − 16560 = 1496`, and `18006 − 16560 = 1446`. | | Kings `+50` non-cascade claim | Structural inference from solution-fit. The `+50` reaches the schematic `1496 BC` Exodus node but does not cascade backward to Adam without an explicit operator. | | `20886 BC → 1446 BC = 19440 = 270 × 72` | Precessional nine-month display. It supports the bounded Exodus relation without replacing the primary Exodus anchor. | | `27366 BC → 1446 BC = 25920 = 360 × 72` | SKL Long Flood-to-primary-Exodus precessional-year display. It supports Short / Long complementarity without collapsing the Flood states. | | Kalumum terminal alignments | Non-exhaustive solution-fit evidence supporting the terminal anchors: `12600` and `11760 = 24 × 490`. | | `18000 − 1200 = 16800`; `18000 = 50 × 360`; `16800 = 50 × 336` | Jushur-subtracted dual-scale display. The `336` component is a File_12 Priestly Ledger comparison and does not replace the prophetic `360` field. | | Non-exhaustive alignment examples | Corroborative solution-fit evidence, not an exhaustive catalog of all possible Kish-cipher alignments. | | Clean values `18000`, `2160`, `16560`, `16100` | Actual / local harmonic values. They are not Rounded Scaffold states by default. | Argument-control result: The claim-status controls above remain active in this Final source. Arithmetic facts and source-retained SKL data carry the base layer; structural inference, shared mathematical grammar, and providential synchronization are classified as argument layers rather than substitutes for arithmetic or source control. ### 8.1 Opening Kish arithmetic | Display | Arithmetic-control result | Status | |---|---:|---| | `1200 × 360 = 432000` | `1200 × 360 = 432000` | Verified. | | `18600 + 1200 = 19800 = 55 × 360` | `18600 + 1200 = 19800`; `55 × 360 = 19800` | Verified. | | `1200 + 960 = 2160 = 6 × 360` | `1200 + 960 = 2160`; `6 × 360 = 2160` | Verified. | | `1200 + 960 + 670 = 2830` | `1200 + 960 + 670 = 2830` | Verified. | | `670 + 50 = 720` | `670 + 50 = 720` | Verified. | | `670 × 360 = 241200` | `670 × 360 = 241200` | Verified. | | `50 × 360 = 18000` | `50 × 360 = 18000` | Verified. | | `(670 + 50) × 360 = 720 × 360 = 259200` | `720 × 360 = 259200` | Verified. | | `420 + 300 = 720` | `420 + 300 = 720` | Verified. | ### 8.2 Coordinate-family checks | Coordinate family | Arithmetic-control result | Status | |---|---:|---| | `20886 − 2830 = 18056` | `18056 BC` | Verified. | | `20916 − 2830 = 18086` | `18086 BC` | Verified. | | `20888 − 2830 = 18058` | `18058 BC` | Verified. | | `20918 − 2830 = 18088` | `18088 BC` | Verified. | | `18056 − 420 = 17636` | `17636 BC` | Verified. | | `18086 − 420 = 17666` | `17666 BC` | Verified. | | `18058 − 420 = 17638` | `17638 BC` | Verified. | | `18088 − 420 = 17668` | `17668 BC` | Verified. | Fractional-tail control: The endpoint checks above use En-tarah-ana's whole-year `420` component only. The appended `3 months and 3.5 days` remain a fractional textual payload and are not converted into a silent endpoint adjustment. ### 8.3 Reduced 23-kings table and terminal-window checks | Display | Arithmetic-control result | Status | |---|---:|---| | Standard table total | Sum of the `23` visible reigns = `17980`; `20886 − 2906 = 17980` | Verified. | | Hidden-adjusted total | `17980 + 50 = 18030`; `20886 − 2856 = 18030` | Verified. | | Ideal terminal member | `20886 − 2886 = 18000`; `18000 = 50 × 360` | Verified. | | Total-state window | `18030 − 17980 = 50` | Verified. | | Miniature relation | `18000 ÷ 360 = 50` | Verified. | | Hidden drop in table | `18726 − 670 = 18056`, while the hidden variant restarts En-tarah-ana at `18006`; gap = `50` | Verified as an intentional hidden-drop state, not a table error. | | First-six-boundary sum | `1200 + 960 + 670 + 50 + 420 + 300 = 3600` | Verified. | | First-six-boundary span | `20886 − 17286 = 3600 = 60 × 60` | Verified. | | Terminal remainder | `17286 − 2886 = 14400 = 120 × 120` | Verified. | | Partition sum | `3600 + 14400 = 18000` | Verified. | | Tail split | `2936 − 2906 = 30`; `2906 − 2886 = 20`; `2936 − 2886 = 50` | Verified. | | Refined hidden-`50` partition | `670 + 30 + 20 = 720` | Verified. | Table-continuity note: The standard column checks by subtracting each ruler's reign from the prior start date. The hidden-`50` variant column checks by the same rule after the deliberate post-Nangishlishma `50`-year drop is introduced. ### 8.4 Deep-time scalar and Short / Long rail checks | Display | Arithmetic-control result | Status | |---|---:|---| | `262086 − 20886 = 241200 = 670 × 360` | `262086 − 20886 = 241200`; `670 × 360 = 241200` | Verified. | | `262086 − 2886 = 259200 = 720 × 360` | `262086 − 2886 = 259200`; `720 × 360 = 259200` | Verified. | | Short `+30` rail | `20916 − 2936 = 17980` | Verified. | | Short base rail | `20886 − 2906 = 17980` | Verified. | | Long `+30` rail | `27396 − 2886 = 24510` | Verified. | | Long base rail | `27366 − 2856 = 24510` | Verified. | | Terminal separation, `+30` rail | `2936 − 2886 = 50` | Verified. | | Terminal separation, base rail | `2906 − 2856 = 50` | Verified. | | Flood separation, base rail | `27366 − 20886 = 6480` | Verified. | | Flood separation, `+30` rail | `27396 − 20916 = 6480` | Verified. | | Three-month scale | `6480 = 18 × 360 = 90 × 72`; `90 = 3 × 30` | Verified. | | Appended payload display | `3 × 30 + 3.5 = 93.5` days | Verified under the rounded `30`-day month state. | ### 8.5 Etana / Balih and non-exhaustive alignment checks | Display | Arithmetic-control result | Status | |---|---:|---| | Alternate precessional boundary | `20886 − 10136 = 10750`; `150 × 71⅔ = 10750` | Verified; exact form uses `71⅔ = 215/3`. | | Standard precessional boundary | `20886 − 10086 = 10800`; `150 × 72 = 10800`; `30 × 360 = 10800` | Verified. | | Standard-column terminal continuation | `10136 − 2936 = 7200 = 20 × 360` | Verified. | | Hidden-`50` terminal continuation | `10086 − 2886 = 7200 = 20 × 360` | Verified. | | Long Flood to primary Exodus | `27366 − 1446 = 25920`; `360 × 72 = 25920` | Verified. | | Short Flood to primary Exodus | `20886 − 1446 = 19440`; `270 × 72 = 19440`; `270 = 9 × 30` | Verified. | | Kalumum standard start | `15536 − 2936 = 12600` | Verified. | | Kalumum standard endpoint | `14696 − 2936 = 11760`; `24 × 490 = 11760` | Verified. | | Kalumum hidden-`50` start | `15486 − 2886 = 12600` | Verified. | | Kalumum hidden-`50` endpoint | `14646 − 2886 = 11760`; `24 × 490 = 11760` | Verified. | | Kalumum reign separation | `12600 − 11760 = 840` | Verified. | | Jushur-subtracted dual scale | `18000 − 1200 = 16800`; `18000 = 50 × 360`; `16800 = 50 × 336` | Verified. | ### 8.6 Terminal square-chain arithmetic checks | Display | Arithmetic-control result | Status | |---|---:|---| | Enmebaragesi | `900 = 30^2` | Verified. | | Aga of Kish | `625 = 25^2` | Verified. | | Mesh-ki-ang-gasher | `324 = 18^2` | Verified. | | Three-reign transition sum | `900 + 625 + 324 = 1849`; `43^2 = 1849` | Verified. | ### 8.7 Biblical-interplay arithmetic checks | Display | Arithmetic-control result | Status | |---|---:|---| | Moses-birth lock | `18086 − 1526 = 16560`; `10 × 1656 = 16560` | Verified. | | Danielic capstone | `18058 − 1958 = 16100`; `7 × 2300 = 16100` | Verified. | | Historical Temple-to-Exodus display | `966 + 480 = 1446 BC` | Verified as backward BC movement from Temple foundation to Exodus. | | Schematic Temple-to-Exodus display | `1016 + 480 = 1496 BC` | Verified as File_08 schematic `+50` display. | | Exodus doublet, schematic track | `18056 − 1496 = 16560`; `46 × 360 = 16560` | Verified. | | Exodus doublet, primary track | `18006 − 1446 = 16560`; `46 × 360 = 16560` | Verified. | | Key-of-23 expansion | `16560 × 25/23 = 18000` | Verified exactly: `16560 ÷ 23 = 720`; `720 × 25 = 18000`. | | Expansion gap | `18000 − 16560 = 1440` | Verified. | | Exodus-to-Christ terminal span | `1446 − 6 = 1440` | Verified as same-side BC span. | | En-tarah-ana hidden-`50` to Christ terminal | `18006 − 6 = 18000 = 50 × 360` | Verified. | | Abraham landing | `18726 − 16560 = 2166` | Verified. | | Schematic Exodus landing | `18056 − 16560 = 1496` | Verified. | | Primary Exodus landing | `18006 − 16560 = 1446` | Verified. | Arithmetic-boundary note: The author has clarified the Shem-death node-class: `1956/1958 BC` are MT no-`+60 Terah`, Gear 1 / Gear 2 respectively. arithmetic-control review verified the visible Gear 2 display `18058 − 1958 = 16100` and `7 × 2300 = 16100`; argument-control layer preserves `1956 BC` as the Gear 1 companion without substituting it into the active Danielic capstone. ## Audit Notes Audit note 1: The relation between the selected En-tarah-ana coordinates `18086 BC`, `18058 BC`, `18056 BC`, and `18006 BC` is now state-classified, but the full SKL source derivation remains dependency-controlled by `File_21` / `File_34`. Audit note 2: The author-decision layer resolves the source phrase “one-month straddle” as local File_24 language for the SKL `+30 Apparent Mode` rail. It is not a separate operator, date correction, tolerance, or replacement for File_21 / File_34 rail terminology. Audit note 3: The En-tarah-ana fractional-tail datum explains why En-tarah-ana matters, but it does not by itself derive the coordinate quartet. The `3 months` and `3.5 days` remain a textual fractional payload, not a silent whole-year endpoint adjustment. Audit note 4: Shem death is clarified by author direction: `1956 BC` and `1958 BC` are MT no-`+60 Terah`, Gear 1 and Gear 2 respectively. `File_24` uses the Gear 2 / Shem-axis `1958 BC` endpoint for `18058 − 1958 = 16100` and preserves `1956 BC` as the Gear 1 companion. Audit note 5: The hidden-`50` drop at Nangishlishma remains a solution-fit argument under a conjectural cipher premise. The `+50` allows the table to align with `720`, `18000`, `3600 + 14400`, and related scaled displays. It does not prove direct scribal intent by itself. Audit note 6: Public SKL translation / summary sources may report the First Dynasty of Kish total as `24510` years, `3 months`, and `3.5` days, while this file uses the repository operating state `17980` years, `3 months`, and `3.5` days. The Final source treats these as complementary SKL Short / Long source-state displays, not contradictions. Audit note 7: The terminal square-chain clue is preserved as structural inference / probable authorial design under the conjectural cipher premise. Mesh-ki-ang-gasher is classified as the first ruler listed under the First rulers of Uruk after Kish is defeated and kingship is taken to E-anna. He must not be counted as a 24th Kish king. Audit note 8: The phrase “first six kings” is authorial boundary shorthand. The active display reaches `17286 BC`, the hidden-`50` variant start of Puannum, after completed Jushur through Babum plus the hidden `50`. Audit note 9: The `1496 BC` Exodus display is a schematic Kings `+50` state generated from the File_08 schematic Temple pivot at `1016 BC`. It does not replace the primary `1446 BC` Exodus anchor. Audit note 10: The Hebrew scribal `+50` awareness claim remains a shared mathematical grammar / providential synchronization hypothesis. The local proof available is solution-fit, not a source statement that such awareness existed. Audit note 11: The terminal-tail perspective is foregrounded as `2936 BC → 2906 BC → 2886 BC`, giving `30 + 20 = 50`. The `2856 BC` lower hidden-`50` base rail remains valid but is not the preferred tail explanation in the `23`-kings cipher section. Audit note 12: The `6480` Flood-level Short / Long separation is a nested scale-state: `6480 = 18 × 360 = 90 × 72`; `90 = 3 × 30`. The three-month interpretation is structural inference / solution-fit evidence and does not convert the En-tarah-ana textual `3 months and 3.5 days` into ordinary whole-year arithmetic. Audit note 13: The author-supplied SKL / Bible merger diagram is retained as source-context for rail and terminal-anchor distinctions. It should not replace `File_21` / `File_34` source derivation in final source-control. Audit note 14: The `18000 − 1200 = 16800 = 50 × 336` display opens a Priestly `336`-day Ledger comparison by dependency. It is a companion scale-state and must not replace `18000 = 50 × 360`. Audit note 15: The final-source external source-control link is the public Sumerian King List page. It is sufficient for public source-context and provisional citation control, but primary SKL / Berossus derivation remains with `File_21` / `File_34`. ## Unresolved Issues Post-equalization pressure-test note: No author-decision blocker, arithmetic blocker, or publication-clean blocker remains after this sampled File_24 pressure test. The retained items below are dependency-boundary / source-control awareness notes only. No author-decision blockers remain after Finalization. Remaining source-critical derivation details are dependency-boundary notes for `File_21` / `File_34` and may be tightened only in a later publication-source upgrade or cross-file source-control update. ## Recommended Cross-File Updates Author confirmation status: The author has confirmed the recommended cross-file updates as accepted carry-forward items. These are not applied to other repository files inside `File_24`; they should be carried to the appropriate glossary, state-register, or dependency-control update pass. Post-equalization pressure-test note: this carry-forward list is not a publication hold for File_24. - Add `Shem death Gear 1/Gear 2 state` for `1956/1958 BC` as MT no-`+60 Terah` Gear 1 / Gear 2, with `1958 BC` selected for the File_24 Danielic capstone. - Add `File_24 re-scoped Kish-cipher state` to the project glossary or state register. - Add `First Dynasty of Kish 23-kings cipher state`. - Add `File_24 conjectural cipher-premise state`. - Add `Jushur post-Flood repair state` for `1200 × 360 = 432000` and `18600 + 1200 = 19800 = 55 × 360`. - Add `Kullassina-bel precessional-month state` for `1200 + 960 = 2160`. - Add `Nangishlishma hidden-50 riddle state` for the `670 + 50 = 720` partition and the reduced 23-kings table. - Add `En-tarah-ana / Babum 720 state` for `420 + 300 = 720`. - Add `first-six-boundary / 3600-14400 partition state` for `20886 BC → 17286 BC = 3600` and `17286 BC → 2886 BC = 14400`. - Add `30 + 20 terminal-tail state` for `2936 BC`, `2906 BC`, and `2886 BC`, while preserving `2856 BC` as a lower hidden-`50` base rail. - Add `SKL Short / Long complementary variant state` for `17980` and `24510` as harmonious SKL total states. - Add `universal SKL +30 rail state` for Short and Long SKL date-pairs. - Add `SKL appended 93.5-day fractional-payload state` for `3 months + 3.5 days`. - Add `6480 three-month scale state` for `6480 = 18 × 360 = 90 × 72` and `90 = 3 × 30`. - Add `SKL Long Flood-to-Exodus precessional-year state` for `27366 BC → 1446 BC = 25920 = 360 × 72`. - Add `Kalumum terminal-alignment state` for the `12600 / 11760` rows to `2936/2886 BC`. - Add `Jushur-subtracted 50-year dual-scale state` for `18000 − 1200 = 16800`, `18000 = 50 × 360`, and `16800 = 50 × 336`. - Add `non-exhaustive alignment-support state` as an argument-scope guard for selective Kish-cipher examples. - Add `nested SKL scaling-law state` for the relation between the terminal `50`, the `30 + 20` tail, and the Flood-level `6480` separation. - Add `Etana / Balih precessional boundary state` for `10136/10086 BC`, `10750`, `10800`, and the `150 × 71⅔` / `150 × 72` boundary displays. - Add `670 + 30 + 20 partition state` as a refinement of the Nangishlishma hidden-`50` riddle. - Add `First Dynasty of Kish terminal total-state window` for `17980`, `18000`, `18030`, and `50`. - Add `terminal square-chain clue state` for Enmebaragesi `900`, Aga of Kish `625`, Mesh-ki-ang-gasher `324`, and the total `1849`. - Add `Kish-to-Uruk transition square state` to preserve the cross-dynasty boundary. - Add `SKL Flood / Kish beginning rail-pair state` with the displays `20886/20916 BC` and `20888/20918 BC`. - Add `En-tarah-ana coordinate quartet state` for `18056/18086 BC` and `18058/18088 BC`. - Add `En-tarah-ana endpoint / Babum-start quartet state` for `17636/17638/17666/17668 BC`. - Add `Alulim-to-Ubara-Tutu 670 × 360 state` for `262086 BC → 20886 BC = 241200`. - Add `720 × 360 completion state` for `262086 BC → 2886 BC = 259200`. - Add `En-tarah-ana fractional-tail carrier` as a state label linking `File_23`, `File_24`, `File_21`, and `File_34`. - Confirm in `File_21` / `File_34` whether `18056/18086 BC`, `18058/18088 BC`, the hidden-`50` variant `18006 BC`, `17286 BC`, and the endpoint / terminal displays should be indexed as formal En-tarah-ana / Kish-sequence states. - Add `Kings +50 / Exodus doublet state` for `966/1016 BC`, `1446/1496 BC`, and the File_08 schematic ledger relation. - Add `Abraham / dual-Exodus 16560 triad state` for `18726 BC → 2166 BC`, `18056 BC → 1496 BC`, and `18006 BC → 1446 BC`. - Add `Kings +50 non-cascade state` for the claim that `1496 BC` is a temporary schematic Exodus node and not an Adamward cascade. - Add `precessional nine-month Exodus state` for `20886 BC → 1446 BC = 19440 = 270 × 72`. - Add `Nangishlishma-start / Abraham lock state` for `18726 BC → 2166 BC = 16560`. - Add `File_24 16560-to-18000 Key-of-23 expansion state` for `16560 × 25/23 = 18000`. - Add `File_24 Christological 1440 extension state` for `18000 − 16560 = 1440`, `1446 BC → 6 BC = 1440`, and `18006 BC → 6 BC = 18000`. - Add `Sumerian-Hebrew +50 shared-grammar hypothesis state` as a structural-inference / providential-synchronization label, not as proof of direct scribal dependence. - Confirm in `File_08` / `File_18` whether `1496 BC` should be indexed as a schematic +50 Exodus display derived from `1016 BC + 480`. - Confirm in `File_01` whether `2166 BC` should be indexed locally in `File_24` as the Abraham landing point of the `18726 BC → 2166 BC = 16560` display. - Confirm in `File_17` whether the `19440 = 270 × 72` display should be indexed as a precessional nine-month display or a more generic precessional component display. - Confirm in `File_17` whether `10750 = 150 × 71⅔` and `10800 = 150 × 72` should be indexed as alternate / standard precessional-boundary pair displays. - Confirm in `File_21` / `File_34` whether the `2936/2906/2886 BC` terminal-tail perspective should be indexed as the preferred `23`-kings tail state, with `2856 BC` retained as the lower hidden-`50` base rail. - Confirm in `File_13` whether `File_24` should label `6 BC` specifically as the pre-existent Son / Son-of-God New Creation anchor. - Record that `File_24` uses `16560 = 10 × 1656` as a distinct biblical-interplay example state from any other `16560` harmonic elsewhere. - `File_26 companion bridge state` is now registered in `File_24`; future project-state registers may cite `File_26` for the `18726 BC` pre-branching bridge, `8640/8600`, `18766/18756 BC`, Pillar, and remote `434886 BC` displays. - `File_34 post-final citation-control state` is now registered in `File_24`; future project-state registers should cite `File_34 Final; post-final pressure tested` for full SKL / Berossus derivation, paired slash-display arithmetic, phase-chain vocabulary, and File_34-specific corridor controls without importing those systems into File_24 by default. ## 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 arithmetic, anchors, modal states, node-classes, sign conventions, operators, slash-pairs, ranges, envelopes, Mirror protocols, Machine Guards, claim-status labels, theological claims, or dependency boundaries are changed. Final pressure-test status is preserved in the file header. Detailed pressure-test records are archived rather than repeated in the public file body.