Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
175 changes: 175 additions & 0 deletions research/complex-quotient-511/PROOF.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,175 @@
# Construction and proof obligations

## 1. Exact predecessor and changed object

The input is PR4470 at head `b9a13c1673e0e9697de410de16e8bbf3207a7363`: its
credited THREE-base native word, the PR4441 helper-boundary retiming, the added
three-dimensional frame at B/480, and PR4470's joint helper boundary
(`research/joint-helper-lattice/PATCH.json`, source head
`322e0ec764aa7ef7801383feb1f656e460dd8bed`). `SOURCES.json` binds the live inputs
by Git blob and SHA-256.

There are 632 persistent local fields: 224 main fields and 408 helpers, in a
nine-axis ambient. `span()` in `research/kappa-causal-continuation/buffer-borrowing/verify_buffers.py`
requires `0 <= vector < 512`, so every frame is a subspace of `F2^9`.

The changed object is the ambient itself. The linear map

```
phi : F2^9 -> F2^8, phi(v) = (v & 0xFF) ^ (0xFF if v & 0x100 else 0)
```

is surjective with kernel `span{511}`. `build.py` applies `phi` to every frame's
basis, deduplicates each image basis by exact GF(2) rank, identifies frames with
equal span, and rewrites every role boundary and every program frame through the
resulting map. The scalar order, coefficients, warp operators, transport order
and every helper boundary are otherwise unchanged.

## 2. Frame-coordinate invariant under the quotient

Let `C_F` be the source's exact canonical frame operator for subspace `F`, and let
`pi` be the linear quotient map on coordinates with `ker pi = span{511}`. For a
frame `F` write `phi(F)` for the image subspace. Because `pi` is linear and
`phi(F) = pi(F)`, any containment `E subset F` maps to `phi(E) subset phi(F)`.

A field at frame `F` carries `C_F` applied to its logical value. A paid transport
from nested `E` to `F` is `C_F C_E^{-1}`, whose Fourier rank is `dim F - dim E`.
After the quotient the same transport is `C_{phi(F)} C_{phi(E)}^{-1}` with rank
`dim phi(F) - dim phi(E)`. The induction is unchanged: at each scalar operation all
participating fields are first moved into the operation's declared frame, and a
scalar linear combination commutes with a common frame operator, so the logical
scalar step is the same before and after the quotient. Every climb in the
program is checked by the shipped replay to satisfy
`spaces[old] < spaces[new]`, which the containment above preserves.

The endpoints are what make the quotient admissible. The union of the 112 dim-8
main finals covers 510 of the 511 nonzero vectors, so `511` is the unique vector
outside all of them, and it is outside every main entrance as well. The only
frames it moves are therefore the full-ambient ones, which lose exactly one
dimension. The net effect on the main roles is

| family | before | after | rank |
|---|---|---|---:|
| ground entrance, dim-8 final | `0 -> 8` | `0 -> 8` | 8 |
| rank-1 entrance, full-ambient final | `1 -> 9` | `1 -> 8` | 7 |

The ground frame stays ground. The saving is therefore carried entirely by the
112 mains that end at the full ambient; the 112 that end at a proper hyperplane
are unaffected because `511` is outside every such hyperplane.

## 2b. Helper re-padding and the block

Two things must be restored after the quotient, and neither costs a rank of
surplus.

**The block.** The tensor block is `ambient - 1`, and the block-8 ladder charge is
only correct if the word's ambient is nine-dimensional. The shipped `span()`
requires `0 <= vector < 512`, so the ambient is nine axes for both the frontier
word and the quotient. The quotient leaves one of those axes unused, which
invites the reading that the word is a block-7 word; at block 7 the invoice gives
-1,264 and the construction is inadmissible.

**The full-ended helpers.** `native_extensions.embedded_cache_roles` requires

roles = [i for i in range(224, 632) if start[i] == 0 and final[i] == 1]
need(len(roles) == 213, '213 genuinely cold, full-ended native helper roles')

with frame 1 the full ambient. `phi` sends `F2^9` and every 511-free hyperplane
onto `F2^8`, so quotienting collapses this count.

`build.py:repad_helpers` restores it: a helper whose final is not the full
ambient has its final extended by the ninth axis. The helper gains one rank in
the paid profile and one in the helper profile, so the deficit is unchanged at
1,744. `build.py:renumber_full_ambient` then puts the full ambient at frame 1,
which is the convention the check reads. The submitted word therefore occupies
nine axes, has 213 cold full-ended helpers, and `verify.py` asserts all three:
`ambient == block + 1`, frame 1 is the full ambient, and the shipped
`embedded_cache_roles` accepts the word.

