# 490d — C532–C551: sequential research record

Research begun27 September2026 in the user’s local timezone; packet dated28 September UTC. Working continuation of C531. No canonical source is changed; second-order inversion and quarantined primers remain deferred.

Each step records a question before its calculation, frozen inputs, exact result, finding, and reassessment. Preparatory source extraction and review were delegated; the numbered sequence was evaluated in order. These are bounded research actions, not independent discoveries.

## C532 — Reconstruct the Covenant partition

**Question.** Does the frozen grammar reconstruct161/299/460 in File60 without selecting a new anchor?

**Sources.** File60 §§0.4,3,5; C531 checkpoint

**Inputs**

```json
{
  "state": "MT Minimum/−215; whole-year principal display",
  "dates": {
    "Covenant": 1866,
    "Ishmael_birth": 1865,
    "Ishmael_death": 1728,
    "Levi_birth": 1704,
    "Levi_death": 1567,
    "Joseph_birth": 1700,
    "Joseph_death": 1590,
    "Exodus": 1446,
    "Conquest": 1406
  },
  "Keys": {
    "E": "25/23",
    "P": "70/69",
    "J": "300/299"
  }
}
```

**Results**

```json
{
  "partition": [
    299,
    161
  ],
  "total": 460,
  "23_coefficients": [
    13,
    7,
    20
  ],
  "converted_parts": {
    "J_left": 300,
    "E_right": 175
  }
}
```

**Finding.** The supplied Covenant–Levi–Conquest partition is299+161=460, with coefficients13+7=20 in23-units. The existing Keys complete the arms to300 and175 without new ratios or anchors.

**Reassessment.** Determine whether the two arms are one uniform dilation or two distinct calendar branches.

## C533 — Uniform and mixed calendar branches

**Question.** Can the completed299 and161 arms be treated as one uniform expansion?

**Sources.** File60 §5; C532

**Inputs**

```json
{
  "arms": [
    299,
    161
  ],
  "E": "25/23",
  "J": "300/299"
}
```

**Results**

```json
{
  "all_E": [
    325,
    175,
    500
  ],
  "all_J": [
    300,
    "2100/13",
    "6000/13"
  ],
  "mixed": [
    300,
    175,
    475
  ]
}
```

**Finding.** Uniform E preserves the partition as325+175=500. The mixed J/E completion is300+175=475 and is a different operation. Shared coefficients do not make the Keys interchangeable; source-declared mixed branches must retain their separate labels.

**Reassessment.** Test the actual common1566 landing where File60 deliberately uses two different Keys.

## C534 — Joseph and Levi converge at1566

**Question.** Does the supplied common landing follow from the frozen anchored operators?

**Sources.** File60 §§5.4–5.5

**Inputs**

```json
{
  "held_Covenant": 1866,
  "Joseph_death": 1590,
  "Levi_death": 1567
}
```

**Results**

```json
{
  "radii": [
    276,
    299
  ],
  "outputs": [
    1566,
    1566
  ],
  "gains": [
    24,
    1
  ],
  "initial_gap": 23
}
```

**Finding.** Joseph’s276 under E and Levi’s299 under J both become300, reaching generated1566. The gains24 and1 close their original23 difference. This is a whole anchored two-route reconstruction, not an identification of the historical deaths.

**Reassessment.** Compare its cross-Key ratio with the earlier Jared/Noah2926 convergence.

## C535 — One coincidence law spans both studies

**Question.** Are1566 and2926 instances of the same calendar-measure condition?

**Sources.** File60 §5; File52c §3.15; C500,C502

**Inputs**

```json
{
  "Covenant_radii": [
    276,
    299
  ],
  "Actual_field_radii": [
    8372,
    8970
  ],
  "year_lengths": [
    336,
    360,
    364
  ]
}
```

**Results**

```json
{
  "Covenant_radius_ratio": "13/12",
  "E_over_J": "13/12",
  "Actual_radius_ratio": "15/14",
  "E_over_P": "15/14",
  "normalized_Covenant": [
    "23/28",
    "23/28"
  ],
  "normalized_Actual": [
    "299/12",
    "299/12"
  ],
  "general_rule": "K_d(s)=K*s/d; equal outputs iff s1/d1=s2/d2"
}
```

**Finding.** The13:12 Covenant pair and15:14 Actual pair express the same normalized-measure equality under different calendar lengths. This unifies their calculation while leaving the supplied radii and held anchors as separate placement facts.

