# 490d — C572–C591: 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.

## C572 — Close the Actual-to-Rounded cumulative square

**Question.** Does the J image followed by the source pair adjustment recover both Rounded endpoints?

**Sources.** File63 §9.7; File51a; latest File52c

**Inputs**

```json
{
  "Actual": [
    14004,
    1446
  ],
  "Rounded": [
    14006,
    1406
  ],
  "pair_translation": 2
}
```

**Results**

```json
{
  "Actual_span": 12558,
  "J_pair": [
    14004,
    1404
  ],
  "translated_pair": [
    14006,
    1406
  ],
  "span_gain": 42,
  "endpoint_change": [
    2,
    -40
  ]
}
```

**Finding.** The Actual Creation–Exodus pair maps by anchored J to14004/1404, then by a declared+2 pair translation to Rounded Creation–Conquest14006/1406. This is an exact interface between differently typed endpoint pairs.

**Reassessment.** Relate this pair interface to the separate12026 regular/cumulative bridge.

## C573 — Connect the two Actual/Rounded interfaces

**Question.** Can the endpoint square and weighted bridge coexist without conflating their terminals?

**Sources.** C531 synthesis; File63 §9.7; latest File52c

**Inputs**

```json
{
  "Creation_regular_Actual": 4114,
  "Creation_cumulative_Actual": 14004,
  "Creation_regular_Rounded": 4106,
  "Creation_cumulative_Rounded": 14006
}
```

**Results**

```json
{
  "weighted_anchors": [
    12026,
    12026
  ],
  "Creation_changes": [
    2,
    -8
  ],
  "weighted_change": 0,
  "interfaces": [
    "Creation/Exodus→Creation/Conquest",
    "Actual/rounded regular+cumulative Creation→12026"
  ]
}
```

**Finding.** Both interfaces share the cumulative Creation change14004→14006. The regular Creation change4114→4106 cancels it in the weighted12026 bridge; the terminal change1446→1406 instead contributes to the42-year span gain. The maps meet at a node but do different work.

**Reassessment.** Reconstruct the common integral Key lattice across the newly linked spans.

## C574 — Generate the common integral Key family

**Question.** Do Noah, Creation and macro scalar seeds share one normal form?

**Sources.** File63 §§6,9; C531 Noah family

**Inputs**

```json
{
  "multipliers": [
    10,
    14,
    160
  ],
  "base": 897
}
```

**Results**

```json
{
  "n_input_J_P_E": [
    [
      10,
      8970,
      9000,
      9100,
      9750
    ],
    [
      14,
      12558,
      12600,
      12740,
      13650
    ],
    [
      160,
      143520,
      144000,
      145600,
      156000
    ]
  ],
  "normal_form": [
    897,
    900,
    910,
    975
  ]
}
```

**Finding.** All three seeds lie on897n, with J/P/E outputs900n/910n/975n. The newly completed E outputs for File63 are algebraic diagnostics, not additional source-appointed event dates.

**Reassessment.** Determine which gains and calendar volumes are automatic consequences of this normal form.

## C575 — Compress Key gains and day volumes

**Question.** Which apparent agreements follow automatically from the897 normal form?

**Sources.** File12 calendrical physics; File63; C574

**Inputs**

```json
{
  "input": 897,
  "outputs": [
    900,
    910,
    975
  ],
  "calendar_days": [
    364,
    360,
    336
  ]
}
```

**Results**

```json
{
  "gain_coefficients": [
    3,
    13,
    78
  ],
  "output_gap_coefficients": [
    10,
    65,
    75
  ],
  "day_volume_coefficient": [
    327600,
    327600,
    327600
  ],
  "lattice_condition": "integer S divisible by lcm(299,69,23)=897"
}
```

**Finding.** The gains3n/13n/78n, output gaps10n/65n/75n and common327600n day volume are consequences of one calibrated lattice. They should be counted as dependent outputs of that structure.

**Reassessment.** Reconstruct the smaller quarter-carrier ladder that supplies483.

## C576 — Generate the quarter-carrier ladder

**Question.** Can all five source scales follow from40→40.25?

