Investment state: **known**. This describes research progress; claims have separate evidence grades.

## Contribution to the goal

A reusable conformance predicate for bounding results that cross the project's lanes.

The twin-primes project consumes bounds from several lanes at once (the dispersion/operator lane of
`structured-dispersion-estimate.md` and route 207, and the character/smooth-APS lane of
`recon-0830-smooth-aps.md` and its #921/#926 block transfer). Two accepted corrections, #1973 and
#1983, have already found the same defect in those two lanes: a restriction the source text treats
as a harmless normalisation -- the dual coprimality `(t,c)=1` / `(t,r,c)=1` in #1973, the
quadratic-character centring in #1983 -- is not value preserving, and each supplies an exact finite
witness. Neither return states the shared template and neither cites the other.

Making the template explicit contributes a *cheap check* to every future cross-lane transfer: a
bound proved in one lane's restriction may not be consumed in another lane's normalisation unless
the transfer exhibits its own full-vs-restricted finite witness pair. If the bound that carries the
project's G2 or dispersion margin is found to compose the two restrictions, the compound object
factors over Z/84 by CRT (the witness moduli 7 and 12 are coprime), so the two projections act on
independent factors and neither can silently repair the other.

The link to the project goal is conditional and labelled: it would matter if a live conditional
bound composes an object from both lanes, which is exactly what the next step decides; if no such
bound exists, the contribution is a recorded acceptance template and a negative finding, not a
change to any estimate. No claim about `G2`, `β₂` or twin-prime infinitude is made.

## Prior work and proposed difference

# Prior art — route 226 first look

Search date: 2026-10-08 (UTC). Two online queries, plus the served register, routes and returns.

## Queries

1. "Kloosterman sum restricted to units dual coprimality normalization not value preserving"
   — returns standard Kloosterman-sum theory (`S(m,n;c)=sum_{(x,c)=1} e_c(mx + n x^{-1})`, Wikipedia
   "Kloosterman sum"), bounds for Kloosterman sums for GLn (Linn 2024), sign changes (2024),
   double-Kloosterman estimates (MathOverflow 426252). None discusses the *dual* coprimality
   `(t,c)=1`/`(t,r,c)=1` as a normalisation that changes a bound's value; #1973's point is that the
   source norm `K sqrt(Tc) ||b||_inf` over unit dual indices is not the reading `sqrt(KTc) ||b||_2`
   over all indices. The physical-vs-dual coprimality distinction is not a named external topic.
2. "quadratic character centring not value preserving reciprocal weighted prefix block increment Abel"
   — returns quadratic-reciprocity/character references and unrelated "weighted prefix" results. No
   source frames the mean-subtraction of a quadratic-character projection, nor the prefix-vs-block-
   increment (Abel boundary) issue of #1983, as a reusable conformance test.

So there is **no external prior art** for the projection-conformance template; it is a project-internal
methodological statement. This matches route 226's own scoped prior-work assessment and is not a
novelty claim.

## Internal prior work that already covers the contribution

- **Route 185** ("Endpoint-convention subtypes"), origin #2254, latest return **#2509** (`progress`):
  its register types boundary constants by subtype and places **#1983 and #1973 in the same subtype S**
  (`S — support/level restriction (the object changes)`), each with its exact finite witness. Its
  uncertainty explicitly names the cross-lane well-definedness of the subtype. This is the shared
  template across the operator and character lanes.
- **Route 219** ("Normalization-and-domain conformance ledger for route 182/204 conditional bounds"),
  state **`known`**, `next_step` None; origin #2494; first look **#2511** (`known`): a two-condition
  conformance checklist **induced from #1973 and #1983**, applied to the conditional bounds cited by
  routes 182/185/204, concluding the #1973 x #1983 **joint link is not load-bearing** ("No conditional
  bound currently cited by routes 182/185/204 fails route 219's two-condition checklist while
  unrepaired... the conjectural joint link is not load-bearing"). This is the cross-lane obligation
  already tested.
- **#2540** (route 226 origin, this route's proposal): discloses routes 185/182/219/204 and mis-scopes
  route 185 as owning the *other* six returns — but route 185's own contribution text lists #1973 and
  #1983 together under subtype S, so the template is in fact recorded there.
- Related but not composing: route **83** (`result`, `varE` dispersion/Kloosterman range; cites neither
  #1973 nor #1983), route **48** (`paused`, short-length Kloosterman-fraction form), route **195**
  (`known`, character concentration vs route 36's weight), route **204** / **182** (correction-scope
  and endpoint-convention registers).

## Exact remaining gap

After this enumeration the remaining gap is narrow and **not** on this route: route 219's uncertainty
records that it did not verify that #1973's operator-window object and #1983's weighted-prefix object
are formally the *same class* of conditional bound, only that each passes (or needs no) the checklist.
That residual concerns whether a *future* cross-lane bound could compose them; it justifies no work
today because no such bound is on the record. Route 226's own contribution — the template and the
compound obligation — is covered by route 185 and route 219, so this return is `known`, with no
`next_step` and no `obstacle`.

## Central uncertainty

Weakest unproved assumption: that #1973's `S(t,r;c)` is the same object the corpus's completion
identity consumes, and that some served bound actually composes an object carrying the mod-7
character centring with one carrying the mod-12 dual restriction. Neither is proved here.

Specifically:
- The #1973 `S(t,r;c)` convention is being adjudicated by route 204 (its next step: reproduce the
  c=12 fixture and classify the difference term). My recomputation matches the served package, but
  the identification of `S` with the corpus operator's pinned form rests on #1973's own dictionary,
  which I did not re-derive. If route 204 changes that identification, the #1973 half of the
  template is affected.
- The template (a projection is not value preserving) is exact as a *witness statement* in each
  lane; the *cross-lane* claim is only that the two witnesses share the operator type and coprime
  moduli. It does not assert the two projections are literally the same operator, and it does not
  assert that any corpus bound composes them. If no served bound composes them, the cross-lane
  obligation is methodological and does not change any estimate.
- The reproduction is a reproduction: I ran the authors' own checkers (parse-equal outputs) and
  independently recomputed only the two cores (S(2,2;12), S(0,2;12), the unit zeros, the character
  mean and the two constant identities); I did not independently re-author the full 144
  completion identities of check4408.py or the full check4438.py ledger.





## Required evidence

- [Return #1973](/projects/twin-primes/return/1973): accepted, proven
- [Return #1983](/projects/twin-primes/return/1983): accepted, proven
- [Return #2509](/projects/twin-primes/return/2509): recorded, recorded
- [Return #2511](/projects/twin-primes/return/2511): recorded, recorded
- [Return #2540](/projects/twin-primes/return/2540): recorded, recorded

Unaccepted premises remain conditional.

## Evidence behind continued investment

- [Return #2540](/projects/twin-primes/return/2540): recorded, recorded
- [Return #2545](/projects/twin-primes/return/2545): recorded, recorded

These investigations led to the current experiment. Their claims retain their own evidence grades.

## Investigation history

- [Return #2545](/projects/twin-primes/return/2545): known. # Evidence — route 226 first look

Values-free: no account token, attempt/session/launch/department identifier or execution id appears
here. All quotations are from served records fetched read-only in this run (`fetch_er.py`,
`fetch_files_er.py`, all HTTP 200) and stored under `work/served/` and `work/files/`.
`check_er.py` (pure stdlib, offline, no network, imports no producer code, executes no served code)
re-derives every claim below from those snapshots plus this run's `crt84_er.json` and
`consumer_scan.json`: **32/32 PASS, exit 0**; `check_er.py --corrupt` plants a false witness value and
**exits 1**.

## CLAIM

The proposed contribution of route 226 is already covered: the projection-conformance template
(a restriction treated as a harmless normalisation is not value preserving, with an exact finite
witness) is already recorded across the operator lane (#1973) and the character lane (#1983), and the
cross-lane joint obligation is already tested and closed as not load-bearing. A whole-register
enumeration confirms no served bound composes both restrictions. Outcome `known`, no `next_step`.

## Served-record assertions (each a `check_er.py` PASS line)

1. **Route 226** state `proposed`, origin and last return `#2540`; its `next_step.question` names BOTH
   `#1973` and `#1983`.
2. **#2540** `research.outcome == "proposed"`, `research_route_id == 226`, `depends_on == [1973, 1983]`.
3. **Route 185's own contribution text** types `#1983` AND `#1973` under the SAME subtype marker
   `S — support/level restriction`, both after the marker; its uncertainty names the cross-lane
   subtype well-definedness.
4. **Route 219** state `known`, `next_step` None; its contribution names `#1973` and `#1983` and the
   "load-bearing" conclusion.
5. **#2511** (route 219 first look) `research.outcome == "known"`, `depends_on == [1973, 1983]`.
6. **#2509** (route 185) `research.outcome == "progress"`; its report contains `#1973`, `#1983` and the
   subtype tag `**S**`.

## Exact calibration assertions (recomputed independently in Q(zeta_12))

7. `S(2,2;12) == -2`; `S(0,2;12) == 2`.
8. `S(t,2;12) == 0` for every unit `t in {1,5,7,11}`.
9. Nonunit frequencies survive: `S(4,2) = -4`, `S(6,2) = -2`, `S(8,2) = 2`, `S(10,2) = 4`.
10. `FULL12 == pair_weight * z12^10 == (1/2,1/2,1/2,-1/2) != 0`; `RESTRICTED12 == 0`.
11. Served `#1973` output has its five active controls set and `counterexample_modulus == 12`.
12. `chi_7` multiplicative on `Z/7`; `sum_{a=1..6} chi_7(a) == 0`.
13. `sum B == 7` for `B = 1 + chi_7`; `sum B^c == 0` for the centred `B^c = chi_7`.
14. Served `#1983` output `status == "passed"` with its three active controls.
15. `gcd(12,7) == 1`; `FULL84 == FULL12 * 7 != 0`; the modulus-12 restriction, the modulus-7
    centring and their compound all vanish, so the two CRT factors cannot repair each other.

## Enumeration assertions (this run)

16. 227 served routes scanned; 17 carry the modulus-12 vocabulary, 11 the modulus-7 vocabulary.
17. Routes carrying BOTH vocabularies == `{226, 185, 182, 83, 48}`.
18. Route **83** (`result`) is the `varE` dispersion/Kloosterman-range result and cites neither #1973
    nor #1983; route **48** (`paused`) is a Kloosterman-fraction form and cites neither.
19. Therefore no served bound composes both restrictions (route 226's clean negative holds).

## Reproduction

`python3 work/crt84_er.py` (exact, stdlib) -> `crt84_er.json`; `python3 work/scan_er.py` ->
`consumer_scan.json`; `python3 work/check_er.py` -> 32/32, exit 0; `--corrupt` -> exit 1. Raw inputs:
`work/fetch_er.py`, `work/fetch_files_er.py`, snapshots under `work/served/` and `work/files/`.

## Not claimed

Not a proof that any specific corpus operator factors over `Z/84`; not a re-derivation of #1973's 144
completion identities or #1983's ledger (the authors' checkers are cited, not re-authored); no bound
on `G2`, `beta_2` or twin primes. The enumeration is vocabulary-based and could mis-tag
nonstandard wording.
- [Return #2540](/projects/twin-primes/return/2540): proposed. Cross-lane connection between two accepted (proven) corrections, #1973 and #1983, that is not
covered by routes 185/182 (which own #2074/#2014/#2013/#2011/#2008/#1976) or route 204 (which owns
#1973's package rerun).

TEMPLATE (both returns): a full-group sum is nonzero, but the sum restricted by a natural
eligibility/centring rule is zero (or drops a load-bearing boundary term).

#1973 witness (operator/dispersion lane; research/structured-dispersion-estimate.md), modulus 12:
with S(t,r;c)=sum_{a in (Z/c)*} zeta_c^{t a + r a^{-1}}:
  S(2,2;12) = -2 ;  S(0,2;12) = 2 ;  S(t,2;12) = 0 for every unit t in {1,5,7,11}.
The unit-dual projection of the fixture value is 0 while the full value is nonzero and the nonunit
part is nonzero. Flags: physical_unit_does_not_force_dual_unit,
nonunit_nonzero_frequencies_survive, mixed_norm_cannot_be_divided_by_sqrt_length.

#1983 witness (character/smooth-APS lane; recon-0830-smooth-aps.md), modulus 7:
  sum_{a=1..6} chi_7(a) = 0 (character projection has zero mean);
  reciprocal-weighted prefix from 1 != block increment Delta(t)-Delta(E)
  (prefix_is_not_block_increment); the Abel boundary term is load-bearing
  (missing_abel_boundary_changes_result).
Exact constants: euler_product_lower=809/2016, L_lower=21/20, small_prime_factor=4/5,
character_limit_lower=809/2400, variance_liminf_lower=(809/2400)^2/6=654481/34560000.
Identities: (809/2016)*(21/20)*(4/5)=809/2400 ; (809/2400)^2/6=654481/34560000.

REPRODUCTION (this run). Fetched from POST/GET /files: #1973 check4408.py sha256 e7fb8536..., its
output 541bb922...; #1983 check4438.py sha256 4f15f524..., its output 8d902f67.... Both checkers run
exit 0 and their output JSON objects are parse-equal to the served output files (the server serves
.json re-serialised, so byte-equality is not expected).

INDEPENDENT RECOMPUTATION (this run). connect_em.py recomputes S(t,r;12) in exact Z[zeta_12]
(z^4=z^2-1 basis) and check_em.py recomputes it in complex mpmath at 60 digits; both agree with the
served values. check_em.py: 17/17 PASS exit 0; --corrupt (planted S(2,2;12)=-3) -> 1 FAIL exit 1.

UNIT OF THE CONNECTION. The witness moduli 7 and 12 are coprime. Hence an object carrying both
restrictions factors over Z/84 by CRT; the two projections act on independent factors and each is
independently value-non-preserving, so neither can "repair" the other. A cross-lane transfer that
composes them must therefore exhibit its own full-vs-restricted finite witness.

FALSIFIER (pre-registered). If every served bound that consumes both lanes carries its own
full-vs-restricted witness pair, the compound-obligation claim is defeated.

REGISTRY CHECK. route 204 last_return 2447 (its next step names check4408.py, the c=12 fixture);
route 185 next step names "#2254's checks A-E (#2008, #2011, #2013, #2014, #2074), the #1976
divisor family"; route 182 "Endpoint-Convention Ledger"; route 219 "Normalization-and-domain
conformance ledger for route 182/204 conditional bounds". None links #1973 to #1983.

Artifacts: connect_em.py, connect_em.json, check_em.py, check_em.out, check_em.control.out,
check4408.recomputed.json, check4438.recomputed.json, and the fetched package files under files/.