**Reassessment.** Trace the161 spine to the biographical equality that generates it.

## C536 — Equal lives preserve birth and death displacement

**Question.** Which161 equality is forced by the supplied biographies?

**Sources.** File60 §§3.1–3.2

**Inputs**

```json
{
  "Ishmael": [
    1865,
    1728
  ],
  "Levi": [
    1704,
    1567
  ],
  "terminal": 1406
}
```

**Results**

```json
{
  "lifespans": [
    137,
    137
  ],
  "birth_gap": 161,
  "death_gap": 161,
  "terminal_arm": 161,
  "identity": "(B1−L1)−(B2−L2)=(B1−B2)−(L1−L2)"
}
```

**Finding.** Equal137-year lives force equal161 birth/death displacement. The further161 from Levi’s death to the terminal is an additional source placement. Separating these two facts avoids treating the biography rectangle as several independent alignments.

**Reassessment.** Reconstruct the bilateral spine and its expansion with a single held midpoint.

## C537 — Distinguish bilateral expansion from a mixed comparison

**Question.** How do the350 and336 displays arise from the same161 spine?

**Sources.** File60 §§3.3–3.4

**Inputs**

```json
{
  "original_triple": [
    1728,
    1567,
    1406
  ],
  "held_midpoint": 1567
}
```

**Results**

```json
{
  "uniformly_expanded_triple_diagnostic": [
    1742,
    1567,
    1392
  ],
  "uniform_outer_width": 350,
  "one_arm_expanded_with_original_terminal": 336,
  "historical_outer_width": 322
}
```

**Finding.** Both arms expanded give175+175=350. Expanding only the Ishmael arm while retaining the original terminal gives175+161=336. The generated1392 companion is only the algebraic fixed-midpoint display, not a newly admitted historical node.

**Reassessment.** Resolve the147/161/175 progression and its14-unit connection to later clutch operations.

## C538 — The14 gain links reconciliation and clutch scales

**Question.** What common arithmetic underlies147/161/175 and the full/half clutch values?

**Sources.** File60 §§2.6,3.3; File62 dependency note

**Inputs**

```json
{
  "source_values": [
    147,
    161,
    175
  ],
  "calendar_factor": "25/23"
}
```

**Results**

```json
{
  "coefficients_over7": [
    21,
    23,
    25
  ],
  "E_gain": 14,
  "half_relation": {
    "input": "161/2",
    "output": "175/2",
    "gain": 7
  },
  "center_identity": 322
}
```

**Finding.** The progression is7×(21,23,25). E raises161 to175 by14; halving gives80.5→87.5 by7. This provides a value-level bridge to T14/H7, while their chronology domains still require the File61/62 source rules.

**Reassessment.** Reconstruct the ordered147 rails, testing translation of both endpoints rather than isolated widths.

## C539 — The three147 rails form a translated object

**Question.** Do the three direct147 rails share an endpoint-by-endpoint reconstruction?

**Sources.** File60 §§2.3–2.4

**Inputs**

```json
{
  "pairs": [
    [
      1851,
      1704
    ],
    [
      1791,
      1644
    ],
    [
      1714,
      1567
    ]
  ],
  "roles": [
    "Isaac birth/Levi birth",
    "Jacob birth/death",
    "Jacob call/Levi death"
  ]
}
```

**Results**

```json
{
  "widths": [
    147,
    147,
    147
  ],
  "translations": [
    [
      60,
      60
    ],
    [
      77,
      77
    ]
  ],
  "outer_translation": [
    137,
    137
  ],
  "overlapping_gap_sequence": [
    77,
    70,
    77
  ]
}
```

**Finding.** The whole first pair translates by−60 and then−77. Equal widths follow from these paired translations; the77|70|77 ordering generates the two overlapping147 windows. The central70 remains the separate call-to-death unit.

**Reassessment.** Place Joseph’s double147 in the same ordered chain and identify the extra endpoint placement.

## C540 — Joseph’s double147 and the household bracket

**Question.** How does the14-year household interval fit inside the larger lattice?

**Sources.** File60 §§2.5,2.7

**Inputs**

```json
{
  "Jacob_call": 1714,
  "Levi_birth": 1704,
  "Joseph_birth": 1700,
  "Levi_death": 1567,
  "Conquest": 1406
}
```

**Results**

