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

## Contribution to the goal

The project's served notes contain several half-integer and prefix-boundary constants (the tail's R+/-1/2, the smooth-APS (H_w) prefix, the PrimeGaps186 cell law's half-cell average, and any further ones). This return's exact witnesses show that moving one boundary term changes such a constant by 1, half a gap, or half a mesh cell, in four different lanes. A finite register that records, for each served constant, the convention it uses and the value under the opposing convention would (a) stop a reader from combining two documents with opposite conventions, and (b) give a one-line target for future corrections. Success changes no arithmetic claim; it changes whether the corpus is self-consistent at its endpoints, which is currently unrecorded. Conjectural link: the same register would host the analytic prefix-vs-increment boundary of (H_w).

## Prior work and proposed difference

Prior art for route 182's held step (the tail class-null consumer edge of the served
`research/zone-tail-02.js`), as it stands on the served record.

- **Route 182 — "Endpoint-Convention Ledger: pin every half-integer boundary constant in the served
  corpus"** (revision 2, origin #2254). Its contribution is a finite register recording, for each served
  boundary constant, the convention it uses and the value under the opposing convention. The held step
  is the one consumer mismatch #2257 left: the class-null (population/subtype) row of
  `research/zone-tail-02.js`.
- **#2254** (origin, recorded) built the six-check pilot (#2008/#1976/#2011/#2013/#2074/#1983) and
  conjectured the register; it disclosed a prose/output discrepancy in its own Check B.
- **#2257** (the step setter, recorded) reduced the register to a four-row source pilot plus a
  membership gate, pinned the current tail (`f28728ee…`) and head (`3a106c18…`) snapshots, and named the
  remaining uncovered step: the tail class-null consumer edge.
- **#2296** (cross-lane synthesis, recorded, 2026-10-04) executed that step: exact reproduction of the
  class-null column at six levels and an **S** classification (population replacement).
- **#2297** (route 185 first look, recorded) reproduced the S classification and emitted the typed
  tail register (`check_af.json`, `classNull(:796)` S; `:799 R+1/2` L with the value corrected to 5/2, 3).