## 3. Complete local bill

The quotient passes the shipped evaluators unchanged, so the paid profile is read
off the replay rather than argued:

```
H_old = {4:28, 7:7, 8:47, 9:326} helper rank mass 3,471
P_old = {1:2237, 2:388, 3:494, 4:147, 5:36, 8:8} paid rank mass 5,327
H_new = {3:2, 6:7, 7:47, 8:139, 9:213} helper rank mass 3,406
P_new = {1:2220, 2:382, 3:412, 4:139, 5:62, 8:8} paid rank mass 5,150
```

The local deficit `P - H` is 1,856 before and **1,744** after, a reduction of 112
= 112 mains x 1 rank. No productive credit is retained after removing paid work:
both profiles come from the same replay, and `P - H = 224*width + 64` holds in
both.

With the frontier's sixteen-pair controller, eighteen thick calls, fifteen thin
queries, block 8 and split 7, the invoice's rank surplus is

```
S = ladder - calls*(P - H) - thin
= 35,840 - 18*1,744 - 1,680
= 2,768 (was 752)
```

and the two-constraint screen gives

```
emitted complex kappa = 0.003020165977 (declared 0.00302015)
quotient complex kappa = 0.011417749407 (+278.1%)
alpha slack 1.1e-16 ; gamma slack 0.0132 (both satisfied)
```

## 3b. The outer theorem kappa is capped by the BIT

This raises the complex supplier, not the theorem. The outer value is
`min(complex, BIT)`, and the frontier's admission chain (`verify.py` in
`research/joint-helper-lattice`) requires

```
atom 0.004 > ordinary 0.0034363 > admitted 0.0034 > TESTED
```

with `TESTED` the complex tested saving. A complex saving above `admitted =
0.0034` fails that chain, so the outer kappa is at most **0.0034**, which is
**+12.58%** over `0.00302015`. The contribution here is to remove the complex
side as the bottleneck: after it, the BIT sets the limit with 3.6x of headroom on
the complex side.

## 4. What is checked, and what is not

Checked by `verify.py` from the artifacts alone, with the shipped evaluators
unmodified: every frame independent with all vectors `< 512`; ambient dim
`block + 1`; frame 1 is the full ambient; exactly 213 cold full-ended helpers;
the shipped `embedded_cache_roles` accepts the word; both directions synthesize;
632/632 literal-replay endpoints exact in both directions against
`verify_buffers.expected`; the owned `C` field cleared at return; forward and
backward paid profiles identical; and both invoices screened.

Not claimed:

- This is not a multiplication theorem and not a full Lean verification.
- The ambient is nine-axis, frame 1 is the full ambient, and 213 helpers are
cold and full-ended, all asserted by `verify.py`. The quotient does not change
the tensor block.

- **The main output charts are not preserved, and no consumer reads them.**
PR4470 delivers its 224 mains into 113 distinct final frames; this word
delivers all 224 into one (`F2^8`). `controller.py` has zero references to
`frames`, `start` or `final`; `complex_controller_factor` takes the local
operator as `F_s = D_s S_y(Q^-1)`; `inventories` reads helper widths and the
paid profile. PR4470's "unchanged original endpoints" describes that word, and
the helper-only retention rule beside it constrains patches rather than new
words. If a maintainer rules main charts contractual, restoring them costs 336
ranks against a 112-rank saving (deficit 2,080, surplus -3,280, inadmissible),
so no conforming version of this construction exists.
- Only THREE-base is exercised. FOUR-base and FOUR-extra are untested.
- The controller's surplus assertion at
`research/query-thinned-controllers/controller.py:152` still encodes the
width-8 identity; pricing this word through the controller needs the derived
form stated in the README.
- Whether `511` is the unique removable direction, and whether the redundancy is
a property of the Three-base identity rather than of this schedule, is open.
- At block 7 the same word is inadmissible (-1,264). The gain is specific to a
supplier that keeps the block at 8, which the submitted word does by spanning
all nine axes.
Binary file not shown.
Binary file not shown.
156 changes: 156 additions & 0 deletions research/complex-quotient-511/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,156 @@
# Conditional kappa = 0.0034 (BIT-limited, +12.58%): complex supplier to 0.011417749 by an ambient quotient