```json
{
  "household_parts": [
    10,
    4
  ],
  "call_Levi_death_parts": [
    14,
    133
  ],
  "Joseph_Conquest_parts": [
    133,
    161
  ],
  "double147": 294
}
```

**Finding.** The14=10+4 bracket lies inside the147 call-to-Levi-death span, leaving133. Joseph’s294 then decomposes as133+161=2×147. This joins the household and Covenant structures through an existing hinge, while its double-portion interpretation remains a separate reading.

**Reassessment.** Test the full biography translations linking the principal, full430 and localized−33 states.

## C541 — Levi’s state changes explain three terminal forms

**Question.** How do161,336 and343 arise while the same137-year biography is preserved?

**Sources.** File60 §§1.3,3.4–3.5,8

**Inputs**

```json
{
  "principal": [
    1704,
    1567,
    1406
  ],
  "full430": [
    1919,
    1782,
    1446
  ],
  "localized_minus33": [
    1886,
    1749,
    1406
  ]
}
```

**Results**

```json
{
  "states": {
    "principal": {
      "life": 137,
      "terminal_span": 161
    },
    "full430": {
      "life": 137,
      "terminal_span": 336
    },
    "localized_minus33": {
      "life": 137,
      "terminal_span": 343
    }
  },
  "span_changes": [
    175,
    7
  ],
  "biography_translations": [
    215,
    -33
  ]
}
```

**Finding.** Every biography retains137. The principal-to-full comparison adds215 to Levi but40 to the held terminal, raising161 to336 by175. The localized comparison shifts Levi−33 while changing the terminal back40, raising336 to343 by7. These are controlled state-and-anchor changes, not one interchangeable terminal date.

**Reassessment.** Use the genealogical27/4/23 identity to connect consecutive Covenant coefficients to actual lifespans.

## C542 — The23 death gap has a local biographical cause

**Question.** Can the consecutive12/13 Covenant coefficients be explained without assuming their death gap independently?

**Sources.** File60 §§6.1,6.6

**Inputs**

```json
{
  "Levi_life": 137,
  "Joseph_life": 110,
  "births": [
    1704,
    1700
  ],
  "Covenant": 1866
}
```

**Results**

```json
{
  "lifespan_difference": 27,
  "birth_offset": 4,
  "death_offset": 23,
  "death_dates": [
    1590,
    1567
  ],
  "Covenant_coefficients": [
    12,
    13
  ]
}
```

**Finding.** The23-year death separation is27−4: the lifespan difference minus the birth offset. Hence the consecutive coefficients12 and13 share a local source mechanism. The absolute12 placement still depends on the supplied Covenant and Joseph dates.

**Reassessment.** Reconstruct the larger300/500 terminal sequence from those generated and historical nodes.

## C543 — The Covenant completion generates an ordered terminal family

**Question.** How do the common300 landing and whole460 expansion connect to Moses and Joshua?

**Sources.** File60 §§6.2,6.4–6.5

**Inputs**

```json
{
  "path": [
    1866,
    1566,
    1526,
    1406,
    1366
  ],
  "roles": [
    "Covenant",
    "generated Joseph/Levi completion",
    "Moses birth",
    "Conquest",
    "Joshua death"
  ]
}
```

**Results**

```json
{
  "gaps": [
    300,
    40,
    120,
    40
  ],
  "Covenant_Conquest": 460,
  "E_held_Covenant_result": 1366,
  "remaining_after300": 200
}
```

**Finding.** The ordered300|40|120|40 sequence is reconstructed without moving the historical Moses/Joshua anchors. E sends the supplied460 Covenant–Conquest span to500, agreeing with Joshua’s supplied1366 endpoint. The source-role agreement adds information beyond the scalar500 conversion.

**Reassessment.** Test the cross-modal1260 translation that connects the Covenant family to exile and return.

## C544 — Covenant and cumulative boundary share a1260 translation

**Question.** Does one admitted translation reconstruct the exile/return pair with both endpoint roles retained?

**Sources.** File60 §8.4

**Inputs**

```json
{
  "regular_Covenant": 1866,
  "cumulative_Levi_Kohath": 1796,
  "translation": -1260,
  "targets": [
    606,
    536
  ]
}
```

**Results**

```json
{
  "source_width": 70,
  "translated_pair": [
    606,
    536
  ],
  "target_width": 70,
  "translation_each": [
    1260,
    1260
  ]
}
```