**Sources.** File63 §§1.1–1.4,4.6

**Inputs**

```json
{
  "multipliers": [
    3,
    10,
    12,
    30,
    300
  ],
  "base_pair": [
    40,
    "161/4"
  ]
}
```

**Results**

```json
{
  "multiplier_base_carrier_excess": [
    [
      3,
      120,
      "483/4",
      "3/4"
    ],
    [
      10,
      400,
      "805/2",
      "5/2"
    ],
    [
      12,
      480,
      483,
      3
    ],
    [
      30,
      1200,
      "2415/2",
      "15/2"
    ],
    [
      300,
      12000,
      12075,
      75
    ]
  ],
  "ratio": "161/160"
}
```

**Finding.** One source replacement40→40.25 generates the entire ladder, including480→483 and12000→12075. The quarter-phase carrier is a scalar construction, not an additional biological generation unit.

**Reassessment.** Compose the carrier replacement with existing Keys.

## C577 — Connect480483490 through composite factors

**Question.** Which effective ratios summarize the declared two-stage carrier routes?

**Sources.** File63 §1.3; C576

**Inputs**

```json
{
  "carrier_ratio": "161/160",
  "base": 480
}
```

**Results**

```json
{
  "effective_P_E_factors": [
    "49/48",
    "35/32"
  ],
  "carrier_P_E_outputs": [
    483,
    490,
    525
  ]
}
```

**Finding.** The source carrier replacement followed by P gives49/48 overall, taking480→483→490. With E it gives35/32 and525. These summarize ordered admitted operations; they do not add universal Keys.

**Reassessment.** Test whether one translated cell reconstructs the Creation-to-Temple family.

## C578 — Generate the translated Creation cell

**Question.** Does the483 carrier preserve the complete3|2|2 cell at all supplied levels?

**Sources.** File63 §§7.1–7.6

**Inputs**

```json
{
  "cell": [
    14011,
    14008,
    14006,
    14004
  ],
  "counts": [
    25,
    26,
    27
  ],
  "carrier": 483
}
```

**Results**

```json
{
  "translated_cells": [
    [
      1936,
      1933,
      1931,
      1929
    ],
    [
      1453,
      1450,
      1448,
      1446
    ],
    [
      970,
      967,
      965,
      963
    ]
  ],
  "invariant_gaps": [
    3,
    2,
    2
  ],
  "role_rule": "only source-selected coordinates receive event names"
}
```

**Finding.** One four-coordinate cell and three integer translations generate all twelve landings. Selected Levi, Exodus and Temple roles are source inputs; the remaining generated coordinates are not independent historical hits.

**Reassessment.** Apply the480/483/490 family to the source Flood envelope.

## C579 — Transport the complete Flood envelope

**Question.** What does changing the carrier do to both ends of the seven-year Flood cell?

**Sources.** File63 §8

**Inputs**

```json
{
  "envelope": [
    4836,
    4829
  ],
  "counts": 7,
  "carriers": [
    480,
    483,
    490
  ]
}
```

**Results**

```json
{
  "images": [
    [
      1476,
      1469
    ],
    [
      1455,
      1448
    ],
    [
      1406,
      1399
    ]
  ],
  "successive_displacements": [
    21,
    49
  ],
  "total_displacement": 70
}
```

**Finding.** The three carriers translate the whole7-year envelope to1476/1469,1455/1448 and1406/1399. The21+49=70 displacement is generated by carrier differences, while the envelope shape is preserved.

**Reassessment.** Connect the same3430 translation to Shem/Jacob and Flood/Conquest.

## C580 — Join Shem and Flood to the regular chronology

**Question.** Does one carrier translation explain both source horizontal bridges?

**Sources.** File63 §8; C546; latest File52c

**Inputs**

```json
{
  "upper_pair": [
    5436,
    4836
  ],
  "lower_pair": [
    2006,
    1406
  ]
}
```

**Results**

