# C737 — Transfer the full bridge to SP

## Question

Does the same recurrence preserve SP’s local counting conventions throughout the field?

## Inputs

```json
{
  "Cainan": "OFF",
  "terminal_lower_pair": [
    2433,
    2166
  ],
  "edge_corrections": {
    "Noah": 2,
    "Lamech": -1
  },
  "Lamech_count": "53rd year52completed;653inclusive lifespan ledger"
}
```

## Sources

```json
[
  "File18 §§3.1–3.2,6C; C733–C736"
]
```

## Opened utc

2026-09-28T01:43:08.226805+00:00

## Results

```json
{
  "names": [
    "Adam",
    "Seth",
    "Enosh",
    "Kenan",
    "Mahalalel",
    "Jared",
    "Enoch",
    "Methuselah",
    "Lamech",
    "Noah",
    "Shem",
    "Arphaxad",
    "Shelah",
    "Eber",
    "Peleg",
    "Reu",
    "Serug",
    "Nahor",
    "Terah",
    "Abraham"
  ],
  "lower_mode_bridge": [
    8982,
    8182,
    7375,
    6560,
    5720,
    4890,
    4105,
    3805,
    3152,
    2551,
    2103,
    1603,
    1300,
    997,
    727,
    618,
    511,
    411,
    342,
    267
  ],
  "row_generators": [
    800,
    807,
    815,
    840,
    830,
    785,
    300,
    653,
    601,
    448,
    500,
    303,
    303,
    270,
    109,
    107,
    100,
    69,
    75
  ],
  "source_center_checks": {
    "Adam": 13398,
    "Peleg": 3436,
    "Terah": 2580
  }
}
```

## Finding

All20 SP comparisons follow from the same recurrence with its two declared edge corrections. The Creation bridge8982 arises from the full source profile. The653 inclusive lifespan ledger and52 completed regular interval remain distinct inputs, rather than an unexplained one-year repair.

## Reassessment

Compare the three complete profiles on their shared named boundaries and locate their source differences.

## Checks

```json
{
  "regular_edges": true,
  "source_nodes": true,
  "whole_field": true
}
```

## Closed utc

2026-09-28T01:43:08.227012+00:00

## Record provenance

Exact record hash: `4925158cf69551cc48800bde92491f77d773e028f56bbdd86819b04e7821c5bf`

Source journal: `Research_Cycles/C0732_C0831/journal.json`