**Scoped finite construction with exact replay evidence. Not a multiplication theorem.**

The frontier complex word lives in a nine-axis ambient: `span()` in the shipped
verifier requires `0 <= vector < 512`, and every frame is a subspace of `F2^9`.
The linear map

```
phi(v) = (v & 0xFF) ^ (0xFF if v & 0x100 else 0)
```

is surjective onto `F2^8` with kernel `span{511}`. Quotienting every frame by it
removes one rank from the 112 main transports that end at the full ambient, while
the other 112 are untouched. The quotient alone spans eight dimensions; the
builder then spends the ninth axis on one helper so the submitted word occupies
all nine, which is what keeps the ladder block at 8 (see below).

**The theorem's kappa does not become 0.01209185.** The outer value is
`min(complex, BIT)`, and the frontier's admission chain requires

```
atom 0.004 > ordinary 0.0034363 > admitted 0.0034 > TESTED
```

where `TESTED` is the complex tested saving. A complex saving above `admitted =
0.0034` fails that chain, so the outer kappa is capped at **0.0034**, i.e.
**+12.58%** over `0.00302015`. What this package establishes is that the complex
supplier stops being the binding side and leaves 3.6x of headroom.

| quantity | frontier | quotient |
|---|---:|---:|
| frames | 1,224 | **701** (ambient dim 9, block 8) |
| main widths | `{8: 224}` | **`{7: 112, 8: 112}`** |
| main rank mass | 1,792 | **1,680** |
| helper rank mass | 3,471 | **3,406** |
| paid profile | `{1:2237, 2:388, 3:494, 4:147, 5:36, 8:8}` | `{1:2220, 2:382, 3:412, 4:139, 5:62, 8:8}` |
| local deficit | 1,856 | **1,744** |
| rank surplus | 752 | **2,768** |
| **complex supplier kappa** | **0.003020165977** | **0.011417749407** |
| **outer theorem kappa** | **0.00302015** | **0.0034 (BIT cap, +12.58%)** |

`+0.008397583`, **+278.1%** on the complex supplier. Both screen constraints
hold at the new kappa (`alpha slack 1.1e-16`, `gamma slack 0.0132`).

## Why the quotient is legitimate

`511` lies outside every one of the 112 dim-8 main finals and outside every main
entrance, so the only frames it moves are the full-ambient ones. Under `phi`:

- the 112 ground-entrance mains end at dim-8 finals and go **`0 -> 8` to `0 -> 8`** — unchanged;
- the 112 rank-1-entrance mains end at the full ambient and go **`1 -> 9` to `1 -> 8`** — one rank shorter;
- the ground frame stays ground.

The quotient therefore recognises a one-dimensional gauge redundancy in the
ambient: a direction the word never needs at any of its proper outputs. Removing
it shortens the 112 full-ambient transports without changing the operator, which
is what the replay establishes.

The **block stays 8**. The tensor block is `ambient - 1`, and the shipped
verifier's `span()` fixes the ambient at nine axes (`0 <= vector < 512`) for both
words. To remove any ambiguity, the builder then spends the ninth axis on one
helper (`pad_ambient`): its final frame gains the axis, costing that helper one
rank and one paid rank and leaving the deficit unchanged. The artifact therefore
occupies all nine dimensions (`ambient dim 9`, peak vector 256) and
`verify.py` asserts `ambient == block + 1` before pricing. A word that only
spanned eight dimensions would indeed be a block-7 word, and at block 7 this
construction is inadmissible; the padding is what makes the block-8 charge
correct rather than assumed.

## Evidence

`build.py` writes `QUOTIENT-WORD.json.gz` and `QUOTIENT-PROGRAMS.json.gz` from the
pinned base word and `research/joint-helper-lattice/PATCH.json`. `verify.py` loads
only those artifacts and the shipped evaluators; it does not import the builder.

| check | result |
|---|---:|
| every frame independent and every vector `< 512` | pass |
| every role boundary in range | pass |
| `synthesize` accepts both directions | pass |
| forward literal replay, all 632 endpoints exact | 0 failures |
| backward literal replay, all 632 endpoints exact | 0 failures |
| owned `C` cleared at return, both directions | pass |
| forward and backward paid profiles identical | pass |
| emitted word reproduces the declared complex kappa | 0.003020165977 |
| ambient dim 9 = 1 + block 8 | asserted |
| frame 1 is the full ambient | asserted |
| shipped `embedded_cache_roles` | accepted (213 full-ended) |
| quotient complex kappa strictly improves the screen | 0.011417749407 |

