490d — C832–C871: sequential research record
Working continuation of C831 · packet date20260928.
Each completed step retains its question, declared inputs, exact results, finding, and reassessment. These are bounded research actions, not a count of independent discoveries. Canonical sources remain unchanged; second decimal inversion remains deferred.
C832 — Select complete-family transfer tests
Question. Can the established path grammar explain new source-controlled families without fitting their endpoints?
Sources. Strategy stagesD–H; C831 synthesis; local File58
Inputs
{
"first_family": "File58 complete ledger matrices and declared partitions",
"other_candidates": [
"File43/54 full Luke display",
"File52c complete paired-anchor field",
"File63 ordered carrier network"
],
"predecessor": "C831"
}
Results
{
"selection": {
"path": "model/RESEARCH_SELECTION.json",
"sha256": "57658fdf754e76e533371e0183608c0c10b33a58131b0dcfd0c92e85dfdc1709",
"bytes": 285
},
"source_snapshots": 41,
"primary": "a5ea84562101158b60d0cf296765d6eff38e7a2abda4e74ad1b353dfd13b9530"
}
Finding. The next test moves from genealogy to a bounded list with multiple source-defined measurements. Complete-family transformations, not additional endpoint searches, will guide the cycle.
Reassessment. Freeze File58’s complete ledger and partition data before calculating its consequences.
C833 — Freeze the complete File58 list objects
Question. Which literal tables and declared orders are the inputs to the holdout?
Sources. File58 §§3–5,7,13
Inputs
{}
Results
{
"packet": {
"path": "model/list_inputs.json",
"sha256": "9884a95572290132effce69c3a16e362d9c298c9a9b4c6bded06545f449dd2f1",
"bytes": 14983
},
"literal_table_rows": {
"category": 8,
"leviticus": 3,
"feast_scale": 6,
"full_scale": 7,
"forward": 8,
"reverse": 8,
"esau": 9,
"clean_walk": 6
}
}
Finding. The complete category, sequence and partition tables are frozen with source line locators. Subsequent tests can distinguish source inputs from generated consequences.
Reassessment. Reconstruct the whole seven-day Sukkot count matrix.
C834 — Reconstruct a complete Sukkot species-by-day matrix
Question. Can the seven day totals be generated by one declining component and three constant components?
Sources. File58 §§3.1–3.2,7.1
Inputs
{
"uniform_daily_rams_lambs_goats": [
2,
14,
1
],
"status": "declared allocation reconstruction; marginal totals alone do not imply uniformity"
}
Results
{
"matrix": {
"path": "model/Sukkot_matrix.json",
"sha256": "2dd0f49ee2c98a58d388b4eb25ad26956588342e8058e1f8517abb1f9e4204a4",
"bytes": 642
},
"species": [
"bulls",
"rams",
"lambs",
"goats"
],
"day_rows": [
[
13,
2,
14,
1
],
[
12,
2,
14,
1
],
[
11,
2,
14,
1
],
[
10,
2,
14,
1
],
[
9,
2,
14,
1
],
[
8,
2,
14,
1
],
[
7,
2,
14,
1
]
],
"day_totals": [
30,
29,
28,
27,
26,
25,
24
],
"column_totals": [
70,
14,
98,
7
],
"rank": 2,
"generator": "row_d=(14−d,2,14,1), d=1…7"
}
Finding. The declared daily allocation has a rank-two generator: only the bull component changes. It recovers all seven totals and the complete189 species ledger. The uniform component allocation remains an input, not a deduction from margins alone.
Reassessment. Recover the whole Tishri category/species table as a linear measurement object.
C835 — Recover both complete Tishri margins
Question. Do event-category and species totals measure the same frozen count matrix?
Sources. File58 §3.1 literal category table
Inputs
{}
Results
{
"matrix": {
"path": "model/Tishri_count_matrix.json",
"sha256": "ccbb58ccd547dbe8e826eba227e09d3454451f998f4531f34677c06ee73375c2",
"bytes": 665
},
"category_totals": [
44,
6,
11,
10,
10,
189,
10
],
"species_totals": [
75,
18,
176,
11
],
"grand_total": 280
}
Finding. The two280 totals are different marginals of one seven-by-four matrix. Their agreement is forced by the shared ledger, while the chosen categories and entries remain source inputs.
Reassessment. Determine what the margins preserve and what they cannot recover.
C836 — Test whether the margins determine the ledger
Question. Can preserved category/species totals recover every internal cell?
Sources. C835; diagnostic only
Inputs
{}
Results
{
"diagnostic_changed_rows": {
"NewMoon": [
3,
1,
6,
1
],
"Trumpets": [
0,
1,
8,
1
]
},
"kernel_move": "a2×2 +1,−1,−1,+1 cell circulation",
"source_status": "not an admitted offering variant"
}
Finding. Both margins survive a nonzero cell circulation. Totals compress the ledger but do not reconstruct its source cells; the complete table supplies information beyond280.
Reassessment. Evaluate the source-admitted calendar/corpus overlay states.
C837 — Generate the finite calendar/corpus comparison matrix
Question. Do independent declared additions reconstruct all four source states?
Sources. File58 §4.3
Inputs
{}
Results
{
"states": {
"path": "model/Tishri_overlay_states.json",
"sha256": "6b9e2c3bfcfaf70af42bf0540baf3553326d37c0998a9450fee912eadec5ac0d",
"bytes": 387
},
"00": {
"species": [
75,
18,
176,
11
],
"total": 280
},
"01": {
"species": [
76,
20,
176,
13
],
"total": 285
},
"10": {
"species": [
75,
18,
178,
11
],
"total": 282
},
"11": {
"species": [
76,
20,
178,
13
],
"total": 287
},
"controls": "00 controls; fourth Sabbath and Leviticus16 are separate comparison choices"
}
Finding. The280/282/285/287 matrix is a two-choice additive configuration with independently stated supports. Calendar placement adds lambs; corpus inclusion adds a different animal vector.
Reassessment. Check the separate slaughtered subset and scaled overlay response.
C838 — Separate ledger selection from scale
Question. How do ritual disposition and shemitah scale interact with the finite overlay?
Sources. File58 §§4.3,5
Inputs
{}
Results
{
"complete_rite": 5,
"slaughtered_subset": 4,
"scaled_states": {
"00": 1960,
"01": 1995,
"10": 1974,
"11": 2009
},
"scaled_calendar_increment": 14,
"scaled_complete_rite_increment": 35,
"derived_slaughtered_totals": [
284,
286
]
}
Finding. Selecting displayed ritual animals or slaughtered animals changes the measured object by one goat. Scaling then carries that difference to seven; it cannot be suppressed by retaining the same ledger name.
Reassessment. Regenerate every forward festival boundary from its day generator.
C839 — Regenerate the full forward festival path
Question. Does one day generator recover every supplied cumulative and chronological row?
Sources. File58 §7.1
Inputs
{
"anchor": 1859,
"scale": 7
}
Results
{
"path": {
"path": "model/festival_forward_path.json",
"sha256": "b92c95b5b92dd58e80d9a6bbba6b1b8e0bae4b0de0da292d19d6bb68e552a67a",
"bytes": 340
},
"prefix_counts": [
0,
30,
59,
87,
114,
140,
165,
189,
199
],
"BC": [
1859,
1649,
1446,
1250,
1061,
879,
704,
536,
466
]
}
Finding. The complete forward path follows the descending day total and one appended Eighth-Day10. All eight source boundaries are forced once the source order, scale7, and1859 anchor are fixed.
Reassessment. Generate the complete declared reverse order through the same accumulation rule.
C840 — Regenerate the complete reverse-order festival path
Question. What relation joins the two declared orders at every boundary?
Inputs
{}
Results
{
"path": {
"path": "model/festival_reverse_path.json",
"sha256": "2a0416f26a90c2385b0ac39c1ea69d227783bc5d0804feadd08722dc4b6e0cbc",
"bytes": 287
},
"prefix_counts": [
0,
10,
34,
59,
85,
112,
140,
169,
199
],
"BC": [
1859,
1789,
1621,
1446,
1264,
1075,
879,
676,
466
],
"paired_formula": "reverse_prefix(k)=199−forward_prefix(8−k)",
"coordinate_pair_sum": 2325
}
Finding. Every reverse boundary is the complement of a corresponding forward boundary. This is a sequence-reversal relation on two paths, not a newly licensed formal Mirror operation.
Reassessment. Identify exactly where the two source orders share boundaries.
C841 — Resolve all shared boundaries of the two festival orders
Question. Which overlaps follow from the complete prefix sets?
Sources. C839–840
Inputs
{}
Results
{
"shared_boundaries": [
{
"count": 0,
"years": 0,
"BC": 1859,
"forward_step": 0,
"reverse_step": 0
},
{
"count": 59,
"years": 413,
"BC": 1446,
"forward_step": 2,
"reverse_step": 3
},
{
"count": 140,
"years": 980,
"BC": 879,
"forward_step": 5,
"reverse_step": 6
},
{
"count": 199,
"years": 1393,
"BC": 466,
"forward_step": 8,
"reverse_step": 8
}
],
"status": "complete dependent comparison of the two declared orders; no alternative-order search"
}
Finding. The two paths share only counts0,59,140,199, producing1859,1446,879,466. Their common internal boundaries occur at different step indices, so endpoint agreement does not identify the ordered paths.
Reassessment. Test scaling and order as separate linear operations.
C842 — Separate scale, order and accumulation
Question. Which operations commute, and which change the internal chronological field?
Sources. File58 declared order and×7; C839–841
Inputs
{}
Results
{
"scale_order_commutes": true,
"scale_accumulation_commutes": true,
"forward_prefix_years": [
210,
413,
609,
798,
980,
1155,
1323,
1393
],
"reverse_prefix_years": [
70,
238,
413,
595,
784,
980,
1183,
1393
]
}
Finding. Scaling commutes with both declared reordering and accumulation. Reordering preserves the total but changes the intermediate prefix field; that distinction is the same one needed for genealogical and Rounded paths.
Reassessment. Construct the complete sex-by-purity measurement table for Esau’s ledger.
C843 — Build the complete Esau joint-category table
Question. What cell structure lies beneath the equal490/60 marginals?
Sources. File58 §13.1 nine printed rows
Inputs
{}
Results
{
"joint_table": {
"path": "model/Esau_joint_measurements.json",
"sha256": "74bd41362ddc19e287e21419635e918f8fa091f10f6f059baf43cab8a13a8fbf",
"bytes": 1169
},
"joint_clean_unclean_by_female_male": [
[
440,
50
],
[
50,
10
]
],
"purity_totals": [
490,
60
],
"sex_totals": [
490,
60
]
}
Finding. The complete joint table is[[440,50],[50,10]]. Equal490/60 marginals arise because the two off-diagonal cells agree, while purity and sex remain different classifications.
Reassessment. Identify the exact constraint and freedom behind that equality.
C844 — Derive the equal-marginal constraint
Question. What exactly must be true for purity and sex totals to coincide?
Sources. C843
Inputs
{}
Results
{
"clean_minus_female": 0,
"unclean_minus_male": 0,
"fixed_margin_family": "[[490−t,t],[t,60−t]], 0≤t≤60",
"source_t": 50,
"constraint_count": 1,
"independence_determinant": 1900
}
Finding. The double490/60 display imposes one cross-category balance, b=c. Given those margins, one cell parameter remains; the source selects50. Distinct category definitions and equal marginals do not establish statistical independence.
Reassessment. Recover the exact rank of the nine-row measurement map.
C845 — Measure the information retained by the category projections
Question. How many independent totals do the four marginals supply?
Sources. File58 nine-row ledger; C843–844
Inputs
{}
Results
{
"incidence_matrix": [
[
1,
1,
1,
1,
1,
1,
0,
0,
0
],
[
0,
0,
0,
0,
0,
0,
1,
1,
1
],
[
1,
0,
1,
0,
1,
0,
1,
1,
0
],
[
0,
1,
0,
1,
0,
1,
0,
0,
1
]
],
"rank": 3,
"kernel_dimension_on_unrestricted_nine_counts": 6,
"row_relation": "clean+unclean=female+male"
}
Finding. The four totals contain three independent linear measurements of nine source counts. Six numerical directions are invisible to these marginals; species, order and individual counts remain necessary source data.
Reassessment. Regenerate the complete source-admitted clean category-order walk.
C846 — Regenerate the complete clean category-order walk
Question. Do declared category keys determine every source landing without selecting targets?
Sources. File58 §13.3
Inputs
{
"anchor": 1896,
"sort_keys": [
"male before female",
"goats sheep cattle"
]
}
Results
{
"ordered_counts": [
20,
20,
10,
200,
200,
40
],
"landings": [
1876,
1856,
1846,
1646,
1446,
1406
],
"source_rows_used": [
[
"Goats",
"male"
],
[
"Sheep",
"male"
],
[
"Cattle",
"male"
],
[
"Goats",
"female"
],
[
"Sheep",
"female"
],
[
"Cattle",
"female"
]
]
}
Finding. The predeclared male-first/species order yields all six source landings, including its intermediate boundaries. The result depends on category order in addition to the conserved490 total.
Reassessment. Explain the female cumulative register without turning it into one date walk.
C847 — Resolve the female register as a two-endpoint measurement
Question. How do400/430/470/490 arise when the chronological endpoints also change?
Sources. File58 §13.2
Inputs
{}
Results
{
"female_source_counts": [
200,
200,
30,
40,
20
],
"prefix_register": [
200,
400,
430,
470,
490
],
"chronology_heads": [
1846,
1876,
1876,
1896
],
"chronology_tails": [
1446,
1446,
1406,
1406
],
"span_changes": [
{
"head": 30,
"tail": 0,
"span": 30
},
{
"head": 0,
"tail": -40,
"span": 40
},
{
"head": 20,
"tail": 0,
"span": 20
}
]
}
Finding. The30,40,20 increments come respectively from an earlier head, a later tail, and an earlier head. This is a two-endpoint span register, not one chronology walk from a fixed anchor.
Reassessment. Test a second list’s declared regroupings against the same measurement grammar.
C848 — Transfer the projection model to the four-household ledger
Question. Do equal regrouped totals recover the ordered household inputs?
Sources. File58 §1.4 Genesis46 printed-household subtotal register
Inputs
{
"source_vector": [
33,
16,
14,
7
]
}
Results
{
"source_pair": [
49,
21
],
"source_bracket": [
40,
30
],
"source_prefix": [
33,
49,
63,
70
],
"invisible_regrouping_direction": [
1,
-1,
1,
-1
],
"diagnostic_prefix": [
34,
49,
64,
70
],
"scope": "printed source subtotals only; no person-count repair or chronology projection"
}
Finding. The same four counts produce49/21 and40/30 through two declared partitions. Both partitions miss one direction of change that the ordered prefix register detects. Retaining order adds information beyond shared totals.
Reassessment. State the precise extension of the path grammar established by the list holdout.
C849 — State the new list-family extension of the grammar
Question. What has transferred unchanged, and what must be added to the source object?
Sources. C833–848; Strategy stageH
Inputs
{}
Results
{
"transfer": {
"path": "model/list_transfer_summary.json",
"sha256": "62e4c18b5e59ca75bc8be2c620ee822cd8c4d7b978eb5ec526b76817b4e3614f",
"bytes": 762
}
}
Finding. The grammar transfers to lists when source rows retain category annotations and declared order. The new explanation identifies the constraints behind equal totals and the information those totals lose; it does not derive the textual counts or their historical intention.
Reassessment. Freeze the next complete File52c paired-anchor test before execution.
C850 — Freeze the full paired-anchor inverse field
Question. Can one digit-register rule explain every existing pair of File52c endpoints?
Sources. latest File52c §2.1 and AppendixA.2–A.3; inverse preparation audit
Inputs
{}
Results
{
"packet": {
"path": "model/inverse_inputs.json",
"sha256": "dbcb35bf6cfe88b318b4c8c327e97aa0be06583d5e945c43c9aac8b7f7b80911",
"bytes": 19844
},
"scope": "existing32 sources and64 endpoints; target columns excluded; original input durations only",
"hypothesis": "anchor dependence is generated by decimal borrow, core length and retained zero-placeholders"
}
Finding. The entire original paired field is the next fixed reconstruction target. No extra dates, target counts, or second-pass reversal are admitted.
Reassessment. Close the first20-step checkpoint, then test the paired field.
C851 — Close the first twenty-step explanatory checkpoint
Question. What did the complete list holdout add to the common grammar?
Sources. C832–850
Inputs
{}
Results
{
"checkpoint": {
"path": "deliverables/490d_Chronological_Families_Checkpoint_C851.md",
"sha256": "18816601d66beb94848c9353dd59c9d2cbc13c64b9fad842459de3a7d3e78369",
"bytes": 1453
}
}
Finding. The first transfer succeeds with one explicit enrichment: category predicates and declared order remain attached to source rows. Equal totals are now traced to exact constraints rather than treated as interchangeable objects.
Reassessment. Reconstruct the full paired-anchor field from its original digit registers.
C852 — Reconstruct all existing paired-anchor endpoints
Question. Does a single digit-register operation recover every original File52c endpoint?
Sources. model/inverse_inputs.json; latest File52c existing manifest
Inputs
{}
Results
{
"field": {
"path": "model/inverse_paired_field.json",
"sha256": "eea45a0802d05e2ada4ee33ae2685da893929e1995083b0df2ebcfa2f86f2ce9",
"bytes": 19047
},
"source_rows": 32,
"existing_endpoints": 64,
"scope": "original durations only; no target enumeration"
}
Finding. Every existing endpoint is reproduced by one digit-position evaluation with its original zero-placeholders. The whole paired field is now available for explanation without adding source or target states.
Reassessment. Express anchor dependence as a gain field on original durations.
C853 — Derive the complete paired gain field
Question. Where does the anchor dependence enter the forward construction?
Sources. C852; inherited one-pass gain definition
Inputs
{}
Results
{
"gains": {
"path": "model/inverse_gain_field.json",
"sha256": "093b354383add7d87f104fb0d8a32411bab1bb2465eddb6ccb4e78273938c8ba",
"bytes": 3362
},
"paired_delta": [
7200,
990,
990,
990,
990,
990,
990,
990,
1980,
1980,
990,
990,
990,
-6930,
-3330,
-630,
-6840,
-4140,
-1440,
-4050,
-3960,
0,
-360,
-1800,
-900,
-5940,
990,
-6660,
-5670,
-2970,
-2970,
1980
],
"identity": "A+I(D−A)=D+g(D−A), with g(s)=I(s)−s"
}
Finding. All anchor dependence resides in the gain of the original selected duration. The32 differences are one generated field, not32 adjustable translations.
Reassessment. Derive the long-core no-borrow and borrow branches from digit positions.
C854 — Explain the990 and1980 branches by decimal borrowing
Question. Does subtraction of the1400 anchor gap force the repeated paired differences?
Sources. C852–853 digit registers
Inputs
{}
Results
{
"branches": {
"path": "model/inverse_long_core_branches.json",
"sha256": "418a6416c1a58fb34c0422d9915ccb2ad6bd1b44ed9bcc43ccf96f0c7c7c02dd",
"bytes": 2979
},
"branch_values": [
990,
1980
],
"derivation": "the shared terminal core digit cancels after positional reversal; leading/tens changes force the remaining gap"
}
Finding. No borrow yields990; a tens borrow yields1980. These are forced branch values for every applicable source row, rather than separately chosen gaps.
Reassessment. Explain every shortened-core source row by the same positional rule.
C855 — Explain every shortened-core branch
Question. Which positional changes produce the later nonconstant paired differences?
Sources. C852–854
Inputs
{}
Results
{
"branches": {
"path": "model/inverse_short_core_branches.json",
"sha256": "fb9e0311663e549bcb790b83c963c12b4f8c56b5a4c775d265f84df52f81b8c0",
"bytes": 2122
},
"formulas": {
"three_to_two": "1260+90a−90b−900c",
"three_to_one": "990−990c"
}
}
Finding. The later variations follow core-length changes, which move the same digits into different place values. The nonlinear field therefore needs its digit register, not extra chronological corrections.
Reassessment. Resolve the two retained-zero source cases and complete the partition.
C856 — Resolve retained-zero cases without changing the operation
Question. Do Adam and Jacob follow the same register model?
Sources. C852; latest File52c placeholder rule
Inputs
{}
Results
{
"retained_zero_cases": [
{
"name": "Adam / Creation",
"n": 410,
"source_durations": [
4100,
2700
],
"placeholder_counts": [
2,
2
],
"endpoints": [
1406,
8606
],
"delta": 7200
},
{
"name": "Jacob",
"n": 200,
"source_durations": [
2000,
600
],
"placeholder_counts": [
3,
2
],
"endpoints": [
2006,
2006
],
"delta": 0
}
],
"complete_case_partition": [
14,
16,
2
]
}
Finding. Adam’s two-placeholders route gives7200 separation; Jacob’s fully retained2000/600 values give0. The exceptional-looking rows are ordinary cases of the stated zero-place rule.
Reassessment. Test the full paired-field law and rule out one affine column conversion.
C857 — Test complete coverage and the affine obstruction
Question. Can the two original endpoint columns be related by one global affine map?
Sources. C852–856
Inputs
{}
Results
{
"forced_affine": {
"slope": 1,
"shift": 990,
"defining_sources": [
"Seth",
"Enosh"
]
},
"counterexample": {
"source": "Lamech",
"predicted": 4226,
"actual": 5216
},
"coverage": 32
}
Finding. Two distinct990-gap rows force a translation by990, which fails on the1980 branch. The digit-register model covers the complete manifest where a single affine column map cannot.
Reassessment. Integrate the gain field with the source-path model without conflating it with rounding.
C858 — Integrate the decimal module by its retained register
Question. How does one-pass reversal join the common grammar without becoming a chronology-wide affine operation?
Sources. C852–857; C831 rounding/path model
Inputs
{}
Results
{
"module": {
"path": "model/inverse_module_summary.json",
"sha256": "bde0cd431d5efd716efd80d92de26b2cf52ba7dd2128c23d73168826f5c48c1f",
"bytes": 494
}
}
Finding. The shared model needs a digit register for decimal evaluation just as it needs categories for list measurement. The complete gain field explains route dependence while leaving source selection and historical interpretation open.
Reassessment. Freeze the complete NT indexed-display family and its comparison domains.
C859 — Freeze the complete NT display domain
Question. Which source object can be compared without changing its claim status?
Sources. File43 §3.4; File51a §3.1; File54 §§6,8.6,13.2
Inputs
{}
Results
{
"packet": {
"path": "model/NT_inputs.json",
"sha256": "5b5baff0eaaf68b71c1be598c1619cf840bc2da75c779d30336c822b6e8fb269",
"bytes": 129000
},
"sources": [
"File43",
"File54",
"File15",
"File51a"
],
"literal_tables": 41,
"display_rows": 78
}
Finding. The new object is the entire display-only ledger, with shared-name comparisons ending at Jacob. Its schematic labels, count types and civil crossing remain explicit.
Reassessment. Reconstruct all 78 rows from one index rule.
C860 — Recover the complete 78-row display
Question. Does one civil index reconstruct every opening and closing boundary?
Sources. File43 §3.4
Inputs
{
"civil": "BC b maps to 1−b; AD a maps to a"
}
Results
{
"display": {
"path": "model/NT_full_display.json",
"sha256": "d2f7053688c4b16b3671bcf84e6ce0539652095cacaa7b13561b40df7527f591",
"bytes": 8304
},
"primary_span": 5390,
"extended_span": 5460,
"crossing_row": {
"r": 0,
"open": -5,
"close": 65,
"Luke": "Jesus",
"Matthew": "Jesus Christ"
}
}
Finding. One rule x(r)=−5−70r reconstructs all 78 displayed rows. The primary 77-row span is 5390; the final AD65–135 extension increases it to 5460.
Reassessment. Separate named generations, intervals and carrier slots before comparison.
C861 — Separate the complete count objects
Question. Why do several legitimate NT spans coexist?
Sources. File43 §§2,3.4
Inputs
{}
Results
{
"objects": {
"Luke_names": 76,
"Luke_intervals": 75,
"Luke_birth_span": 5250,
"Luke_names_projection": 5320,
"Matthew_names": 41,
"Matthew_birth_span": 2800,
"Matthew_carrier_span": 2870
},
"artifact": {
"path": "model/NT_count_objects.json",
"sha256": "adc4fb617491fdf1f1f9fbf5f6c559dd1ff7088ce790bcfa34caf6f8b486bf38",
"bytes": 192
}
}
Finding. 76 Luke names measure 75 birth intervals; 41 Matthew names measure 40 birth intervals or 41 carrier slots through AD65. These are different measured objects, so none silently repairs the others.
Reassessment. Compare the full 22 shared Genesis names with the strict MT Rounded path.
C862 — Construct the whole Luke–MT comparison field
Question. Can the highlighted bridges be located within a complete named field?
Sources. File43 lines674–696; File51a §3.1 strict regular table
Inputs
{}
Results
{
"field": {
"path": "model/NT_MT_field.json",
"sha256": "d5868ac088ea4c4394124a7e43edfb3e05bfeba639827f5e973f7b01bec2c280",
"bytes": 2861
},
"ordered_G": [
1150,
1210,
1245,
1265,
1265,
1260,
1350,
1345,
1460,
1570,
2000,
2030,
1925,
1885,
1850,
1810,
1770,
1730,
1690,
1690,
1720,
1710
]
}
Finding. The 22 common names give one complete difference field. The 1150 Adam and 1260 Jared bridges are members of that field, with the strict Actual4112 and Rounded4106 states kept distinct.
Reassessment. Recover all field values from local edge differences and one terminal.
C863 — Derive the local generator of the NT–MT field
Question. Does a terminal value plus every local difference reconstruct the whole comparison?
Sources. C862 complete named field
Inputs
{}
Results
{
"generator": {
"path": "model/NT_MT_edge_generator.json",
"sha256": "cd68ef6b5e218c258dc3ff30d648772d33404f38860df5085feb5f154472ad64",
"bytes": 2884
},
"Cainan_contraction": {
"from": "Arphaxad",
"to": "Shelah",
"NT_edge": 140,
"MT_edge": 35,
"difference": 105
},
"Noah_edge": {
"from": "Noah",
"to": "Shem",
"NT_edge": 70,
"MT_edge": 500,
"difference": -430
}
}
Finding. All 22 differences are generated by G_i−G_next=NT_edge−MT_edge and terminal1710. The sole 140-year NT shared-name edge records the intervening Cainan; the Noah edge explains the −430 local change.
Reassessment. Restore the admitted MT Cainan explicitly and compare the two edge measures.
C864 — Compare the restored common name graph
Question. Does inserting the admitted Cainan equate the two measurements?
Sources. C831 admitted Cainan insertion; C862–863
Inputs
{
"MT_Cainan_interval": 130,
"NT_slot": 70
}
Results
{
"restored": {
"path": "model/NT_MT_Cainan_restored.json",
"sha256": "46441b0b41bf1df994edae7b66280d7656c4698f1b5e8a807042db4b5b176e53",
"bytes": 4037
},
"local_edges": [
{
"from": "Arphaxad",
"to": "Cainan",
"NT": 70,
"MT": 35
},
{
"from": "Cainan",
"to": "Shelah",
"NT": 70,
"MT": 130
}
],
"local_G": [
1900,
1865,
1925
]
}
Finding. Restoration yields the same 23-name graph but different edge weights: 70|70 in NT and 35|130 in restored MT. Topological alignment does not require equal durations.
Reassessment. Transfer the Actual-to-Rounded residual theorem across the whole native comparison.
C865 — Transfer the rounding residual to the complete NT comparison
Question. Can the Actual and Rounded comparison fields be related without new fitting?
Inputs
{}
Results
{
"response": {
"path": "model/NT_rounding_response.json",
"sha256": "e6e2bb2979741f262f8d970c828b0198a3ae315d5382cdc57de1c22c5ff2e9e4",
"bytes": 2788
},
"nonzero_support": [
"Adam",
"Seth",
"Enosh",
"Kenan",
"Mahalalel",
"Jared",
"Enoch",
"Methuselah",
"Lamech",
"Peleg",
"Reu",
"Serug",
"Nahor"
]
}
Finding. Across every shared node, G_Rounded−G_Actual equals the negative MT rounding residual. The existing residual mechanism transfers unchanged to this new display object.
Reassessment. Classify all E returns within the finite NT index domain.
C866 — Classify the complete finite E return family
Question. Which positive display indices return to display indices under E?
Sources. File43 complete display; File54 Enoch fork
Inputs
{
"domain": "r=0,...,76",
"E": "25/23"
}
Results
{
"returns": [
{
"r": 0,
"image_r": 0,
"source": "Jesus",
"image": "Jesus",
"source_BC": 6,
"image_BC": 6
},
{
"r": 23,
"image_r": 25,
"source": "Melki",
"image": "Cosam",
"source_BC": 1616,
"image_BC": 1756
},
{
"r": 46,
"image_r": 50,
"source": "Salmon",
"image": "Hezron",
"source_BC": 3226,
"image_BC": 3506
},
{
"r": 69,
"image_r": 75,
"source": "Enoch",
"image": "Creation of Adam",
"source_BC": 4836,
"image_BC": 5256
}
],
"artifact": {
"path": "model/NT_E_returns.json",
"sha256": "3fd2848a494b025de9c077ff77f10011cb24bf0a463fc3b1f5a7754b04e029d7",
"bytes": 528
}
}
Finding. Coprimality of25 and23 makes 23-divisibility the complete return rule. The four finite returns, including the fixed hinge, follow from one lattice condition; only the Enoch fork carries the supplied interpretation.
Reassessment. Classify P on the same fixed domain and compare its intersection with E.
C867 — Classify P and the complete shared-return fork
Question. What singles out the finite Enoch fork without endpoint selection?
Sources. C866; File43 display; File54 §6
Inputs
{
"P": "70/69",
"domain": "r=0,...,76"
}
Results
{
"returns": [
{
"r": 0,
"image_r": 0,
"source": "Jesus",
"image": "Jesus",
"source_BC": 6,
"image_BC": 6
},
{
"r": 69,
"image_r": 70,
"source": "Enoch",
"image": "Jared",
"source_BC": 4836,
"image_BC": 4906
}
],
"joint_source_indices": [
0,
69
],
"artifact": {
"path": "model/NT_P_returns.json",
"sha256": "57e7e768f128f3bde28682375c60890d81a29710cb6f03a930ac9d45c0306761",
"bytes": 255
}
}
Finding. P returns exactly at multiples of69. On the complete r0–76 domain, Enoch at69 is the only nonzero source returning under both E and P, because lcm(23,69)=69. This is a dependent domain classification, not a probability result.
Reassessment. Transport the full indexed result to the admitted 36BC rail.
C868 — Transport the complete NT fork to the second rail
Question. Does moving both hinge and display preserve every Key radius?
Sources. File43 rail36; File54 Enoch fork; C866–867
Inputs
{
"old_hinge_BC": 6,
"new_hinge_BC": 36
}
Results
{
"translated_returns": {
"path": "model/NT_36BC_rail_returns.json",
"sha256": "17f7a1fd328c63476e6ad5c6c76eda6f800ea34f63d9a0470af4b40ece161565",
"bytes": 868
},
"Enoch": [
{
"key": "E",
"source": "Enoch",
"image": "Creation of Adam",
"source_BC": 4866,
"image_BC": 5286,
"old_image_plus30": 5286
},
{
"key": "P",
"source": "Enoch",
"image": "Jared",
"source_BC": 4866,
"image_BC": 4936,
"old_image_plus30": 4936
}
]
}
Finding. Moving the whole display and hinge by30BC preserves every radius and Key index. The source fork becomes4866→5286/4936. This is whole-frame covariance, distinct from an isolated MT apparent-age adjustment.
Reassessment. Construct the entire common49/70 coarsening of the primary span.
C869 — Recover the whole49/70 common coarsening
Question. How do the two measurements divide one primary5390-year display?
Sources. File54 §§8.6,13.2; C860
Inputs
{
"span": 5390,
"units": [
49,
70
]
}
Results
{
"unit": 490,
"boundaries": {
"path": "model/NT_49_70_coarsening.json",
"sha256": "0f8f6b632e788373b74ddac612833439ab7771d12b0a72baef53e4076e4974ee",
"bytes": 959
},
"partition_common_blocks": [
3,
5,
3
],
"partition_70_slots": [
21,
35,
21
],
"partition_49_units": [
30,
50,
30
]
}
Finding. 70k=49j holds exactly at k7m,j10m. The whole primary span has12 common boundaries in490-year steps; the source1470|2450|1470 partition becomes3|5|3 blocks in either measurement. The extended49-grid is a comparison construction.
Reassessment. Test reflection on the complete common grid and its source-marked partition.
C870 — Recover the full reflection of the primary display
Question. Which part of the chiasm is automatic grid closure and which part is supplied placement?
Sources. File54 primary chiasm; C860,869
Inputs
{}
Results
{
"reflection": {
"path": "model/NT_primary_reflection.json",
"sha256": "f8d0f90c2df70d00c1860bba662e5b44f509ff956993a095f01ee1e9e0e1a460",
"bytes": 6988
},
"marked": {
"outer_pair": [
-5325,
65
],
"BJ_pair": [
-3855,
-1405
],
"center_civil": -2630,
"center_BC": 2631
}
}
Finding. Reflection x→−5260−x closes the entire primary grid and sends coarse indexm to11−m. Closure follows from uniform spacing; the placement of BJ Creation and Conquest at swapped indices21 and56 is the supplied structural fact.
Reassessment. Checkpoint the completed NT transfer, then test Key domains beyond the homogeneous display.
C871 — Checkpoint the complete new display transfer
Question. What has the cycle established after40 actions?
Sources. C832–870
Inputs
{
"completed_before_checkpoint": 39
}
Results
{
"checkpoint": {
"path": "deliverables/490d_Chronological_Families_Checkpoint_C871.md",
"sha256": "c60360eafabad58481459cfa629adae3c322cc83c4481f8f717e2afc19f11a56",
"bytes": 1328
},
"prefix_actions": 39
}
Finding. The complete NT family transfers to the same ordered-path and measurement grammar. Its new contribution is whole-field reconstruction, finite lattice classification and common coarsening, not additional isolated dates.
Reassessment. Freeze the complete operator packet and derive the general grid-preservation condition.