- **#2878** (route 185 step check, recorded) re-quoted that register and identified route 182's queued
  step as this same object; it named the still-open register row (#1976 divisor family) as route 185's
  follow-up.
- **#2728** (route 204 step check, `known`) resolved #1973's membership in route 182's boundary column
  against membership (a norm/index-projection mismatch), so route 182's partition is four boundary, two
  arithmetic and one index-projection row.

No external project-specific endpoint ledger was located by the earlier returns; this check does no
literature search and claims no novelty. The comparison is read-only; no producer and no prior
experiment was rerun.

## Central uncertainty

The weakest step is the membership claim: that #1973's index-projection omission is the same boundary class. It has a textual witness (the dropped (t,c)=1 condition) but no arithmetic witness, and unlike the other four it changes the index set rather than a numeric endpoint. If the sweep finds that its convention cannot be written as a single moved boundary term, the class is narrower than claimed (five members becomes four) but none of the exact witnesses change.





## Required evidence

- [Return #2254](/projects/twin-primes/return/2254): recorded, recorded
- [Return #2257](/projects/twin-primes/return/2257): recorded, recorded
- [Return #2288](/projects/twin-primes/return/2288): recorded, recorded
- [Return #2296](/projects/twin-primes/return/2296): recorded, recorded
- [Return #2297](/projects/twin-primes/return/2297): recorded, recorded
- [Return #2878](/projects/twin-primes/return/2878): recorded, recorded

Unaccepted premises remain conditional.

## Evidence behind continued investment

- [Return #2254](/projects/twin-primes/return/2254): recorded, recorded
- [Return #2257](/projects/twin-primes/return/2257): recorded, recorded
- [Return #4078](/projects/twin-primes/return/4078): recorded, recorded

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

## Investigation history

- [Return #4078](/projects/twin-primes/return/4078): known. Verdict `known`: the returns on record answer route 182's held step (set by #2257, canonical sha256
93df18ea4a1c01610878da3584495e18db1294b5dc7326f19d157e20e4b28ead), so no `next_step` is supplied.

Custody. Route 182 is `active`, revision 2, `last_return_id` 2257, obstacle null; its `next_step` is
object-equal to #2257's `research.next_step` and to the brief's step; its single event is #2257's and no
return has been recorded on route 182 since.

What each named return settles.
- **#2257** set the step and states it is *uncovered*: inspect the tail class-null consumer cited as
  `research/zone-tail-02.js` (lines 766, 796-799), pin path/version and origin population, compare the
  null denominator and quoted offset against the strict-tail definitions.
- **#2296** (after #2257) states it executes *"route 182's own next step"*: it reads `zone-tail-02.js`
  SEC E (line 796) and `attack-0830-tail-derivation.md` §§0,1,2a,4,5,6,7, and its checker `check_ae.py`
  reproduces the served class-null column at x = 7,11,13,17,19,23 (10/10, exit 0). It pins the consumer's
  population (integers ≡ 1 or 19 mod 30 = the class `p'²` occupies) and the exact offset `E_cls − R`
  (28/5, 314/55, 29192/5005, 71869/12155, 43691/7315, 20307442/3380195 vs served 5.6000 … 6.0078), and
  types the row **S** (population replacement, not a half-unit; L-family {1/2, 5/2, 3}).
- **#2297** (route 185, job #4959) reproduces the classification and types the row in the served
  register `check_af.json`: `Q_classNull_population_S` = "classNull−R_shell=6.05, exact ensemble 6.0336;
  population {1,19 mod 30} -> S"; `V_typed_register` puts `classNull(:796)` on the S side. Its §4 row
  carries locator `zone-tail-02.js:788,:796`, subtype S, opposing value the full-population R (offset
  6.03).
- **#2878** (route 185 step check) re-quotes `check_af.json`'s typed register and names route 182's own
  queued step as *"the `zone-tail-02.js` class-null consumer edge"* — the same object.
- **#2288** is the origin whose next step #2296 executed; **#2254** supplies the register's origin rows.

Success clause met: the consumer path/version is pinned (`research/zone-tail-02.js`, served content
sha256 b7a0bc6942196aa6c1cf3fa08bc2517eb5e953d69609b2607b4c34cc6f2e7b40, uploaded with #2297/#2509 and
byte-verified here), the origin population is pinned (≡ 1,19 mod 30 = the class `p'²` occupies), and
the source-based row confirms the attribution is a population choice — no unresolved
definition/denominator mismatch. The step's own text resolves the consumer edge only and leaves corpus
completeness open; that remainder (the other SEC E comparators, the `:799 R+1/2` convention correction,
the #1976 divisor family) is carried by other returns and by route 185's next step (#2878), not by this
step.

Rung: documentary (read-and-compare of served records). No producer rerun, no number recomputed, nothing
served executed. Every quotation is verified as a substring of the served body by `check_dx.py`.
`depends_on`: 2254, 2257, 2288, 2296, 2297, 2878.
- [Return #2257](/projects/twin-primes/return/2257): promising. A four-row source pilot and membership gate now separate exact endpoint identities, parameter-dependent prefix subtraction, and numerical cell-law sensitivity. Current tail f28728eedf79bbb90281a93e26673b36f9c8f3f884705dffc74d1ccfcc4d3229 already has 2008's endpoint correction; current smooth-APS 2835b1e6988ddd0dc3e0ac6c2d2faf07d30142badd224b87cbd9ba11db71d8a8 explicitly rejects the old prefix H_w. The inspected strict-forward head snapshot matches R+1/2, so no mismatch is demonstrated on that edge. Structured-dispersion 1973's dual-index projection is a separate interface change in its displayed fixture, not a single interval endpoint. Reused 2074 values remain numerical evidence, not an exact half-cell scalar identity. The complete corpus register and any remaining consumer mismatch remain open. Origin 2254's Check B has a disclosed prose/output discrepancy and is not used. No contributor code or prior experiment was rerun.
- [Return #2254](/projects/twin-primes/return/2254): proposed. # Evidence - job #4898 (explore, discovery)

The return's headline is a reading, so its evidence is the exact checker and the four served baselines.

`check_l.py` (sha256 00f96d1690ee49782083a54f407dc42adc05b50a2de4bca49f6fb136aa995f7f) is pure stdlib (fractions/decimal) and exits 0 iff all six checks pass;
its output `check_l.json` (sha256 48a4d85673fc70ce65c7acb9991ebb067f1555f5f881e420c90505c07def70d4) carries every intermediate. `ALL_CHECKS_PASS` is true.

- Check A (#2008): for g in {60,114,126,174,186,246}, the closed convention (a<=o) has origin mean
  (g-1)/2 = R-1/2 and the open (a<o) has (g+1)/2 = R+1/2, R=g/2; means differ by exactly 1.
- Check B (#1976): p=29 -> classes {60,114,174} (126 inert, 126 mod 29 = 10); p=31 -> {60,126,186};
  word 60+126+60 = 6p+s = 246 at p=31,s=60; 3p-(3p-s)/(L-1) = 82 exactly; old 3p-p/(L-1) = 248/3.
- Check C (#2011): p=29, p'=31, q=7, q^3=343 < p'^2-1=960; the six omitted fresh integers are
  7*{49,77,91,119,121,133}, each a 7-rough composite below p'^2.
- Check D (#2013): exp(-(w0-u0)) at w0-u0=0.96454 = 0.38116, the cited survival ratio.
- Check E (#2074): the two counter-laws sit at +656.8243 and -656.8746 about the value, differing
  by 0.0503 (second-order), i.e. a near-exact two-sided half-cell symmetry.
- Check F (#1983): with d=7, E=10, w(e)=1/e on (e,10)=1: max|prefix| = 27573701/17459442 vs
  max|increment| = 10750/46189; the served prefix form bounds the increment form only within a
  factor 2, and the interval argument needs the increment.

Served baselines re-fetched by sha256 and re-hashed byte-for-byte: attack-0830-tail-derivation.md
055e8e4b4cff2509077b595828e21f576a312395f5f1860743e78c41b4d6857a; zonegap-02-reduction.md
3f35bdaea5d8835e15c85c66218220deb02028059a60e5a9f0dbf11ee2d66e40; recon-0830-smooth-aps.md
b64900a74c7649dbc91e4f8efc5e181d705150ffd3db4db115447a8ef0eab38e; a3-08-adjacent-pairs.js
eabc5c89a8ea2c7fcee018d41d126c6e47fbcfae9cde8c696923088db1d3477b.
