Independent preparation: File60 and the C531 grammar
Prepared from the full supplied File60, the C531 checkpoint and synthesis, with targeted checks of Files09/18. This is a preparation memo, not an executed numbered research step or a canonical amendment.
Main finding
The 161/299/460 family transfers into the C531 grammar with no new calendar Key. Its important addition is a source-defined genealogy packet, plus an explicitly imported census packet. The chronology can be reduced to an anchored affine coefficient diagram. The census connections additionally use products, quotients, and changed quantity interpretations; they are not simply another regular-to-cumulative projection.
Smallest useful exact packet
For execution only, take Covenant Q=1866 BC, unit u=23, and the source-assigned endpoint coefficients below. This is a compact representation of the source, not a derivation of the coefficient assignments.
| Node | Coordinate formula | BC |
|---|---|---|
| Joseph death | Q−12u | 1590 |
| Levi death | Q−13u | 1567 |
| Conquest terminal, whole-year Nisan display | Q−20u | 1406 |
| Transformed common generation node | Q−300 | 1566 |
| Joshua terminal | Q−500 | 1366 |
Existing E=25/23 and J=300/299 give E(12u)=J(13u)=300, while E(20u)=500. Levi splits the source total as 13u+7u=20u. The original Joseph–Levi separation u is exactly absorbed by their different gains24 and1. This mixed-Key equality is caused by the supplied radius ratio299/276=13/12 and operator ratio E/J=13/12; it is not interchangeability of E and J.
The source-founded biography packet behind these coefficients can be kept explicit:
- Covenant Q=1866; Abraham birth Q+85=1951; Ishmael birth Q−1=1865; Isaac birth Q−15=1851.
- Jacob birth Isaac−60=1791; Jacob call Jacob−77=1714; Jacob death Jacob−147=1644.
- Levi birth1714−10=1704; Levi lifespan137; Joseph birth1714−14=1700; Joseph lifespan110; Ishmael lifespan137.
- Fixed terminal1406; Moses birth1526, Exodus1446, Joshua terminal1366 retain their independent source authority.
This packet derives Joseph/Levi deaths, the shared137 lifespan rectangle, the birth displacement161, the death displacement161, and the Covenant widths276/299. The second161 arm additionally requires the supplied terminal1406. It should not be counted as guaranteed by the equal lifespans alone.
The three147 rails require two source relations, not three independent successes: Isaac–Jacob60 plus Jacob–Levi87 equals Jacob lifespan147; and Levi137−Jacob call-age77=60. Once those are supplied, the three translated147 rails and their60/77 shifts follow. The Joseph294 rail additionally uses Joseph birth1700 and Conquest1406. Its decomposition133+161 is derivative of that placement.
Affine descriptions that preserve the source distinctions
Holding Levi birth1704, the radius161 expands to175 and generates1879. The lower companion radius147 differs by14, because Ishmael and Isaac births differ by14. Thus147/161/175 is a progression at scale7 with coefficients21/23/25. The equality E(161)=175 is operative;147 is supplied by genealogy, not obtained by applying an inverse-of-inverse procedure.
Holding Levi death1567, source Ishmael death1728 expands to1742. The unchanged1406 terminal is336 from1742. This is a hybrid comparison:175 transformed plus161 unchanged. Dilating both original161 arms about1567 would instead generate endpoints1742 and1392 and total350. File60 does not need to replace the1406 source terminal to make its175+161=336 comparison.
The +215, localized−33, and MT-Minimum variants explain the terminal calibration: full-state Levi1782 to Exodus1446 is336; shifting Levi by−33 and terminal by−40 changes the width by+7, giving343; localized1749 to minimum1567 changes it by−182, giving161. The identity161+175=336 is consequent on the supplied215 and40 shifts, not another free operator.
Mirror packet
For the §7 matched phase-pair construction, the common Exodus component makes the three radii simply1446+x for lower Nisan source labels x=1567,1728,1866. Thus3013,3174,3312 preserve differences161,299,138 automatically. Their exact divisibility by23 additionally depends on1446+x≡0 mod23. Here1446≡20 and each x≡3; the congruence is a source placement constraint. Reflection preserves differences, but does not generally create the divisibility.
The family lies in23×{131,138,144}. Hence E multiplies coefficients by25, P uses70/3 times coefficients, and P is integral for138/144 but not131. This is the same residue-domain idea already used for the C531 Keys. The denominator ratios against579600 are algebraic consequences once that census scalar and the source radii are fixed.
Cumulative packet
From Moses1526, stack [137,133,137,147,180,175] in the backward direction to produce Amram1663, Kohath1796, Levi1933, Jacob2080, Isaac2260, Abraham2435. The source Abraham radius to Exodus is989=43×23. E gives1075 and the generated2521; the215 ladder thereafter also needs separately sourced endpoints2091/1876/1661.
The equal270 windows are direct consequences of repeated137 flanking133:137+133=133+137=270. The displayed273 windows add the whole-year Aaron/Moses branch3. Exact3.5 branches instead produce273.5. Likewise the cross-branch Levi width140 becomes140.5 at exact3.5. These are deliberate display-state alternatives, not numerical errors, but every reconstruction must keep them separate.
The Flood4836→Abraham2435 width2401 additionally needs the source Flood envelope member4836. Abraham→Conquest1029 follows from the independently anchored stack. Their sum3430 relates directly to the C531 rounded cumulative Flood–Conquest leg, while their internal split is additional genealogical information. This is a particularly strong next connection to the rounded family.
Census packet and dependency rank
File60 explicitly imports File59's579600,588000,602640,458640,23000,37730 and adjusted census heads. Reconstructing the chronology from File60 does not verify the census derivation. The safest dependency graph has two source branches converging at exact arithmetic comparisons.
| Census comparison | Chronology contribution | Algebraic dependency |
|---|---|---|
| 579600=1260×460=161×3600 | 161 death arm and460 Covenant total | Refactorization once1260/460 known;6–161–6 display is derivative |
| P(579600)=588000=1470×400 | Jacob2006→Return536=1470 | Multiplication/scalar expansion; restoration endpoint independently supplied |
| 602640−144000=458640=637×720 | Abraham2166→Aaron1529=637 and→Exodus1446=720 | Product of widths; Aaron1529 whole-year state, not1529.5 |
| 579600−23000=556600=121×4600 | Levi1567→Exodus1446=121 | Numerical subtraction, distinct from census coordinate translation |
| [1866,1796]−1260=[606,536] | Regular Covenant and cumulative Levi/Kohath | Translation of a mixed node-class pair; not a continuous historical interval |
At the mathematical-description level, bilinear products are an extension to a purely affine operation inventory unless treated as already sourced scalars. This is a useful extension of representation, not a license for searching arbitrary factor pairs.
Source issues and limits
- No proof-bearing elementary arithmetic error was found in the inspected spine, Keys, census factorizations, or ledger equations. This is a focused independent source read, not a claim to replicate File60's historical342/342 or175/175 suites.
- Potential phase provenance issue in §9.3/AppendixC:2436t/2435n BC→AD2165t/2166n gives4600 arithmetically. But AD2165t/2166n is the declared-rule reflection of2166t/2165n BC. If ordinary Abraham2166 is intended as lower-Nisan2166 in2167t/2166n BC, that pair reflects asAD2166t/2167n and the matched spans are4601. File60 does not print the original regular Abraham BC pair here. Preserve4600 as its explicitly supplied execution, and ask a bounded source-phase question before promoting it to a generic application.
- The Terah−33 Machine Guard still calls the scope extension exploratory, although the September header and §4.4.2 promote the bounded Terah-through-Levi corridor. Later substantive scope is controlling; do not globalize−33. This is stale control wording, not failed arithmetic.
- Several File60 outer-envelope examples use1486. The active C531 task retains the user’s removal of that node; those examples should remain source context unless specifically reopened. They are unnecessary for the161/299/460 transfer.
- The exact3.5 priestly branch and integer3 shorthand produce different outputs.273,140,637 through whole-year labels must not silently become exact-phase claims.
- The1714 call/date service convention,536 restoration endpoint, repository Covenant2081→minimum1866 selection, and Joseph/Levi birth timings are source inputs. This memo does not independently establish ancient historical dates or scribal intent.
Ten bounded questions for the sequential lead
- Does the frozen C531 grammar reconstruct the complete Q=1866 coefficient packet without adding a Key, target-fitted pivot, or reversed-number operation?
- How many independent source equalities underlie the three147 rails, the equal137 biography rectangle, and the two161 death arms?
- Can the147/161/175 progression and bilateral175 description be stated with explicit fixed pivots, distinguishing simultaneous dilation from mixed transformed/untransformed comparisons?
- Is the Joseph–Levi common1566 junction exactly the same mixed-Key ratio principle as the earlier Jared/Noah common2926 junction, with different source ratios?
- Does the scoped215/33/40 state-change formula generate161/336/343 while explaining which terminal shifts are independent inputs?
- Which §7 Mirror divisibilities follow from retained differences, and which require the source residues of Exodus and the family endpoints?
- What regular Abraham BC phase pair actually supports File60's4600 cumulative-to-regular Mirror comparison, and can its supplied4600 execution be retained without asserting an unsupported phase identification?
- Does the cumulative stack derive270 and the3430=2401+1029 partition, connecting the same3430 palindrome already operative in the rounded12026 path?
- What minimal extra typed operations or imported scalars are needed to represent census products and quotients while preserving File59's derivation boundary?
- After removing dependent restatements, which source placement constraints remain unexplained, and which now connect regular, cumulative, rounded, Mirror, and census families in one dependency diagram?
These are candidate questions only. The lead should select each after the preceding result and may replace any already resolved question.