**Finding.** The mixed regular/cumulative pair translates to606/536 with its70 width preserved. The translation carries a typed pair; it does not turn the cumulative boundary into a regular event. This is a concrete cross-mode relationship under the existing grammar.

**Reassessment.** Reconstruct cumulative Abraham’s23/989 interface and its relation to the previously selected Creation bridge.

## C545 — Cumulative Abraham scales the Creation bridge

**Question.** How does the989 unit connect this new family to the previous Actual Creation comparison?

**Sources.** File60 §9.2; File22 §5.1; C481,C494

**Inputs**

```json
{
  "cumulative_Abraham": 2435,
  "regular_FloodG2": 2458,
  "Exodus": 1446,
  "Actual_Creation_gap": 9890,
  "comparison_targets": [
    2091,
    1876,
    1661,
    1446
  ]
}
```

**Results**

```json
{
  "Flood_Abraham_gap": 23,
  "Abraham_Exodus": 989,
  "Creation_gap_multiple": 10,
  "expanded_coordinate": 2521,
  "target_spans": [
    430,
    645,
    860,
    1075
  ],
  "gain": 86
}
```

**Finding.** The cumulative Abraham–Exodus989 is one tenth of the9890 Actual Creation bridge. Its E expansion to1075 generates2521 and the supplied430/645/860/1075 comparison ladder. The tenfold link is an exact source relation; the ladder outputs share one expansion.

**Reassessment.** Reconstruct the3430 Flood-to-Conquest leg through Abraham while retaining the source-state distinction.

## C546 — The3430 leg links the Covenant and rounded studies

**Question.** Can the shared3430 duration be reconstructed from the cumulative lifespan trunk?

**Sources.** File60 §9.5; File51a §16.2; File52c §3.3

**Inputs**

```json
{
  "upper_Actual_Flood": 4836,
  "Actual_cumulative_Abraham": 2435,
  "Conquest": 1406,
  "lifespans": [
    175,
    180,
    147,
    137,
    133,
    137,
    120
  ],
  "Rounded_Flood_label": 4836
}
```

**Results**

```json
{
  "lifespan_sum": 1029,
  "outer_partition": [
    2401,
    1029
  ],
  "total": 3430,
  "factorizations": [
    "2401=49²",
    "1029=7×147",
    "3430=70×49"
  ],
  "shared_label_note": "Actual upper-envelope Flood and Rounded Moses-line Flood share4836; they remain distinct source states"
}
```

**Finding.** The1029 lower leg is regenerated by the seven lifespans; together with the supplied upper2401 it gives3430. This explains a source-level interface with the rounded primary path’s unchanged3430 leg. It does not license inserting Actual Abraham as a new rounded reversal breakpoint.

**Reassessment.** Reconstruct the repeated270 Levitical windows before examining their census comparison.

## C547 — Repeated270 windows are caused by ordered lifespans

**Question.** What generates the two Levitical270 windows and their phase companions?

**Sources.** File60 §§9.6–9.8

**Inputs**

```json
{
  "trunk": [
    1933,
    1796,
    1663,
    1526
  ],
  "lifespans": [
    137,
    133,
    137
  ],
  "phase_offsets": [
    0,
    3,
    "7/2"
  ]
}
```

**Results**

```json
{
  "two_windows": [
    270,
    270
  ],
  "two_window_anatomy": [
    [
      137,
      133
    ],
    [
      133,
      137
    ]
  ],
  "one_endpoint_phase_windows": [
    270,
    273,
    "547/2"
  ],
  "both_endpoint_translation": "keeps270",
  "cross_branch_Levi_life": [
    137,
    140,
    "281/2"
  ]
}
```

**Finding.** The repeated137 flank makes137+133 and133+137 equal270. Moving only the earlier endpoint adds the chosen3 or3.5 branch offset, giving273 or273.5; moving both preserves270. Thus the repeated value is source-order conservation, while the companion depends on the stated phase display.

**Reassessment.** Test how the chronology joins imported census scalars without claiming a new census derivation.

## C548 — Chronological and census quantities meet through scalar factorization

**Question.** What does the supplied579600 factorization add to the construction grammar?

**Sources.** File60 §§1,8.1,10; File59 provenance imported through File60

**Inputs**

```json
{
  "imported_File59_scalar": 579600,
  "chronological_spine": 161,
  "macro_factors": [
    1260,
    460
  ],
  "P": "70/69"
}
```

**Results**

