Generic latest-reset capability
Reset positions 16–18 can be unified by one exact rule: choose the latest active reset and evaluate only the suffix after that position.
Diagnostic work, exact algebra and local capabilities are not treated as end-to-end mining advantage.
What was tested?
Reset positions 16–18 can be unified by one exact rule: choose the latest active reset and evaluate only the suffix after that position.
Why the test is meaningful
Carry is a first-order recurrence, so a later forced state erases every earlier carry dependency. The union of resets must use maximum-position dominance; adding or multiplying individual reset rates would count overlapping records incorrectly.
r*=max{i∈{16,17,18}:R_i=1}c22=Suffix_{r*→22}(value(R_{r*}))P(any reset)=P(R16∪R17∪R18), not ΣP(R_i)How it was tested
Compile a position-generic contract from exact T1/T2 truth masks, select the maximum reset position, dispatch the corresponding K/P/G suffix and validate on original and fresh cohorts.
What happened
The capability produced zero semantic errors. Latest-reset coverage was 874 of 1,361 records (64.22%) originally and 192 of 300 (64.00%) fresh. Fresh latest positions were bit16:17, bit17:64, bit18:111, none:108; mean suffix stages fell from five to three as the reset moved later.
Exactness and statistical controls
The original/fresh union rates closely agreed, but exact mask equality remained the theorem-level gate. The contract explicitly forbids multiplying reset rates and records downstream attenuation from V42.
What the result means
V43 closes the reset family as a reusable exact representation. Its economy remains unassessed and its known downstream limit prevents promotion to a mining submotor.
Limitations
- Exactness is limited to the declared 16-point source cube.
- Coverage does not equal saved SHA work.
- The downstream a6 interface did not simplify.
Evidence trail
Enumerate all reset overlaps, choose the maximum position, apply the corresponding suffix program and verify every carry-22 lane against direct addition in both cohorts.
Canonical variants
SUBENGINE-V43ASUBENGINE-V43BSUBENGINE-V43CSource: internally audited canonical reports. Local filesystem structure, private headers and operational identifiers are excluded from publication.