# 490d — C552–C571: 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. ## C552 — Generate the cumulative root family **Question.** Does one affine rule reconstruct all six source rails? **Sources.** File62 §§1.2–1.4; File61 §§7.3A–7.6 **Inputs** ```json { "base": [ 2435, 2260, 2080, 1933, 1796, 1663, 1526 ], "phases": [ 0, "7/2" ], "clutch": [ 0, 7, 14 ] } ``` **Results** ```json { "rails": [ [ 2435, 2260, 2080, 1933, 1796, 1663, 1526 ], [ 2428, 2253, 2073, 1926, 1789, 1656, 1519 ], [ 2421, 2246, 2066, 1919, 1782, 1649, 1512 ], [ "4877/2", "4527/2", "4167/2", "3873/2", "3599/2", "3333/2", "3059/2" ], [ "4863/2", "4513/2", "4153/2", "3859/2", "3585/2", "3319/2", "3045/2" ], [ "4849/2", "4499/2", "4139/2", "3845/2", "3571/2", "3305/2", "3031/2" ] ], "coordinate_matches": 42 } ``` **Finding.** C(p,d)=C0+p−d reconstructs all42 source coordinates. This is one family generated from seven inputs and two local state parameters, not42 independent successes. **Reassessment.** Establish why the source clutch is14 and whether its three envelopes are independent. ## C553 — Recover one clutch from nested envelopes **Question.** Are487/473,444/430 and350/336 independent compression measurements? **Sources.** File61 §§6.3–6.6 **Inputs** ```json { "envelopes": [ [ 487, 473 ], [ 444, 430 ], [ 350, 336 ] ] } ``` **Results** ```json { "compressions": [ 14, 14, 14 ], "removed_prefixes": [ [ 43, 43 ], [ 94, 94 ] ] } ``` **Finding.** All three envelopes express the same14-year compression after equal prefixes43 and94 are removed. The maximum nonoverlap envelope is a source model, not a literal succession of biographies. **Reassessment.** Distinguish translating the whole root from moving a single boundary. ## C554 — Separate endpoint and whole-rail translation **Question.** Which spans contract when the clutch moves only a parent boundary? **Sources.** File61 §7.4; §§17.2–17.3 **Inputs** ```json { "lifespans": [ 175, 180, 147, 137, 133, 137 ], "clutch": 14 } ``` **Results** ```json { "parent_only": [ 161, 166, 133, 123, 119, 123 ], "both_ends": [ 175, 180, 147, 137, 133, 137 ], "Isaac_only_Abraham_fixed": 189, "derived_terminal_to_fixed_Exodus": 66 } ``` **Finding.** One-end translation contracts each lifespan; whole-rail translation preserves it. Outputs166 and119 remain part of the family. Moving Isaac alone makes189, showing why endpoint roles are indispensable. **Reassessment.** Determine the exact local composition law for half and full clutch. ## C555 — Specify the finite clutch action **Question.** What symmetry is licensed by the three admitted displacement states? **Sources.** File61 §7.3A; File62 §1 **Inputs** ```json { "displacements": [ 0, 7, 14 ], "example": 1933 } ``` **Results** ```json { "rail": [ 1933, 1926, 1919 ], "half_step_edges": [ [ 0, 7 ], [ 7, 14 ] ], "composite_edge": [ 0, 14 ], "third_half_step": 1912, "third_step_admitted": false } ``` **Finding.** H7 composed twice equals T14 on the declared original-to-full domain. The admitted rails form a finite directed chain, not a closed translation group. Historical event anchors remain fixed. **Reassessment.** Generate Joseph collateral intervals from the same root boundaries. ## C556 — Generate all collateral Joseph intervals **Question.** Do two fixed-offset constructions account for every source Joseph rail? **Sources.** File61 §§11.2–11.3A; File62 §5.2 **Inputs** ```json { "Levi": 1933, "Kohath": 1796, "Joseph_life": 110 } ``` **Results** ```json { "intervals": [ [ 1933, 1823 ], [ 1906, 1796 ], [ 1926, 1816 ], [ 1899, 1789 ], [ 1919, 1809 ], [ 1892, 1782 ], [ "3873/2", "3653/2" ], [ "3819/2", "3599/2" ], [ "3859/2", "3639/2" ], [ "3805/2", "3585/2" ], [ "3845/2", "3625/2" ], [ "3791/2", "3571/2" ] ], "matches": 12 } ``` **Finding.** Two collateral constructors, (L,L−110) and (K+110,K), generate all12 exact-phase Joseph intervals. Joseph remains a collateral interval, not an added trunk generation. **Reassessment.** Derive the invariant geometry shared by these interval pairs. ## C557 — Derive Joseph overlap geometry **Question.** Why do all six paired states share27|83|27? **Sources.** File61 §11; File62 §§5–6 **Inputs** ```json { "trunk": 137, "collateral": 110 } ``` **Results** ```json { "partition": [ 27, 83, 27 ], "overlap": 83, "translation_commutes_with_collateral_construction": [ true, true, true, true, true, true ] } ``` **Finding.** The27|83|27 geometry follows from lengths137 and110. Translation commutes with fixed-offset collateral construction, so twelve intervals reduce to one shape in six placements. **Reassessment.** Compare the moving collateral lives with fixed regular Joseph. ## C558 — Generate the fixed-Joseph comparison family **Question.** Can one flank-transfer formula reproduce all nine comparison states? **Sources.** File62 §§6.1–6.4 **Inputs** ```json { "regular_Joseph": [ 1915, 1805 ], "phases": [ 0, 3, "7/2" ], "clutch": [ 0, 7, 14 ] } ``` **Results** ```json { "partitions": [ [ 18, 9, 83 ], [ 11, 16, 83 ], [ 4, 23, 83 ], [ "43/2", "11/2", 83 ], [ "29/2", "25/2", 83 ], [ "15/2", "39/2", 83 ], [ 21, 6, 83 ], [ 14, 13, 83 ], [ 7, 20, 83 ] ], "formula": [ "18+p−d", "9−p+d", "83" ] } ``` **Finding.** The clutch transfers duration between two flanks while preserving their27 total and the83 overlap. All nine states follow without moving regular Joseph1915–1805. **Reassessment.** Test whether the reported cyclic symmetry acts on dates or on duration components. ## C559 — Locate the Joseph cyclic symmetry **Question.** Does a three-cycle act consistently on the complete component family? **Sources.** File62 §§6.1–6.4; C558 **Inputs** ```json { "rotation": "(a,b,c)→(b,c,a)" } ``` **Results** ```json { "states": 9, "component_displays": 27, "example": [ [ 4, 23, 83 ], [ 23, 83, 4 ], [ 83, 4, 23 ] ], "action_domain": "ordered duration triples" } ``` **Finding.** A genuine C3 action rotates duration components and returns after three applications. It does not establish a permutation of historical people or complete chronology states. **Reassessment.** Test how whole-year and exact phase choices change crossed containers. ## C560 — Unify crossed Joseph containers by phase **Question.** Are140 and140.5 conflicting containers or different declared states? **Sources.** File61 §§12.1–12.3 **Inputs** ```json { "Levi_span": 137, "phases": [ 3, "7/2" ] } ``` **Results** ```json { "phase_family": { "3": { "parts": [ 30, 80, 30 ], "outer": 140, "other_diagonal": 134 }, "7/2": { "parts": [ "61/2", "159/2", "61/2" ], "outer": "281/2", "other_diagonal": "267/2" } }, "exact_diagonal_center": 137, "exact_diagonal_separation": 7 } ``` **Finding.** Whole-year30|80|30 and exact30.5|79.5|30.5 are evaluations of one phase formula. Exact diagonals140.5 and133.5 are centered on137 and separated by7. **Reassessment.** Reconstruct the430/460 Joseph-to-Joshua routes with their declared phase states. ## C561 — Resolve the two Joshua translations **Question.** Which Joseph states yield the source430 and460 routes? **Sources.** File61 §§14.1–14.3 **Inputs** ```json { "target": [ 1476, 1366 ], "source_intervals": [ [ 1906, 1796 ], [ 1936, 1826 ], [ 1933, 1823 ], [ "3873/2", "3653/2" ] ] } ``` **Results** ```json { "translations": [ [ 430, 430 ], [ 460, 460 ], [ 457, 457 ], [ "921/2", "921/2" ] ], "states": [ "backward Nisan", "forward Aaron whole-year", "forward Nisan diagnostic", "forward Aaron exact diagnostic" ] } ``` **Finding.** The430/460 pair is exact in its declared mixed states. Other forward phases require457 or460.5, so460 is not a phase-independent property of Joseph. **Reassessment.** Follow the fixed regular Joshua interval into the cumulative Joshua interval. ## C562 — Compose Joshua interval translations **Question.** Does the regular-to-cumulative Joshua link close the Joseph routes without changing fixed event anchors? **Sources.** File61 §14.3A; File62 §9 **Inputs** ```json { "regular": [ 1476, 1366 ], "cumulative": [ 1406, 1296 ], "terminal_starts": [ 1526, 1512 ] } ``` **Results** ```json { "Joshua_shift": [ 70, 70 ], "composed_Joseph_shifts": [ 500, 530 ], "fixed_Joshua_spans": [ 230, 216 ] } ``` **Finding.** The common70 translation gives total500/530 routes. Holding cumulative Joshua1296 contracts230 to216 when the derived start shifts14; historical Moses1526 remains the original event. **Reassessment.** Test whether the double Adam square is an independent pattern or translated geometry. ## C563 — Compress the double Adam square **Question.** Do both110-squared constructions follow from a rigid translation? **Sources.** File61 §§12.4–12.6 **Inputs** ```json { "base": [ 14006, 1906, 1796 ], "apparent_whole_year": [ 14036, 1936, 1826 ] } ``` **Results** ```json { "differences": [ [ 12100, 12210, 110 ], [ 12100, 12210, 110 ] ], "pair_translation": [ 30, 30, 30 ], "exact_phase_mismatch": "24199/2", "square": 12100 } ``` **Finding.** The two square/rectangle displays are the same12100/12210 geometry translated30. Substituting an exact-phase Joseph node alone yields12099.5 and breaks the square; no new head is fitted. **Reassessment.** Determine how the Isaac macro partition relates to the calendar ratios. ## C564 — Relate the Isaac partition to calendar calibration **Question.** Does the11760/840/12600 family use an existing ratio? **Sources.** File61 §§17.3–17.7 **Inputs** ```json { "head": 14006, "translated_Isaac": 2246, "Conquest": 1406 } ``` **Results** ```json { "partition": [ 11760, 840, 12600 ], "units_of35": [ 336, 24, 360 ], "whole_over_upper": "15/14", "E_over_P": "15/14" } ``` **Finding.** The Isaac macro partition is35 copies of336+24=360. Its15/14 completion ratio is exactly E/P, connecting the cumulative partition to the existing calendar calibration. **Reassessment.** Check which part survives an exact common phase shift. ## C565 — Localize phase invariance in the Isaac partition **Question.** Can the complete dated partition be carried unchanged into the exact Aaron phase? **Sources.** File61 §§17.3–17.7 **Inputs** ```json { "phase": "7/2", "fixed_Conquest": 1406 } ``` **Results** ```json { "upper_common_phase": 11760, "lower_fixed_terminal": "1687/2", "changed_total": "25207/2" } ``` **Finding.** The upper11760 leg is phase-invariant when both ends move. The fixed-Conquest lower leg becomes843.5, so the840 and12600 dated partition belongs to its declared Nisan state. **Reassessment.** Separate the Cainan and Apparent inputs in the12250 variant. ## C566 — Generate the12250 cumulative variant **Question.** How do the separate Cainan and Apparent operations combine in this source state? **Sources.** File61 §§17.6–17.7 **Inputs** ```json { "base_head": 14006, "Isaac": 2246, "cumulative_Cainan": 460, "Apparent": 30 } ``` **Results** ```json { "heads": [ 14006, 14466, 14036, 14496 ], "upper_legs": [ 11760, 12220, 11790, 12250 ], "combined_factorization": [ 25, 490 ] } ``` **Finding.** Separate source operations+460 and+30 combine additively to a490 increment. The combined upper leg12250 is25×490; numerical summation does not identify the two state changes or regular Cainan130 with cumulative460. **Reassessment.** Recover the full, half and quarter Key family behind clutch magnitudes. ## C567 — Unify full half and quarter Key scales **Question.** Do14,7 and3.5 require separate expansion laws? **Sources.** File62 §8.3; File60 §7 **Inputs** ```json { "scales": [ 7, "7/2", "7/4" ] } ``` **Results** ```json { "input_output_gain": [ [ 161, 175, 14 ], [ "161/2", "175/2", 7 ], [ "161/4", "175/4", "7/2" ] ], "general_rule": "23u→25u, gain2u" } ``` **Finding.** The three gains are scaled evaluations of E, not new Keys. They connect the161/175 Covenant unit to80.5/87.5 and40.25/43.75 duration units without making their event placements interchangeable. **Reassessment.** Compare the two source routes from483 to490. ## C568 — Compare the dual490 constructions **Question.** Can subset E and whole-span P agree on the source483 partition? **Sources.** File62 §§8.6A–C; File63 §1.3 **Inputs** ```json { "parts": [ "805/2", "161/2" ], "total": 483 } ``` **Results** ```json { "partial_E": 490, "whole_P": 490, "whole_E": 525, "common_day_volume": [ 176400, 176400 ] } ``` **Finding.** Expanding only80.5 by E and all483 by P both give490. Whole-span E gives525; the calendar volumes490×360 and525×336 agree. The duration identity needs no deferred endpoint. **Reassessment.** Derive the general allocation identity that explains this agreement. ## C569 — Derive the Prophetic allocation identity **Question.** Why does applying E to one sixth reproduce whole-span P? **Sources.** File63 §1.3; algebraic generalization of C568 **Inputs** ```json { "E": "25/23", "P": "70/69" } ``` **Results** ```json { "required_fraction": "1/6", "effective_factor": "70/69", "identity": "(5/6)S+E(S/6)=P S", "483_selected_part": "161/2" } ``` **Finding.** P is the total-span effect of allocating E to one sixth of a duration. The source supplies that partition for483; the identity alone does not authorize the partition at every chronological node. **Reassessment.** Ask whether J has a parallel allocation fraction and an already sourced partition. ## C570 — Derive the Jubilee allocation identity **Question.** Does J admit the same allocation explanation on the source12558 path? **Sources.** File63 §§7.3–7.4,9.7; algebraic generalization **Inputs** ```json { "E": "25/23", "J": "300/299", "path": [ 14004, 1929, 1446 ] } ``` **Results** ```json { "fraction": "1/26", "partition": [ 12075, 483 ], "carrier_counts": [ 25, 1 ], "partial_E": 12600, "whole_J": 12600 } ``` **Finding.** J is the total-span effect of E allocated to one26th. The source path14004→1929→1446 already supplies25×483+483, so expanding its final carrier gives12600 without a fitted breakpoint. **Reassessment.** Check whether equal totals make these complete chronological maps identical. ## C571 — Distinguish endpoint agreement from path identity **Question.** Do whole J and terminal-cell E have the same intermediate coordinate? **Sources.** File63 §§7.3–7.4,9.7; C570 **Inputs** ```json { "head": 14004, "junction": 1929, "terminal": 1446 } ``` **Results** ```json { "whole_J_path": [ 14004, "24552/13", 1404 ], "terminal_E_path": [ 14004, 1929, 1404 ], "junction_difference": "525/13" } ``` **Finding.** Both paths end at1404, but whole J moves the junction to24552/13 while terminal E retains1929. The new compression is equality after evaluating total span, not identity of the ordered chronological path. **Reassessment.** Use the shared endpoint1404 to reconstruct the Actual-to-Rounded cumulative interface. ## Evidence Current completion:C532–C571. 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.