```json
{
  "horizontal": [
    3430,
    3430
  ],
  "vertical": [
    600,
    600
  ],
  "carrier_factorization": [
    7,
    490
  ],
  "Actual_anatomy": [
    2401,
    1029
  ],
  "state_note": "Actual4836 anatomy and Rounded4836 endpoint are separately labelled"
}
```

**Finding.** The Shem/Flood and Jacob/Conquest pairs form a600-by3430 rectangle. Its3430 also has the earlier Actual anatomy2401+1029 and the Rounded role7×490; these are interfaces through labelled quantities, not an erasure of their states.

**Reassessment.** Test the smaller Flood core against the cumulative Levi phase pair.

## C581 — Connect the Flood core to cumulative root placement

**Question.** Does the six-carrier translation land on the source whole-year Levi pair?

**Sources.** File63 §8; File61/62 root family

**Inputs**

```json
{
  "Flood_core": [
    4834,
    4831
  ],
  "translation": 2898
}
```

**Results**

```json
{
  "translated_core": [
    1936,
    1933
  ],
  "source_root_whole_year_pair": [
    1936,
    1933
  ],
  "exact_Aaron_root": "3873/2"
}
```

**Finding.** The3-year Flood core translates by2898 to1936/1933, joining the carrier family to the cumulative root family at its whole-year display. The exact Aaron phase1936.5 remains a different state.

**Reassessment.** Reconstruct the macro birth-law path as an ordered vector.

## C582 — Reconstruct the macro component path

**Question.** Does the source1200-year path preserve the ordered birth-law component vector?

**Sources.** File63 §4

**Inputs**

```json
{
  "nodes": [
    2166,
    2026,
    1366,
    1296,
    966
  ],
  "components": [
    14,
    66,
    7,
    33
  ],
  "scale": 10
}
```

**Results**

```json
{
  "durations": [
    140,
    660,
    70,
    330
  ],
  "total": 1200,
  "node_roles": [
    "regular Abraham",
    "regular Isaac marriage",
    "regular Joshua death",
    "cumulative Joshua endpoint",
    "Temple cardinal foundation"
  ]
}
```

**Finding.** The mixed-role source path is exactly10×(14,66,7,33), retaining order as well as total1200. Its connection is a component projection; it does not equate regular and cumulative Joshua nodes.

**Reassessment.** Compare its Exodus and Joshua hinges as repartitions of one total.

## C583 — Explain macro hinge transfer

**Question.** How does changing the selected interior event repartition the same1200 span?

**Sources.** File63 §§4.3–4.5

**Inputs**

```json
{
  "outer": [
    2166,
    966
  ],
  "hinges": [
    1446,
    1366
  ]
}
```

**Results**

```json
{
  "partitions": [
    [
      720,
      480
    ],
    [
      800,
      400
    ]
  ],
  "transfer": [
    80,
    -80
  ],
  "fixed_total": 1200
}
```

**Finding.** Moving the selected hinge from Exodus to regular Joshua death transfers80 between the two legs:720+480 becomes800+400. This is repartition of one path, not a global expansion.

**Reassessment.** Check whether appending a gestation component preserves the same ordered path as prepending it.

## C584 — Retain order in the proposed gestation extension

**Question.** Does equal1207.5 total imply the same extended path?

**Sources.** File63 §4.6; duration-only comparison

**Inputs**

```json
{
  "base_components": [
    140,
    660,
    70,
    330
  ],
  "proposed_gestation": "15/2"
}
```

**Results**

```json
{
  "appended_prefixes": [
    140,
    800,
    870,
    1200,
    "2415/2"
  ],
  "prepended_prefixes": [
    "15/2",
    "295/2",
    "1615/2",
    "1755/2",
    "2415/2"
  ],
  "total": "2415/2"
}
```

**Finding.** Appending or prepending7.5 yields the same1207.5 total but different intermediate positions. The proposed gestation term therefore remains ordered path data; no deferred endpoint is introduced.

**Reassessment.** Verify local phase arithmetic before joining year and calendar representations.

## C585 — Execute the local Tishri/Nisan phase rule

**Question.** Can one half-year coordinate convention reproduce the source examples?

**Sources.** File12 §§6.1–6.3; File63 phase controls