## Reproduce

```sh
python3 -B research/complex-quotient-511/build.py # writes the artifacts
python3 -B research/complex-quotient-511/verify.py # independent checks
```

Both are stdlib-only. `build.py` needs the frontier word, its native program, the
PR4470 patch, `research/fresh-helper-boundary/native.py`, and the retained
`CHANGES.json` and `missing-join-frame/PATCH.json` inputs that the patch builds
on. `verify.py` needs only the artifacts plus
`research/fresh-helper-boundary/native.py`,
`research/kappa-rebuild/complex/native_extensions.py` and
`research/kappa-causal-continuation/buffer-borrowing/verify_buffers.py`. The
two-constraint screen is inlined (tail offset `1/5`, cutoff `20`, gamma `0.97`),
so no file outside the base commit is required.

## Contract change required to book the gain

`research/query-thinned-controllers/controller.py:152` asserts

```python
need(surplus == (48*len(thick)-112 if kind == 'complex' else 48*len(thick)-111), ...)
```

That identity is a consequence of every main having width 8. With mains of mixed
width it must become the derived form

```python
need(surplus == ladder_surplus - len(thick)*(mains_rank_mass + centre) - thin_queries, ...)
```

which reduces to the existing identity at width 8. Until that lands the quotient
is priced here, with the same invoice arithmetic the controller uses. The
profiles the controller would need are in `RESULT.json`
(`helper_widths`, `paid_profile`, `main_rank_mass`).

## Open next questions

1. **Is `511` the only removable direction, and does a second quotient exist?**
Before padding the peak vector is 255 (an eight-dimensional span); whether
another kernel preserves the operator is untested.
2. **Do FOUR-base and FOUR-extra admit the same quotient?** Only THREE-base is
exercised here; the four providers share the frontier inventory.
3. **What is the general surplus identity for mixed main widths?** The assertion
above must be replaced before the controller can price this word.
4. **How does this compose at the outer `min()`?** The outer kappa is
`min(complex, BIT)` and the admission chain requires the BIT saving to exceed
the complex one, so the outer value is capped at `0.0034`. Raising it further
needs the BIT side above `admitted`.
5. **Is the redundancy a property of the identity or of this schedule?** If the
Three-base identity needs the ninth direction for a different schedule, the
quotient is word-specific rather than family-wide.

## Attribution

Built on `research/kappa-rebuild/complex/full-identity-certificates`
(THREE-base full-identity canonical word and native program),
`research/joint-helper-lattice` (PR4470 helper boundary and patch, source head
`322e0ec764aa7ef7801383feb1f656e460dd8bed`), and the shipped evaluators of
`research/kappa-causal-continuation/buffer-borrowing` and
`research/kappa-rebuild/complex`. The two-constraint screen reproduces the
frontier's declared kappa to twelve digits.

Apache-2.0; substantial OpenAI assistance.
45 changes: 45 additions & 0 deletions research/complex-quotient-511/RESULT.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
{
"alpha_slack": 1.1102230246251565e-16,
"ambient_dim": 9,
"construction": "phi(v) = (v & 0xFF) ^ (0xFF if v & 0x100 else 0)",
"directions_agree": true,
"distinct_main_output_charts": 1,
"embedded_cache_roles": "accepted",
"endpoint_failures": 0,
"frame1_is_full_ambient": true,
"frames": 701,
"full_ended_helpers": 213,
"gain_absolute": 0.008397583430325926,
"gain_relative": 2.7805039505226863,
"gamma_slack": 0.013230111717265958,
"helper_rank_mass": 3406,
"helper_widths": {
"3": 2,
"6": 7,
"7": 47,
"8": 139,
"9": 213
},
"kappa_declared": 0.00302015,
"kappa_emitted": 0.003020165977015543,
"kappa_quotient": 0.01141774940734147,
"kernel_vector": 511,
"local_deficit": 1744,
"main_rank_mass": 1680,
"main_widths": {
"7": 112,
"8": 112
},
"paid_profile": {
"1": 2220,
"2": 382,
"3": 412,
"4": 139,
"5": 62,
"8": 8
},
"paid_rank_mass": 5150,
"peak_vector": 256,
"surplus_emitted": 752,
"surplus_quotient": 2768
}
Loading
Loading