```json
{
  "factorizations": [
    579600,
    579600
  ],
  "P_scalar": 588000,
  "expanded_factorizations": [
    588000,
    588000,
    588000
  ],
  "operation_type": "typed numerical product/refactorization of imported census scalar; not a calendar conversion of people into years"
}
```

**Finding.** The same579600 factors through161 or1260×460 and expands under P to588000. Products and quotients belong in an explicit scalar-comparison layer alongside the chronological maps. The arithmetic is reconstructed; File59’s underlying census derivation is not re-audited here.

**Reassessment.** Connect the458640 census comparison to the already established common calendar measure.

## C549 — The458640 comparison reuses calendar measure

**Question.** Which parts of the637×720 identity follow from existing calendar factors?

**Sources.** File60 §8.5; C500; File63 §9.7 by preparation

**Inputs**

```json
{
  "whole_year_Abraham_Aaron": 637,
  "Abraham_Exodus": 720,
  "imported_counts": [
    602640,
    144000
  ],
  "previous_seed": 12558
}
```

**Results**

```json
{
  "chronological_factors": [
    637,
    720
  ],
  "products": [
    458640,
    458640,
    458640
  ],
  "imported_remainder": 458640,
  "prior_calendar_volume": 4586400,
  "numerical_ratio": 10,
  "exact_phase_diagnostic": "1273/2"
}
```

**Finding.** The637×720 product equals1260×364 and1274×360; the prior12558 calendar volume is numerically ten times this458640 scalar. This joins the factor systems without identifying their units. The637 factor uses Aaron’s whole-year1529 display; exact1529.5 gives636.5 and must remain distinct.

**Reassessment.** Reconstruct the1470 restoration span as the source placement behind the588000 refactorization.

## C550 — Jacob’s lifetime and restoration scale

**Question.** Does the source’s tenfold1470 relation preserve a whole ordered partition?

**Sources.** File60 §8.2

**Inputs**

```json
{
  "Jacob_birth": 2006,
  "Jacob_death": 1859,
  "Exodus": 1446,
  "Exile": 606,
  "Return": 536
}
```

**Results**

```json
{
  "lifetime_and_remainder": [
    147,
    1323
  ],
  "seventy_unit_partition": [
    8,
    12,
    1
  ],
  "total": 1470,
  "census_scalar_factor": 400
}
```

**Finding.** The supplied endpoints give147+1323=1470 and the ordered8+12+1 partition in70-units. This supplies chronological placement for588000=1470×400. The scalar refactorization alone would not select the536 endpoint or the8/12/1 ordering.

**Reassessment.** Consolidate the successful Covenant transfer and choose the next source-generated family.

## C551 — Reconstruct the principal Covenant network from local relations

**Question.** Can the whole selected regular network be generated from a declared local packet rather than separate date lookups?

**Sources.** File60 §§2–6; C532–C550

**Inputs**

```json
{
  "Covenant": 1866,
  "son_offsets": [
    1,
    15
  ],
  "Ishmael_Levi_birth_gap": 161,
  "Levi_life": 137,
  "Joseph_birth_offset": 4,
  "Joseph_life": 110,
  "Isaac_Jacob_gap": 60,
  "Jacob_life": 147,
  "Jacob_call_age": 77,
  "Levi_terminal_gap": 161
}
```

**Results**

```json
{
  "generated_network": {
    "Ishmael_birth": 1865,
    "Ishmael_death": 1728,
    "Isaac_birth": 1851,
    "Jacob_birth": 1791,
    "Jacob_death": 1644,
    "Jacob_call": 1714,
    "Levi_birth": 1704,
    "Levi_death": 1567,
    "Joseph_birth": 1700,
    "Joseph_death": 1590,
    "terminal": 1406
  },
  "scope": "source-conditioned reconstruction; local packet retains source data and chosen161 placements"
}
```

**Finding.** Eleven coordinates reconstruct coherently from one local packet. The reused grammar now explains the Covenant partition, biography rectangles, common1566 and terminal500 family. The next informative extension is File61’s source-defined cumulative clutch and Joseph collateral construction.

**Reassessment.** Rebuild File61/62’s complete phase-and-clutch root family, keeping terminal event dates fixed.

## Evidence

Current completion:C532–C551. The accompanying archive includes the sequential journal, exact scripts, source snapshots and independent reviews. Some carried source snapshots provide future or inherited context; only the sections cited by a step are claimed as its evidence.