**Inputs**

```json
{
  "n": "Y",
  "t": "Y−1/2",
  "examples": [
    [
      1450,
      1446
    ],
    [
      970,
      966
    ]
  ]
}
```

**Results**

```json
{
  "phase_spans_years": [
    "7/2",
    3,
    "7/2"
  ],
  "separate_units": [
    "0.5-year calendar phase",
    "3.5-year Aaron/Moses offset",
    "3.5-day liturgical projection"
  ]
}
```

**Finding.** The local rule t(Y)=Y−0.5 reproduces3.5,3 and3.5-year examples. Equal printed magnitudes across phase offsets and liturgical days do not supply a unit conversion.

**Reassessment.** Reduce calendar comparisons to a common normalized measure.

## C586 — Unify calendar and paired-endpoint equalities

**Question.** What single normalized comparison underlies the calendar Keys and earlier common endpoints?

**Sources.** File12 §§2,6.3; C535; C568–C575

**Inputs**

```json
{
  "calendars": [
    336,
    360,
    364
  ],
  "Keys": [
    "25/23",
    "70/69",
    "300/299"
  ]
}
```

**Results**

```json
{
  "calibration_constant": [
    "8400/23",
    "8400/23",
    "8400/23"
  ],
  "Key_ratios": [
    "15/14",
    "13/12",
    "91/90"
  ],
  "calendar_decomposition": [
    336,
    364,
    360
  ]
}
```

**Finding.** All Keys satisfy d×K_d=8400/23, hence K_d(s)=(8400/23)(s/d). Equal normalized durations explain the calendar-volume agreements and the earlier1566/2926 paired endpoints when anchor and direction also agree.

**Reassessment.** Test the Enochic source family for a similarly compact parameter rule.

## C587 — Generate all twelve Enoch cells

**Question.** Can one count-and-carrier rule recover the complete source family?

**Sources.** File69 §§1–3; Appendix B.1–B.4

**Inputs**

```json
{
  "N": [
    77,
    63,
    50
  ],
  "g": [
    70,
    72
  ],
  "rail": 110,
  "terminal_AD": 65,
  "Enoch_index": 7
}
```

**Results**

```json
{
  "cells": [
    {
      "N": 77,
      "g": 70,
      "u": 180,
      "cell": [
        12646,
        12536,
        12576,
        12466
      ]
    },
    {
      "N": 63,
      "g": 70,
      "u": 180,
      "cell": [
        10126,
        10016,
        10056,
        9946
      ]
    },
    {
      "N": 50,
      "g": 70,
      "u": 180,
      "cell": [
        7786,
        7676,
        7716,
        7606
      ]
    },
    {
      "N": 77,
      "g": 72,
      "u": 182,
      "cell": [
        12786,
        12676,
        12714,
        12604
      ]
    },
    {
      "N": 63,
      "g": 72,
      "u": 182,
      "cell": [
        10238,
        10128,
        10166,
        10056
      ]
    },
    {
      "N": 50,
      "g": 72,
      "u": 182,
      "cell": [
        7872,
        7762,
        7800,
        7690
      ]
    },
    {
      "N": 77,
      "g": 70,
      "u": 70,
      "cell": [
        4946,
        4836,
        4876,
        4766
      ]
    },
    {
      "N": 63,
      "g": 70,
      "u": 70,
      "cell": [
        3966,
        3856,
        3896,
        3786
      ]
    },
    {
      "N": 50,
      "g": 70,
      "u": 70,
      "cell": [
        3056,
        2946,
        2986,
        2876
      ]
    },
    {
      "N": 77,
      "g": 72,
      "u": 72,
      "cell": [
        5086,
        4976,
        5014,
        4904
      ]
    },
    {
      "N": 63,
      "g": 72,
      "u": 72,
      "cell": [
        4078,
        3968,
        4006,
        3896
      ]
    },
    {
      "N": 50,
      "g": 72,
      "u": 72,
      "cell": [
        3142,
        3032,
        3070,
        2960
      ]
    }
  ],
  "coordinate_matches": 48,
  "rule": "x=(N−7)u−64; cell=(x+110,x,x+110−g,x−g)"
}
```

**Finding.** One indexed carrier expression reconstructs48 printed coordinates across twelve cells. Accumulation uses u, while local birth-to-ascension uses g; retaining both is the key compression.

**Reassessment.** Test whether a single ordinary affine map could replace the indexed carrier rule.

## C588 — Reject a universal affine carrier conversion

**Question.** Can a role-preserving affine map send a70 Enoch cell to72 while keeping its110 rail?

**Sources.** File69 Appendix B.1–B.4; C587

**Inputs**

```json
{
  "rail_before_after": [
    110,
    110
  ],
  "local_before_after": [
    70,
    72
  ]
}
```

**Results**

```json
{
  "required_rail_slope": 1,
  "required_local_slope": "36/35",
  "chronological_gap_patterns": [
    [
      70,
      40,
      70
    ],
    [
      72,
      38,
      72
    ]
  ]
}
```

**Finding.** A single role-preserving affine map is impossible: the110 rail forces slope1, while70→72 requires36/35. The source rule changes one carrier parameter while retaining another; it cannot be replaced by global date scaling.

**Reassessment.** Determine the ordinary-to-generation transformation within each schematic.

## C589 — Derive indexed resolution transport

**Question.** How does embedding110 into each generation move the local Enoch cells?

**Sources.** File69 §§1.3,2.3,3.2

**Inputs**

```json
{
  "counts": [
    77,
    63,
    50
  ],
  "Enoch_index": 7,
  "added_carrier": 110
}
```

**Results**

```json
{
  "cell_translations": {
    "77": 7700,
    "63": 6160,
    "50": 4730
  },
  "fixed_local_metrics": [
    110,
    "g"
  ]
}
```

**Finding.** Ordinary-to-generation resolution rigidly translates each local cell by110(N−7):7700,6160 or4730. It is one index-dependent rule across the family, not one translation shared by all three schematics.

**Reassessment.** Derive the ordinary-resolution center directly from the count differences.

## C590 — Prove the ordinary Enoch center condition

**Question.** When is Matthew birth the center of Luke birth and Enochic ascension?

**Sources.** File69 §§2.12–2.13,3.4–3.5

**Inputs**

```json
{
  "birth_counts": [
    70,
    56,
    43
  ],
  "local_gap": "g"
}
```

**Results**

```json
{
  "triples_and_arms": [
    [
      4836,
      3856,
      2876,
      980,
      980
    ],
    [
      4976,
      3968,
      2960,
      1008,
      1008
    ]
  ],
  "symbolic_residual": "(u−g)/2",
  "condition": "u=g"
}
```

**Finding.** The ordinary center follows from the count relation70+43−2×56=1 and the local ascension subtraction g. Equal arms are980 or1008. It is a derived center, not an independently fitted midpoint.

**Reassessment.** Determine which endpoint roles preserve a center at generation resolution.

## C591 — Prove the crossed generation centers

**Question.** Why do two generation-resolution envelopes share a center?

**Sources.** File69 §§2.12–2.13,3.4–3.5

**Inputs**

```json
{
  "rail": 110,
  "carriers": [
    70,
    72
  ]
}
```

**Results**

```json
{
  "envelopes": [
    {
      "u": 180,
      "minimum": [
        12466,
        10126,
        7786
      ],
      "maximum": [
        12646,
        10126,
        7606
      ],
      "widths": [
        4680,
        5040
      ]
    },
    {
      "u": 182,
      "minimum": [
        12604,
        10238,
        7872
      ],
      "maximum": [
        12786,
        10238,
        7690
      ],
      "widths": [
        4732,
        5096
      ]
    }
  ],
  "symbolic_center_residual": "(u−g−110)/2"
}
```

**Finding.** At u=g+110 the two crossed envelopes center on Matthew birth+110, with widths26u and28u. Center preservation requires the stated change of endpoint roles from the ordinary family.

**Reassessment.** Test the wrong-role transports and then connect the cells to the full four-rail Enochic grid.

## Evidence

Current completion:C532–C591. 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.
